feat(gate-107): the same seven items at the bottom-left of every app

[rubenvdlinde]

Implements ADR-114 (ConductionNL/hydra#643).

Why

Seven things belong at the bottom-left of every Conduction app. CnAppNav draws two itself (Personal settings, Admin settings, ADR-079). The other five are the app's own: Documentation, Store, Reports and Features & roadmap in footer, Flows in the settings foldout.

Measured 2026-09-03 across the 21 core apps, from the effective manifest: one app carries all seven, and it is dossiq. Reports is in 3 of 19, Store in 4 of 19.

Why a new gate, when four already read this menu

Every one of them is presence-blind, which is how fifteen apps ship no Store while every gate stays green.

gate	what it does	what it cannot ask
60 icon-vocabulary	validates the icon on an entry that exists	why there is no entry
62 store-plane / 63 settings-surface	judge the names of entries that exist	same
104 reports-one-page	its own header: "does NOT require an app to HAVE a reports page"	absent ⇒ NOT APPLICABLE
53 effective-manifest-crossref	a declared entry resolves	why it was never declared

navigation-budget (ADR-097 D8) was specified and never implemented.

How it decides

By page type, not by label. launchpad and humaniq ship i18n keys as labels (launchpad.menu.dashboards), dossiq's Reports entry has the id AnalyticsGroup, and a label may be translated. Four of the five items are resolved by following entry.route to a page and reading its type. Documentation has no page behind it and is matched on id/label as a documented exception.

The walk descends into children[]. ADR-110's own fleet audit walked only top-level entries, read integriq's nested Flows as absent, and had to withdraw the claim inside the ADR. The clean fixture arm nests Flows under a group for exactly that regression.

The ratchet (ADR-114 D8)

• Blocking now: Documentation, Features & roadmap, Flows, any of the five in the wrong section, and a hand-rolled /settings/admin/<appId> link.
• WARN: Store and Reports, until their rollouts land. Two constants at the top of the checker are the promotion, and they move both the presence and the placement rule, so no app is hard-failed for misplacing a Store while fifteen are merely warned for having none.
• NOT APPLICABLE, never PASS, for an app with no pages. The test is the measurement, not a list of names: ADR-110 named planninq Tier-0 while it shipped pages: [], it now ships nine, and the exemption had quietly lapsed.
• Diff-scoped: an unopened scope is na, not a pass.

Fixtures

Three rows, one per direction of the rule, because the driver grades a verdict plus one named subject. Store and Reports are present and correct in both arms deliberately, so promoting the ratchet later does not silently change what these rows prove. Anti-widening in the clean arm: a Flow runs index in main whose label contains "flow", and the real Flows entry nested inside a group.

Verification

test_gate_acceptance_matrix.sh: 232 passed, 0 failed, 80 of 87 gates fixtured, gate-107 among them. Run against the live fleet the gate reproduces the audit exactly, including integriq/hermiq/openregister's documented Flows-in-main exceptions and shillinq's hand-rolled admin link.

🤖 Generated with Claude Code

---

Update after running it against the live fleet

Two defects the corpus found before this merged, both of which would have shipped a gate that reds an app for being right:

• The page type was not the only correct implementation. The first version tested page.type alone and called openregister's Features & roadmap MISSING. It is type: "custom" at /features-roadmap deliberately ("the built-in roadmap page is not adopted in this shell-swap change"), and shillinq's reports catalogue is custom for a reason gate-104's own header records. isSurface() now accepts the canonical route path as well as the type.
• The footer order is relative, not absolute. openregister runs 1/2, pipelinq 160/200/230, keepiq 80/85 — all correctly sequenced. Hardcoding 90/92/95/100 would have red-flagged four apps and changed no pixel.

Both are fixture controls now: the clean arm's roadmap is a custom page at the canonical path (reverting isSurface reds it, verified 0 → 1 → 0), and the planted arm's Reports sits below Features & roadmap so the order row grades a real defect.

Also fixed: gate-107 was the only silent gate in the package on a repo with no manifest, which failed the entry-point invariant suite under --require-full-coverage (69/1) and the published-location install job. It now declares na out loud, the way gate-60 does. 70 passed, 0 failed.

Fleet state: all 19 manifest-driven apps are at findings=0, thematiq NOT APPLICABLE. The eight app PRs this gate depends on are merged. Acceptance matrix: 235 passed, 0 failed.