@staff0rd/assist 0.1010.1 → 0.1011.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -83,14 +83,14 @@ Keep phases small (2-4 tasks each). A typical item should have 2-3 phases.
83
83
 
84
84
  ### Docs pages belong to Refresh docs
85
85
 
86
- Run `assist config get docs.refreshAfter 2>&1`. If it prints a value, this repo uses **Refresh docs**: docs pages are updated by a separate Refresh docs item after stories ship, and are locked while other items are implemented. In that case:
86
+ Run `assist config get docs.refreshAfter 2>&1`. If it prints a number, this repo uses **Refresh docs**: docs pages are updated by a separate Refresh docs item after stories ship, and are locked while other items are implemented. In that case:
87
87
 
88
88
  - Do not add tasks that update docs pages (e.g. `docs/src/content/docs/`, docs screenshots) to any phase.
89
89
  - Do not add acceptance criteria about docs pages describing the change.
90
90
  - Config help (`configHelp` entries) and command `--help` text are code, not docs pages — keep them in scope as usual.
91
91
  - Exception: when the item's subject is the docs site itself (its pages, content, structure or tooling), plan the docs changes as normal.
92
92
 
93
- If it prints nothing, plan docs updates as the change needs them.
93
+ If it reports the key is not set, plan docs updates as the change needs them.
94
94
 
95
95
  Most phases should NOT have manual checks. Only add `manualChecks` to a phase when the checks are genuinely difficult to automate (e.g. visual appearance, UX flow, hardware interaction). Do not add a final phase just for end-to-end verification — a `Review` phase is appended to every plan automatically, and authoring one is rejected.
96
96
 
@@ -80,7 +80,7 @@ When adding or restructuring plan phases, follow the same rules as /draft:
80
80
  - **Vertical slices, not horizontal layers.** Each phase delivers a thin, working increment verifiable end-to-end — never "backend in phase 1, UI in phase 2".
81
81
  - **Every phase must pass `assist verify` on its own.** Verification includes knip, which fails on unused exports — so every export a phase adds must have a caller wired up in that same phase. No "phase 2 will use it" scaffolding.
82
82
  - If the user proposes a horizontal split, point out that the earlier phase won't verify (knip will flag the unused exports) and suggest a vertical restructure instead.
83
- - **Docs pages belong to Refresh docs.** Run `assist config get docs.refreshAfter 2>&1`. If it prints a value, docs pages are updated by a separate Refresh docs item after stories ship and are locked during implementation, so do not add docs page tasks or docs acceptance criteria — and if the item already has them, propose removing them. Config help (`configHelp` entries) and `--help` text are code and stay in scope. The exception is an item whose subject is the docs site itself, which can plan docs changes as normal.
83
+ - **Docs pages belong to Refresh docs.** Run `assist config get docs.refreshAfter 2>&1`. If it prints a number, docs pages are updated by a separate Refresh docs item after stories ship and are locked during implementation, so do not add docs page tasks or docs acceptance criteria — and if the item already has them, propose removing them. Config help (`configHelp` entries) and `--help` text are code and stay in scope. The exception is an item whose subject is the docs site itself, which can plan docs changes as normal.
84
84
 
85
85
  **To associate an external tracker** (Jira or GitHub — mutually exclusive, one per item; associating one clears the other):
86
86