MARK-003 HIGH: unknown CLI flags are silently ignored — a typo disarms the --strict CI gate

mark accepts any unrecognized dash-argument without complaint (MARK.cli.c:155-180 matches known flags, markcli_inner:123 skips every dash-arg): mark --strikt breach.mkd exits 0 where --strict exits 157 (MARKLIMIT). A typo'd flag in CI silently disarms the budget gate — the docs sell --strict as the CI failure mechanism (DIS-013). From the 2026-07-07 mark/ diagnostic review, orchestrator-verified (mark --utter-nonsense-flag ok.mkd → exit 0, rendered). Method Issues.

Input

Context

Probe (2026-07-07): a bogus flag renders + exits 0 on the fresh build; known-flag path unaffected.
The DIS-013 strict-dir gate exists precisely because silent-pass CI is worthless — this reopens the same hole one typo wide.

Goals

An unknown -/-- argument refuses loudly with a RON60 code (e.g. MARKARG) and non-zero exit; usage hint on stderr.

Constraints

Repro-first (unknown-flag case in mark/test or strict-dir.sh style gate); error code via abc/ok64 conventions.

WIP

Design decisions

(pending)

TODOs

Repro: unknown flag → non-zero exit, no HTML.
MARKARG refusal in the arg loop; suite green.

Blockers and bummers

None known.

Outcome

(pending)