feat(router): project-registerable component nouns (issue #10 dir #3)

[Munawarx]

Summary

Implements issue #10 direction #3 — project-registerable component nouns. Adds an optional policy/component-nouns.yaml; each listed noun behaves like the built-in API noun: when it co-occurs with a live/recorded-state qualifier (alive, up, responding, still, today, right now, …) the prompt routes to runtime, but the noun alone never routes (precision > recall).

Why

Issue #10 showed custom component nouns are invisible to the runtime family (fleet-hub alive right now? got no contract while API responding right now? routed). This lets each project register its own nouns without hard-coding them into tells.yaml.

Design (posted first as issue #16, per CONTRIBUTING core-surface rule)

• New optional file policy/component-nouns.yaml with a nouns: list.
• matcher.loadPolicy merges it into the policy; matchPrompt appends a runtime-component-noun tell when a registered noun + state qualifier is present.
• Per-project: drop a copy next to tells.yaml to register domain nouns.

Measurement (issue #10 ground rules)

• RED tests in test/component-nouns.test.js (4 cases) — all green.
• Precision verified manually: what did we decide about the store? still routes historical (no false runtime); only store + still/read routes runtime.
• Router + component-noun suite: 36/36 green, 0 regressions.

Changes

• src/matcher.js — glossary load + matchComponentNoun + wiring into matchPrompt.
• policy/component-nouns.yaml — example nouns (fleet-hub, connector, ingest, vendor-archive, store).
• test/component-nouns.test.js — RED + precision + backward-compat tests.

Trade-offs / risks

• A broad noun list could hurt precision → mitigated by the qualifier requirement + bench before/after.
• This is a core-surface (routing) change, so it went through issue-first design (issue feat(router): project-registerable component nouns (issue #10 direction #3) #16) as CONTRIBUTING requires.

Files

• src/matcher.js
• policy/component-nouns.yaml
• test/component-nouns.test.js

Co-Authored-By: Hermes Agent noreply@hermes.ai

[Munawarx]

Tracking our current contribution set for Leadline (Munawarx). All are independent, each on its own branch:

• fix(router): add deterministic current-state runtime tells (issue #10) #12 fix(router): deterministic current-state runtime tells — closes issue Router: natural phrasings of the core question class are missed (1 of 5 on real prompts) #10 direction docs: contribution rules + security policy #2 (4/5 → 5/5 natural phrasings route). RED test + bench before/after included.
• refactor(receipts): remove dead createClaimSupportReceipt helper #13 refactor(receipts): remove dead createClaimSupportReceipt helper — dead-code cleanup, 44/44 suite green.
• docs(install): document local clone+link flow and CI install smoke #14 docs(install): document local clone+link flow + CI install-smoke — interim install path until npm publish.
• fix(exam): cross-platform fallback for the labelling/replay harness #15 fix(exam): cross-platform fallback for the labelling/replay harness — extends docs: document the Linux-only requirement for the exam/replay harness #6; best-effort (not race-safe) off-Linux, Linux path unchanged.
• feat(router): project-registerable component nouns (issue #10 dir #3) #17 feat(router): project-registerable component nouns — issue Router: natural phrasings of the core question class are missed (1 of 5 on real prompts) #10 direction docs: link CONTRIBUTING and SECURITY from README #3; design pre-posted as feat(router): project-registerable component nouns (issue #10 direction #3) #16 (core-surface, per CONTRIBUTING).
• docs: document the Linux-only requirement for the exam/replay harness #6 docs: Linux-only exam requirement (still open from earlier).

Each PR is self-contained and ready to review independently. Happy to split, adjust, or rebase any of them. Co-Authored-By: Hermes Agent noreply@hermes.ai

[Nazim22]

Thanks for this — the direction is right (issue #10 dir #3) and worth pursuing, but three blockers before it can land: (1) matching is boundary-less substring (src/matcher.js indexOf) — "storefront"/"restore" match the noun "store"; needs token boundaries. (2) generated matches lack _order, and the shared sorter dereferences it — same-span matches crash the hook. (3) issue #10's intended rule is a qualifier co-occurring with a project-owned component noun (loaded glossary), not a hardcoded list. Happy to re-review a revision.