v4.3.0 — the hygiene check was excluded from its own gate

A home path shipped to a public repo, and the check that exists to stop
exactly that was passed a file list with the offending file removed from it.

.claude/productizer/checks-result.json is committed, and the runner wrote
its own absolute config and root into it. Two occurrences of
/Users/<name> went out in v4.2.0. check-hygiene.sh detects them
correctly; the pre-release gate excluded that path from the manifest to stop
the run churning its own output, and so excluded the only file with a leak.
"PASS hygiene 245/245" was true and worthless.

The runner now emits config repo-relative and root as .. The absolute
values stay in memory for path resolution and never reach disk. Nothing
outside the runner read either field.

Also in this release:

• Stage 5's EARS rules no longer judge superseded requirements. Two of this
  skill's own rules were in direct collision: a superseded requirement keeps
  its original text verbatim (an ERROR to edit), while the EARS check ran on
  every requirement regardless of status. The warning could not be cleared
  without breaking the retention rule. Found by splitting R14/R16/R21, which
  could never have silenced it. --strict is now clean on this repo's spec.
• R14, R16 and R21 each stated two obligations under one id. Superseded, text
  retained, replaced by R23-R28, one obligation each. No id reused, none
  renumbered; verified against a baseline.
• CI, which this repo has never had: claude plugin validate, the Stage 5
  gate, and both self-tests, on every PR and every push to main. Fails closed,
  least privilege, and no github.event.* interpolated into a run: block.
• The view gains a Board tab; the kanban moves off the Dashboard. Setup
  becomes a checklist that appears only while something needs a person, and
  says plainly which items will never tick and why.
• The untagged-versions banner said "so CI builds the releases" in a repo with
  no CI. It now reads the workflow triggers and says what is actually true.
  n/a and "not run" had been rendering identically; they no longer do.