chore(start_dev): retire the z_features audit-only tracker mode (#111)

The z_features/ epic-tracker folder is retired (PyAutoMind moved trackers to
complete/archive/epics/). Remove the corresponding audit-only mode from
start_dev: the usage line, the "switch to tracker mode" branch, the long-form
"z_features audit" reference.md section, and the detail pointer. No z_features
refs remain in skills/. pytest 46 passed.

Co-authored-by: Jammy2211 <JNightingale2211@gmail.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

Author: 3 people

skills/start_dev/reference.md

@@ -60,41 +60,6 @@ Legacy check: if a target repo's **main checkout** is on a feature branch not
 referenced by any `worktree:` claim, warn (unregistered prior-session work) —
 ask whether to proceed; don't treat it as an automatic conflict.
 
-## z_features audit (tracker mode)
-
-`z_features/<epic>.md` files are umbrella trackers for multi-task epics; their
-sub-prompts are issued individually. In audit-only mode, **do not create an
-issue** — instead:
-
-1. **Parse** the tracker for sub-prompt references (markdown links → path in
-   parens; bare `<work-type>/<target>/<name>.md` or pre-migration
-   `<target>/<name>.md` paths). Dedupe, resolve `../` relative to the tracker,
-   skip self-references inside `z_features/`.
-2. **Status each sub-prompt** (lifecycle states, issue #71):
-   - exists at `PyAutoMind/draft/<path>` (or a legacy bare path) → **not yet
-     issued**;
-   - exists at `PyAutoMind/active/<basename>` (or legacy `issued/<basename>`
-     during the transition) → **issued**; derive task-name candidates from the
-     filename stem (`_`→`-`) and from `## <task-name>` headings, then check
-     shipped-ness: a `complete/<YYYY>/<MM>/<candidate>.md` record (or, until
-     `complete.md` is retired, `^## <candidate>$` in `PyAutoMind/complete.md`)
-     → **shipped** (record heading + PR URL); no match = **in flight**;
-   - neither → **unknown** (link rot — warn).
-3. **Report** a table (Sub-prompt | Status | Notes) + summary line
-   `N shipped / M in flight / K not yet issued / U unknown`.
-4. **Decide:**
-   - Any non-shipped entries → stop, list outstanding work, do not move the
-     tracker, do not push.
-   - All shipped → verify PyAutoMind is on `main` and clean, show the archive
-     commands, get explicit confirmation, then:
-     ```bash
-     mkdir -p PyAutoMind/z_features/complete
-     mv PyAutoMind/z_features/<filename> PyAutoMind/z_features/complete/<filename>
-     source PyAutoMind/scripts/prompt_sync.sh
-     prompt_sync_push "prompt: archive completed z_features tracker — <stem>"
-     ```
-   Print a one-line "archived" confirmation and stop.
-
 ## Branch survey (the former /plan_branches)
 
 Run after the plan is approved (start_dev step 4): survey every repository the plan will touch, report branch state, and propose a single working branch name for the task.

skills/start_dev/start_dev.md

@@ -17,7 +17,6 @@ and the Mind registry paths used below.
 ```
 /start_dev <prompt-file-path>          # path relative to PyAutoMind/
 /start_dev <prompt-file-path> --auto   # autonomous mode per ../AUTONOMY.md (see "--auto mode")
-/start_dev z_features/<epic>.md        # audit-only tracker mode (see reference.md)
 ```
 
 Prompts live under `<work-type>/<target>/` (first folder = work type, second =
@@ -73,10 +72,6 @@ Normalize the argument (strip whitespace/backticks/angle-brackets; if it's a
 markdown link `[label](path)`, take the path in the last `](…)`). Read
 `PyAutoMind/<normalized>`. If missing, report and list prompts in that folder.
 
-If the path starts with `z_features/`, switch to **audit-only tracker mode** —
-follow [`reference.md`](reference.md) → "z_features audit" and skip the rest of
-this flow (no issue is created).
-
 ### 2. Route through the Feature Agent (Brain + Memory)
 
 Hand the prompt to the Brain reasoning layer:
@@ -158,5 +153,5 @@ prompt_sync_push "prompt: route <task-name> (#<issue>) → <next-skill>"
 
 - Always present the issue body for review before creating it.
 - If `gh auth status` fails, tell the user to run `! gh auth login`.
-- Long-form detail (issue-body template, registry formats, z_features audit) is
-  in [`reference.md`](reference.md).
+- Long-form detail (issue-body template, registry formats) is in
+  [`reference.md`](reference.md).