Code signal deadline cast unreviewed

The check is code_signal_deadline_cast_unreviewed. It is default-on at verify. Severity of a hygiene miss is warning, not fail. It walks JSON and YAML under proof/signals. Missing directory is a silent pass. proof/signals/packs is skipped: those files are the hunter, not a finding.

A hit needs both a time token and a width token in the finding's rule id, message, or tags. Time tokens: deadline, timelock, executeAfter, execute_after, unlockat, timestamp+, block.timestamp. Width tokens: uint32, uint64, narrow, cast, truncat, wrap. Cast-only noise without a time word does not fire. The hop scores those fields. It does not score the artifact path, so the implementation file cannot match itself.

# proof/signals/last-run.json
{
  "findings": [
    {
      "rule_id": "sol.timelock.executeAfter",
      "message": "executeAfter packed into uint32",
      "tags": ["timelock", "cast"]
    }
  ]
}
# no terminal campaign on deadline_arithmetic_faithful
# warn: signal report proof/signals/last-run.json matches
#       deadline/timelock narrow-cast language
# silent packing: the board listed the row. nobody hunted it

When those rows exist, a terminal campaign under proof/vectors can still close the hop. Closed-null, closed-ki, or deferred counts if the campaign binds deadline_arithmetic_faithful, or names a related signal that itself looks deadline-cast shaped. An unresearched or partial campaign is not yet a review. The hop then passes with the campaign id in the summary.

This is not the untriaged-signal hop. A SARIF hit whose owner never listed the class stays on code signal obligations reviewed. A project-level analyzer skip stays on code signal suppressions reviewed. A draft class id that does not resolve stays on code signal unbindable. A P0 campaign that was never opened stays on unresearched P0 vectors. Whether that YAML still resolves stays on vector campaign hygiene.

Inspect the hunt-rank board before trusting a green summary. Then open the packing campaign, not a Jama note.

proof signals findings list --hunt-rank
proof catalog show deadline_arithmetic_faithful
proof role show trust-collapse-audit
proof vector new --id V-H1 --title "Deadline / delay packing sweep" --priority P0
proof vector campaign V-H1 --status closed-null --note "0 NEW Med+; packing board complete"
proof audit --check code_signal_deadline_cast_unreviewed

Disposition each hit as PoC, known issue, residual, or closed-null with a packing table. Do not mint a new shall to carry the skip. CodeSignal is not this hop.

The teaching graph is still one executeAfter finding whose board called it cast noise and whose packing class was never hunted. Close it with a terminal campaign. Do not treat a Jama note as this hop. Do not treat a listed scanner row as a reviewed hunt.

proof audit --check code_signal_deadline_cast_unreviewed --verbose
proof signals findings list --hunt-rank
proof workflow check --stage verify --verbose

The untriaged-signal hop stays on code signal obligations reviewed. The skip-row hop stays on code signal suppressions reviewed. The draft-class hop stays on code signal unbindable. The unopened-P0 hop stays on unresearched P0 vectors. Jama still authors. Proof vs Jama.

Warning, not fail. Promote once the corpus is clean. No proof/signals directory is a silent pass. Cast-only noise without a time token does not fire. The hop does not write the campaign. It does not prove the Go. It does not score artifact paths. Packs stay unscanned on purpose. An explicit opt-out reports skip, not pass. A deferred campaign still counts as reviewed. We have not scored this floor against a frozen Jama pack, a CodeSignal interview, or a frozen OpenGrep corpus. The loss is named, not scored.

The untriaged-signal hop stays on code signal obligations reviewed. The engagement stays on software correctness audit. Jama still authors.

What is code signal deadline cast unreviewed? Same question. Same URL.

Is this CodeSignal? No. Ads code signal is that interview product. A hosted kata is not this cell.

Is this code signal obligations reviewed? No. That hop is whether a fresh signal still has a covering obligation. This hop is whether deadline-shaped text still has a hunt. See code signal obligations reviewed.

Is this code signal suppressions reviewed? No. That hop is whether a project-level analyzer exception still has a reason, a current expiry, and a path on wildcards. This hop is a listed finding, not a skip. See code signal suppressions reviewed.

Is this code signal unbindable? No. That hop is whether proposes_class still names a class that does not exist. See code signal unbindable.

Is this unresearched P0 vectors? No. That hop is whether a P0 campaign YAML is still unopened. This hop fires from signal text even when no YAML exists yet. See unresearched P0 vectors.

Does a missing signals directory fail? No. No proof/signals is a silent pass.

Does a green hop prove the Go? No. The hop observes that deadline-shaped findings still have a terminal campaign. It does not prove the function is correct.

Is Proof a Jama alternative for the shall? No. Jama still authors. Proof vs Jama.