Raised when a generated PDF does not satisfy its checks.

Step 6b must also write the posting text it is holding to the archive.

/apply Step 6b writes the row that six other commands read.

`<company>_<role>` must derive a single path component. `Novo Nordisk A/S` used to derive `novo_nordisk_a/s_<role>/`: every command that *der

#319: the deadline is carried through the whole pipeline and never dropped. The header migration must be header-line-only (inserting it mid-colum

`drafted` is non-final, so readers that mean *submitted* must say so. Each of these defines its set by exclusion from the final statuses, so

Pin the match semantics of the shipped .gitignore, not just rule presence. The guard checks that a rule exists; it never checks what the rule mat

Builds a minimal repo tree the guards pass on, then breaks one thing per test. The guard script resolves the repo root from its own location, so

A hook in .claude/settings.json runs with no prompt when its event fires. The shape used here is the one the Shai-Hulud worm planted in its Augus

Structural checks on the command file itself.

reports/ must be gitignored — it holds personal generated output.

lint_skills.py must pass after the command is added.

The dashboard is a consumer of every tracker column: the Step 1 field enumeration and the Step 3 table columns must stay in phase with the can

The disagreement in full: --validate blesses a file with a null metadata/categories, then the lookup path must render it, not crash. Both pay

Step 3 must consume the posted_date #391 persists. The field exists because a 27-month-old posting ranked Strong Fit at position 1 of 133 (#3

The expensive fetch-and-score batch is bounded independently of output.

Guards for routing Step 1/3/4 through tools/rank_state.py (#395). /rank's Step 1 and Step 4 used to read the whole of seen_jobs.json into the

Spot-checks across readers that prove the vocabulary block is reachable from each command that makes decisions based on tracker status. Forma

Each reader that classifies tracker values must handle both spellings and must not include archive-only values in tracker buckets.

Every portal CLI's search output must carry the Step 2 contract fields.

The posting date Step 2 guarantees must survive into Step 4's storage. Step 2's contract promises a `date` on every portal CLI's search output an

check_skill()/check_command() are the linter's main job and were previously untested - only check_settings() had coverage, so deleting e.g. th

The instructions above target real tokens; if a template renames them, the instruction and this test must move together.

A URL can never be read by curl as an option. gate() rebuilds the target as scheme://host/robots.txt, so the gate path was never exposed; thi

F34: every documented extraction command must pin the encoding.

F9: no document or template doc may teach `\\item [text]`.

Rule patterns are percent-decoded to match the decoded request path. FAIL-OPEN REGRESSION: without this, a site that percent-encodes its own

Step 1b.3 says to scope to the last 14 days via the portal's recency flag - but not every portal has one (jobdanmark offers no date filter or

A 200 whose body is not a robots.txt used to grant permission. Found by adversarial review, not inspection. A misconfigured host answering /r

F31: both template guides must document the LaTeX escapes.

Builds a real git history: a shared base, then an `upstream/master` ref that runs ahead, so the triage script can be exercised fully offline.

Simulates upstream renaming/deleting one framework file while the fork still has its own copy: git show then fails, and the checker used to sw

Category-shape and duplicate-name checks (reuses assert_invalid_data).

End-to-end checks for the --validate pre-flight flow.

The canonical definition must live in /outcome and nowhere else.