@gobing-ai/spur 0.3.61 → 0.3.63

package/plugins/sp/skills/spur-dev/references/flag-glossary.md

@@ -200,16 +200,25 @@ restrictor. On `dev-refineall` it is instead one of a required pair — supply e
 
 Select an execution mode: `full|implement` on `dev-run` (full pipeline vs implement-only),
 `sequential|parallel` on `dev-runall` (serial vs fanned-out-independent-subset),
-`fan-out|review-panel|investigation` on `dev-parallel`, and the reconstruction depth
-`briefing|structure|architecture|design|full` on `dev-reverse`. Mode selection is explicit and orthogonal
+`fan-out|review-panel|investigation` on `dev-parallel`, the reconstruction depth
+`briefing|structure|architecture|design|full` on `dev-reverse`, and `daily|ad-hoc` on
+`dev-find-issue` (the history-anatomy report mode). Mode selection is explicit and orthogonal
 to `--next`.
 
+### `--date <YYYY-MM-DD>` — local calendar day selection
+
+**Anchor:** `#flag-date`.
+
+Select a local calendar day on `dev-find-issue` (daily mode) and `dev-daily` (report date). DST-aware:
+`--date <that-date>` spans the full local calendar day including any daylight-saving shift, never a
+fixed 24-hour offset.
+
 ### `--task <wbs>` — task work or task narrowing
 
 **Anchor:** `#flag-task`.
 
 Connect the current command's result to task work, or narrow a history analysis to one task
-(`dev-brainstorm`, `dev-debug`, `dev-dogfood`, `dev-find-next`, `dev-history-load`). The value and
+(`dev-brainstorm`, `dev-debug`, `dev-dogfood`, `dev-find-next`). The value and
 the effect are per-command — this flag is a family, not one behavior:
 
 - `dev-brainstorm` `[<feature-id>]` — **creates** one task from the chosen approach, landing at
@@ -221,7 +230,6 @@ the effect are per-command — this flag is a family, not one behavior:
   id names the target instead of offering rank 1.
 - `dev-debug` `[<wbs>]` — **attaches** findings to an existing task. Optional WBS names it.
 - `dev-dogfood` (no value) — **records** run outcomes against the task under test.
-- `dev-history-load` `<wbs>` — narrows the `analyze` step to that task's messages.
 
 ### `--since <ref>` — lower bound on a range
 
@@ -250,10 +258,10 @@ Upper bound on a range: a git ref on `dev-changelog` (defaults to `HEAD`), or an
 
 **Anchor:** `#flag-source`.
 
-Scope the operation to one agent source (`dev-find-issue`, `dev-history-load`): one of
-`pi|claude|codex|gemini|opencode|antigravity|openclaw|omp|grok|agy` (or `all`). On
-`dev-history-load` the value is forwarded to **both** `spur history import` and
-`spur history analyze`; on `dev-find-issue` it narrows the report scan to that source's sessions.
+_(Removed 2026-08-24, HA-S1 0661.)_ The only two commands that consumed this flag;
+`dev-find-issue` (now a `sp:history-anatomy` forwarder) and `dev-history-load` (deleted) no
+longer declare it, so the entry is dead and removed. The underlying `spur history` surfaces
+retain their own `--source` handling.
 
 ### `--status <s>` — filter by task status
 
@@ -280,7 +288,8 @@ Omit the design package (system-design satellite + task `### Design`) on plannin
 
 **Anchor:** `#flag-output`.
 
-Write the command's result to a file path (`dev-daily`, `dev-reverse`) instead of stdout.
+Write the command's result to a file path (`dev-daily`, `dev-find-issue`, `dev-reverse`) instead of
+stdout. On `dev-find-issue` (ad-hoc mode) an explicit path replaces the default run-directory write.
 
 ### `--merge` — trigger branch cleanup
 
@@ -359,8 +368,9 @@ flag sets both.
 
 **Anchor:** `#flag-worktree`.
 
-Batch commands only (`dev-refineall`, `dev-runall`, `dev-verifyall`): run the entire driver loop
-inside an isolated git worktree instead of the operator's working directory. One flag, two modes:
+Batch commands plus single-task `dev-run` (`dev-refineall`, `dev-runall`, `dev-verifyall`,
+`dev-run`): run the entire driver loop inside an isolated git worktree instead of the operator's
+working directory. One flag, two modes:
 
 - **Create mode** — bare `--worktree` (no value). Cut a fresh branch from the current HEAD's ref,
   create a sibling worktree with a derived name, run the batch there. On a fully successful batch
@@ -385,8 +395,10 @@ merges but never removes. This keeps the continue-the-work loop stable — after
 **Value binding.** The following token is consumed as `<name>` **only when it does not begin with
 `-`**, so `--worktree --auto` is the bare create form and `--agent`/`--feature`/etc. are never
 swallowed as the name. `--worktree=<name>` is the unambiguous spelling. `/sp:dev-next` does not get
-the flag (single step; not worth the worktree cost), and `--worktree --mode parallel` is rejected
-(per-task parallel isolation stays task 0142). The full lifecycle — name resolution, dirty-tree
+the flag (single *step*; not worth the worktree cost — unlike `dev-run`, which isolates a whole
+task pipeline), `--worktree --mode parallel` is rejected (per-task parallel isolation stays task
+0142), and `--worktree --mode implement` is rejected on `dev-run` (that mode *is* the pipeline's
+implement stage and runs in the driver's tree). The full lifecycle — name resolution, dirty-tree
 precheck, creation or adoption, crash-safe marker, merge-or-retain, and `--continue` re-entry — is
 specified in [execution-batch.md § Worktree isolation](execution-batch.md#worktree-isolation---worktree-name).
 Portable `git worktree` commands only; the git mechanics are reused from