Feature

Read the Feature authoring contract and the Trace workflow before changing a Feature or Use Case. Run pnpm run repo docs feature --help for current command syntax.

A Feature is the adopted current product target, even when implementation has not caught up. A finalized but unadopted direction belongs in Roadmap; alternatives that still require comparison belong in Design. Do not weaken a Feature into an implementation-status document.

Before editing, use pnpm run repo docs feature list and pnpm run repo docs feature show to identify the exact package, page roles, direct Use Cases, runner-inventoried cases, Feedback/Memory evidence, and related docs. Test coverage is derived only through case sidecar → owner → exact contract; never infer it from directories, filenames, or readable titles.

Keep each fact in its owning page. Put public TypeScript shape in library.md, command behavior in cli.md, internal invariants in architecture.md, cross-owner sequencing in lifecycle.md, and one minimal user goal in each leaf Use Case. Strong relations remain with their source owner; do not add a reverse registry or formatter metadata.

The Feature structure surface is limited to managed feature create, feature page add, and feature page set. It never creates a package implicitly, and it is not retire, physical delete, move, or Roadmap adoption. For a new leaf Use Case, run pnpm run repo docs use-case create --help: its independent owner publishes the body, node metadata, and index link under an existing Feature and existing Use Case index. Do not copy templates, hand-write generated indexes, or fabricate a receipt.

After changes, rerun pnpm run repo docs feature show for the affected Feature and pnpm run repo docs test show <path#caseId> for every changed case. Use pnpm run repo docs test owner --help when creating, retargeting, or retiring the reusable owner anchor; never hand-edit a case sidecar. Run pnpm lint; run pnpm typecheck when repository tooling or TypeScript examples changed. Commit only the intended Feature, Use Case, relation-owner, sidecar/evidence, and generated-index paths.