@codewizard-dt/bootstrap 5.3.0 → 6.0.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.
- package/README.md +11 -3
- package/bin/cli.js +16 -0
- package/lib/hooks/README.md +124 -3
- package/lib/hooks/claude-settings-guard.js +8 -2
- package/lib/prompts/README.md +1 -1
- package/lib/prompts/migrate-wiki.md +7 -7
- package/lib/scripts/README.md +111 -10
- package/lib/scripts/bootstrap-prefs-tui.js +1222 -0
- package/lib/scripts/install-global.sh +137 -6
- package/lib/scripts/migrate-project.sh +52 -10
- package/lib/scripts/rename-wiki-ids.js +232 -0
- package/lib/scripts/templates/CLAUDE-wiki.md +6 -6
- package/lib/scripts/templates/bootstrap-prefs-schema.json +11 -2
- package/lib/scripts/templates/settings-sandbox-unattended.json +36 -0
- package/lib/scripts/templates/settings-sandbox.json +7 -0
- package/lib/scripts/templates/wiki/conventions.md +9 -9
- package/lib/scripts/templates/wiki/dashboard.html +527 -23
- package/lib/scripts/templates/wiki/index.md +2 -2
- package/lib/scripts/templates/wiki/work/bugs/lifecycle.md +1 -1
- package/lib/scripts/templates/wiki/work/decisions/index.md +12 -4
- package/lib/scripts/templates/wiki/work/decisions/lifecycle.md +11 -9
- package/lib/scripts/templates/wiki/work/requirements/index.md +12 -4
- package/lib/scripts/templates/wiki/work/requirements/lifecycle.md +8 -8
- package/lib/scripts/templates/wiki/work/roadmaps/index.md +11 -3
- package/lib/scripts/templates/wiki/work/roadmaps/lifecycle.md +7 -5
- package/lib/scripts/templates/wiki/work/tasks/index.md +1 -1
- package/lib/scripts/templates/wiki/work/tasks/lifecycle.md +16 -8
- package/lib/scripts/templates/wiki/work/uat/lifecycle.md +3 -3
- package/lib/scripts/wiki-dashboard-server.js +98 -0
- package/lib/skills/README.md +27 -22
- package/lib/skills/_shared/ARCHIVE-WORK-ITEM.md +103 -0
- package/lib/skills/_shared/ID-RESOLUTION.md +142 -0
- package/lib/skills/_shared/SKILL-BOILERPLATE.md +50 -0
- package/lib/skills/adr-assess/SKILL.md +112 -0
- package/lib/skills/{decision-create → adr-create}/SKILL.md +26 -26
- package/lib/skills/adr-deprecate/SKILL.md +190 -0
- package/lib/skills/adr-extract/SKILL.md +255 -0
- package/lib/skills/{decision-finalize → adr-finalize}/SKILL.md +38 -38
- package/lib/skills/{decision-next → adr-next}/SKILL.md +20 -19
- package/lib/skills/{decision-walkthrough → adr-walkthrough}/SKILL.md +23 -29
- package/lib/skills/architecture-audit/SKILL.md +1 -1
- package/lib/skills/autopilot/SKILL.md +110 -0
- package/lib/skills/bootstrap-config/SKILL.md +1 -1
- package/lib/skills/bug-assess/SKILL.md +3 -3
- package/lib/skills/bug-close/SKILL.md +13 -27
- package/lib/skills/{bug-file → bug-create}/SKILL.md +10 -14
- package/lib/skills/bug-triage/SKILL.md +5 -19
- package/lib/skills/demo/SKILL.md +1 -1
- package/lib/skills/extract-feature/SKILL.md +3 -3
- package/lib/skills/git-commit/SKILL.md +4 -4
- package/lib/skills/port-feature/SKILL.md +3 -3
- package/lib/skills/power-mode/SKILL.md +42 -49
- package/lib/skills/prd-assess/SKILL.md +105 -0
- package/lib/skills/{req-compile → prd-compile}/SKILL.md +6 -13
- package/lib/skills/{req-create → prd-create}/SKILL.md +19 -19
- package/lib/skills/prd-deprecate/SKILL.md +173 -0
- package/lib/skills/{req-finalize → prd-finalize}/SKILL.md +20 -29
- package/lib/skills/primer/SKILL.md +2 -2
- package/lib/skills/research/SKILL.md +3 -3
- package/lib/skills/roadmap-assess/SKILL.md +20 -20
- package/lib/skills/roadmap-create/SKILL.md +19 -29
- package/lib/skills/roadmap-next/SKILL.md +16 -28
- package/lib/skills/security-audit/SKILL.md +1 -1
- package/lib/skills/tackle/SKILL.md +13 -15
- package/lib/skills/{task-audit → task-assess}/SKILL.md +34 -44
- package/lib/skills/task-close/SKILL.md +73 -0
- package/lib/skills/{task-add → task-create}/SKILL.md +25 -24
- package/lib/skills/uat-assess/SKILL.md +124 -0
- package/lib/skills/uat-auto/SKILL.md +9 -7
- package/lib/skills/uat-auto-plus/SKILL.md +2 -2
- package/lib/skills/{uat-generate → uat-create}/SKILL.md +10 -12
- package/lib/skills/uat-skip/SKILL.md +5 -9
- package/lib/skills/uat-walk/SKILL.md +2 -2
- package/lib/skills/uat-walk/UAT-CORE.md +29 -16
- package/lib/skills/update-docs/SKILL.md +1 -1
- package/lib/skills/usage-report/SKILL.md +52 -0
- package/lib/skills/usage-report/scripts/pricing.json +22 -0
- package/lib/skills/usage-report/scripts/usage-report.js +518 -0
- package/lib/skills/whats-next/SKILL.md +177 -0
- package/lib/skills/wiki-archive/SKILL.md +12 -23
- package/lib/skills/wiki-lint/SKILL.md +23 -13
- package/lib/skills/wiki-query/SKILL.md +1 -1
- package/lib/skills/wiki-rotate-log/SKILL.md +1 -1
- package/lib/skills/wiki-tidy/SKILL.md +6 -9
- package/package.json +1 -1
- package/lib/scripts/templates/wiki/work/decisions/archive/index.md +0 -10
- package/lib/scripts/templates/wiki/work/requirements/archive/index.md +0 -10
- package/lib/scripts/templates/wiki/work/roadmaps/archive/index.md +0 -10
- package/lib/skills/req-extract-decisions/SKILL.md +0 -241
- package/lib/skills/req-retire/SKILL.md +0 -185
- package/lib/skills/req-update/SKILL.md +0 -265
- package/lib/skills/task-trash/SKILL.md +0 -115
- package/lib/skills/task-update/SKILL.md +0 -136
|
@@ -0,0 +1,177 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: whats-next
|
|
3
|
+
description: Survey ALL open work — tasks (in or out of a roadmap), UATs, bugs, roadmaps, ADR blocks and PRDs — and rank one prioritized do-next list with parallel waves (read-only)
|
|
4
|
+
category: researching
|
|
5
|
+
model: claude-sonnet-5
|
|
6
|
+
disable-model-invocation: false
|
|
7
|
+
user-invocable: true
|
|
8
|
+
argument-hint: "[--limit N] [--family tasks,bugs,uat,roadmaps,adr,prd]"
|
|
9
|
+
---
|
|
10
|
+
**Prereqs:** obey `wiki/guides/mcp-tools.md` + `wiki/work/tasks/lifecycle.md`; run /primer if not done this session.
|
|
11
|
+
|
|
12
|
+
# What's Next
|
|
13
|
+
|
|
14
|
+
Answer "what should I do next?" across every work family at once — this is the cross-family counterpart to the per-family `*-assess` skills (`/roadmap-assess`, `/uat-assess`, `/adr-assess`, `/prd-assess`, `/bug-assess`, `/task-assess`), each of which sees only its own family, and to `/roadmap-next` and `/power-mode`, which only see work that sits inside a roadmap. Use this skill first when you want one ordered list of the next actions regardless of where an item lives.
|
|
15
|
+
|
|
16
|
+
This skill is strictly read-only: it never runs a case, never flips a status, never creates or edits a file, never asks questions, and never calls the `*-assess` skills (their side effects and prompts are exactly what it avoids). Acting on an item is the job of the command named in its `Next` cell.
|
|
17
|
+
|
|
18
|
+
Arguments: `--limit N` caps each wave (default 5); `--family <list>` restricts the sweep and the report to the named families (`tasks`, `bugs`, `uat`, `roadmaps`, `adr`, `prd`) — the graph still reads every task so dependency depth stays correct.
|
|
19
|
+
|
|
20
|
+
---
|
|
21
|
+
|
|
22
|
+
## Step 1: Discover & sweep
|
|
23
|
+
|
|
24
|
+
Read the Family table in `lib/skills/_shared/ID-RESOLUTION.md` for each family's directory and ID prefix — do not hardcode them. Both 3- and 4-digit IDs and the legacy `REQ-` / `DEC-` prefixes coexist until migrated, so match every width and prefix the table names.
|
|
25
|
+
|
|
26
|
+
**Sweep by frontmatter, never by index text.** Family `index.md` files go stale (a roadmap index can read 0/9 while its file has nine checked links), so they are consulted only for the index-drift warning in Step 5e. Run **one** `search_for_pattern` per family, pulling just the frontmatter lines you need, and `Read` a file in full only when its fields are not enough. Decide active vs. closed from each item's `status:` per that family's `lifecycle.md`, never from the directory it sits in.
|
|
27
|
+
|
|
28
|
+
Concrete example — the tasks sweep:
|
|
29
|
+
|
|
30
|
+
- `substring_pattern`: `^(id|title|status|created|updated|depends_on|blocks|uat):[^\n]*`
|
|
31
|
+
- `paths_include_glob`: `wiki/work/tasks/TASK-*.md`
|
|
32
|
+
- `paths_exclude_glob`: `wiki/work/tasks/archive/**`
|
|
33
|
+
|
|
34
|
+
Serena pitfalls, all verified — get these wrong and the sweep silently returns nothing or floods the context:
|
|
35
|
+
|
|
36
|
+
- Use `[^\n]*`, never `.*`. Multiline is on by default and `.` then matches newlines, so `^status:.*` swallowed whole files (459,518 characters on this repo).
|
|
37
|
+
- Never pass `multiline=false` together with `^` anchors — it returns `{}`.
|
|
38
|
+
- `paths_include_glob` needs the full repo-relative path (`wiki/work/tasks/TASK-*.md`, not `TASK-*.md`), or it matches nothing.
|
|
39
|
+
- Exclude `archive/` (pass the `paths_exclude_glob` above). Archived items still carry stale open-looking state — archived ROADMAP-009 still shows an unchecked `[[TASK-073]]`. Roadmaps, decisions and requirements no longer archive; skip any legacy `archive/` directory under them too.
|
|
40
|
+
|
|
41
|
+
Per-family recipe (same pitfalls apply to each):
|
|
42
|
+
|
|
43
|
+
| Family | Pattern (frontmatter lines) | Active means |
|
|
44
|
+
|--------|-----------------------------|--------------|
|
|
45
|
+
| tasks | as above | `todo`, `in-progress`, `pending-uat` |
|
|
46
|
+
| uat | `^(id\|title\|status\|task\|created):[^\n]*` plus `^\s*### UAT-[^\n]*` and each case's marker line, over `wiki/work/uat/UAT-*.md` | `pending`, `in-progress`, `failed` |
|
|
47
|
+
| bugs | `^(id\|title\|status\|severity\|priority\|created\|updated):[^\n]*` over `wiki/work/bugs/BUG-*.md` | `open`, `triaged`, `in-progress` |
|
|
48
|
+
| roadmaps | `^(id\|status):[^\n]*` plus `^\s*- \[[ x]\][^\n]*` over `wiki/work/roadmaps/ROADMAP-*.md` | `status: active` |
|
|
49
|
+
| adr | `^(id\|status\|## D\d+[^\n]*)[^\n]*` and each block's `Status:` line over `wiki/work/decisions/ADR-*.md` and legacy `DEC-*.md` | blocks `proposed`; `accepted` blocks with no task |
|
|
50
|
+
| prd | `^(id\|title\|status\|updated):[^\n]*` over `wiki/work/requirements/PRD-*.md` and legacy `REQ-*.md` | `draft`, `approved` |
|
|
51
|
+
|
|
52
|
+
For roadmaps, follow the **Parse a roadmap** procedure in `lib/skills/roadmap-next/SKILL.md` as written — do not restate it. Run only that procedure: never its Upgrade-inline-items, Parallelism-analysis or Close-a-fully-complete-roadmap procedures, which write files. The procedure's 9-item cap applies to its candidate list only; keep the full `total` / `done` counts. A roadmap item that links a task adds no row of its own — the task's row (from the tasks sweep) carries a `Roadmap` display value; an unchecked `inline` item becomes an inline-item row.
|
|
53
|
+
|
|
54
|
+
For the per-family status vocabularies and terminal states, read each family's `lifecycle.md` rather than assuming them. For a UAT, count a case as unit-backed when it carries a `Unit Test Command` line or a `Repeatable Unit Test: Created` line, otherwise manual-only (reading the line is enough — never run it). For a bug, take `severity` and `priority` as written; `priority: "—"` means untriaged. For ADR blocks and PRDs, take in-family precedence and the accepted-without-task / approved-without-downstream checks from `lib/skills/adr-assess/SKILL.md` and `lib/skills/prd-assess/SKILL.md` — do not restate them.
|
|
55
|
+
|
|
56
|
+
Apply `--family` after the sweep, when choosing which rows to report.
|
|
57
|
+
|
|
58
|
+
**An empty sweep against a non-empty family index is a WARNING, not "no work".** Before trusting a zero-hit family, `Read` its `index.md` (or `list_dir` the directory): if the index or directory lists items the sweep did not see, re-check the glob and pattern against the pitfalls above, and record an empty-sweep warning for Step 5e. Only when every family is genuinely empty, STOP: `No open work found — nothing to rank. Use /task-create, /bug-create or /roadmap-create to add some.`
|
|
59
|
+
|
|
60
|
+
## Step 2: Build the graph
|
|
61
|
+
|
|
62
|
+
Nodes are the active tasks, plus bugs, ADR blocks, PRDs and roadmap items where they take part in an edge. For each task, build its dependency edges from the **union** of its own `depends_on` (frontmatter and `depends_on::[[TASK-NNNN]]` links) and the reverse of every other task's `blocks`. Resolve each referenced ID per the masks in `lib/skills/_shared/ID-RESOLUTION.md` (both widths).
|
|
63
|
+
|
|
64
|
+
**Start-satisfied vs. close-satisfied.** A `depends_on` edge is *start-satisfied* when the prerequisite is `pending-uat` or `done`, or has left the active set as terminal (`trashed`). It is *close-satisfied* only when the prerequisite is `done`. A task whose prerequisite is `pending-uat` may be started but is flagged **soft-blocked for closure** — it cannot reach `done` until that prerequisite's UAT is run. A task with any prerequisite that is not start-satisfied is **blocked**.
|
|
65
|
+
|
|
66
|
+
Detect and record for Step 5e:
|
|
67
|
+
|
|
68
|
+
- **Asymmetric edges** — task A lists B in `depends_on` but B lacks A in `blocks`, or the reverse. Report each pair as `A ← B (no matching blocks)`.
|
|
69
|
+
- **Cycles** — walk the graph via DFS; report each cycle as `TASK-A → TASK-B → TASK-A`. Never silently pick a winner; exclude cycle members from the actionable tiers and list them under Blocked.
|
|
70
|
+
- **Stale references** — an edge to an ID that resolves to no file, or to a `trashed` item that never left the edge list.
|
|
71
|
+
|
|
72
|
+
Compute for every node: `downstream_depth` (length of the longest chain of dependents that transitively waits on it) and `fan_out` (count of direct dependents). Also link the other families where a real edge exists: a `pending-uat` task to its UAT (`uat:` field, else the UAT whose `task:` points back), a proposed ADR block to the roadmaps, PRDs and tasks that reference it (its gated count), an approved PRD to any downstream ADR or task, a bug to the task that fixes it (`origin_bug:` on tasks). A UAT or ADR block that gates a task adds to that item's `fan_out` and `downstream_depth`.
|
|
73
|
+
|
|
74
|
+
## Step 3: Rank
|
|
75
|
+
|
|
76
|
+
Ranking is a **deterministic lexicographic sort over tiers, never a numeric score** — tasks carry no priority or effort field and bugs are mostly untriaged, so a score would be false precision. Assign every actionable item to the first tier it fits, highest priority first:
|
|
77
|
+
|
|
78
|
+
| Tier | Name | Items |
|
|
79
|
+
|------|------|-------|
|
|
80
|
+
| 1 | Fix what's broken | bugs `in-progress`; bugs triaged P0 or P1; bugs with `severity: critical` |
|
|
81
|
+
| 2 | Finish what's started | tasks `in-progress`; tasks `pending-uat` (run the UAT); untriaged bugs as **one batch row**, promoted here only when any of them is `high` or `critical` |
|
|
82
|
+
| 3 | Unblock | proposed ADR blocks that gate live work; approved PRDs with no downstream ADR or task |
|
|
83
|
+
| 4 | Start ready work | `todo` tasks whose `depends_on` edges are all start-satisfied; unchecked inline roadmap items; accepted ADR blocks with no task |
|
|
84
|
+
| 5 | Triage & hygiene | untriaged bugs (as one batch row when not promoted), stale drafts, fully-checked roadmaps awaiting close, index drift |
|
|
85
|
+
|
|
86
|
+
Then a separate **Blocked** list — items with an unsatisfied `depends_on` edge, cycle members, and roadmaps gated on a proposed decision — listed with what each waits on and **never ranked as actionable**.
|
|
87
|
+
|
|
88
|
+
**Within a tier**, order by: `downstream_depth` descending, `fan_out` descending, age ascending (oldest `created` first), then ID ascending. For in-family precedence that this table does not decide (which proposed block or draft PRD first, stale-draft and long-idle thresholds), follow the **Rank** step of the matching family skill — `lib/skills/adr-assess/SKILL.md`, `lib/skills/prd-assess/SKILL.md`, `lib/skills/uat-assess/SKILL.md`, `lib/skills/bug-assess/SKILL.md` — without restating it here.
|
|
89
|
+
|
|
90
|
+
**Roadmap membership is a display column, not a ranking input.** An orphan task (in no active roadmap) ranks exactly as if it were in one; otherwise orphans starve behind roadmap work. Count the orphans and suggest adopting them into a roadmap in Step 5e.
|
|
91
|
+
|
|
92
|
+
Record a one-sentence `Why` per item — a judgment call the user can override, not a fact.
|
|
93
|
+
|
|
94
|
+
## Step 4: Waves
|
|
95
|
+
|
|
96
|
+
Build parallel waves from Tier 1-4 items in the **task pipeline** (tasks, plus the UAT runs of `pending-uat` tasks), skipping bug batches, ADR, PRD and roadmap rows. **Wave 1** is the highest-ranked items with no dependency edge between any two of them and every prerequisite start-satisfied; **Wave 2** is the next set that becomes ready once Wave 1 is done (their only unmet edges point into Wave 1). Cap each wave at `--limit N` items, default 5, in rank order; note the overflow count. Omit Wave 3+.
|
|
97
|
+
|
|
98
|
+
Waves rest on graph edges only. Collision-safety beyond the graph (shared files, overlapping edits) is `/power-mode`'s own protocol at execution time — do not try to predict it here.
|
|
99
|
+
|
|
100
|
+
## Step 5: Report
|
|
101
|
+
|
|
102
|
+
Print, in this order, with no preamble:
|
|
103
|
+
|
|
104
|
+
### 5a. Snapshot
|
|
105
|
+
|
|
106
|
+
One line per family: `<family>: <active> active (<by-state counts>)`. Then a WIP-by-state histogram over all active tasks and UATs, one row per state (`todo`, `in-progress`, `pending-uat`, UAT `pending` / `in-progress` / `failed`) with a count and a bar, so a bottleneck concentrated in one state is visible at a glance.
|
|
107
|
+
|
|
108
|
+
### 5b. Waves
|
|
109
|
+
|
|
110
|
+
```
|
|
111
|
+
## Wave 1 (parallel)
|
|
112
|
+
- TASK-NNNN — <title> → `/tackle wiki/work/tasks/TASK-NNNN-slug.md`
|
|
113
|
+
## Wave 2 (after Wave 1)
|
|
114
|
+
- TASK-MMMM — <title> → `/uat-auto wiki/work/uat/UAT-MMMM-slug.md`
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
Each line carries the copy-pasteable `Next` command for that item.
|
|
118
|
+
|
|
119
|
+
### 5c. Ranked table
|
|
120
|
+
|
|
121
|
+
```
|
|
122
|
+
## Ranked
|
|
123
|
+
|
|
124
|
+
| Rank | Item | Family | Roadmap | Why | Unblocks | Next |
|
|
125
|
+
|------|------|--------|---------|-----|----------|------|
|
|
126
|
+
| 1 | TASK-NNNN — <title> | task | ROADMAP-NNNN or — | <one sentence> | TASK-MMMM, TASK-PPPP | `/tackle <path>` |
|
|
127
|
+
```
|
|
128
|
+
|
|
129
|
+
Rank runs 1..N across tiers in order (state the tier in `Why`). `Roadmap` is the display column — `—` for an orphan. `Unblocks` lists the direct dependents and gated items.
|
|
130
|
+
|
|
131
|
+
`Next` by item state — every command below is a real skill; name only these:
|
|
132
|
+
|
|
133
|
+
- task `in-progress` or `todo` → `/tackle <path>`
|
|
134
|
+
- task `pending-uat`, UAT exists → `/uat-auto <uat>` when every unresolved case is unit-backed, otherwise `/uat-walk <uat>`
|
|
135
|
+
- task `pending-uat`, no UAT yet → `/uat-create <task>`
|
|
136
|
+
- bug `open` → `/bug-assess` (the batch row) or `/bug-triage BUG-NNNN` (a single bug)
|
|
137
|
+
- bug `triaged` → `/bug-triage BUG-NNNN` or `/task-create <description>`
|
|
138
|
+
- bug `in-progress` → `/bug-close BUG-NNNN`
|
|
139
|
+
- proposed ADR block → `/adr-finalize <file>#DM`
|
|
140
|
+
- accepted ADR block with no task → `/task-create --decision ADR-NNNN#DM`
|
|
141
|
+
- approved PRD with no downstream → `/adr-extract <file>`
|
|
142
|
+
- draft PRD → `/prd-finalize <file>`
|
|
143
|
+
- roadmap with every item checked → `/roadmap-next <roadmap>`
|
|
144
|
+
- inline roadmap item → `/roadmap-next <roadmap>`
|
|
145
|
+
|
|
146
|
+
### 5d. Blocked
|
|
147
|
+
|
|
148
|
+
```
|
|
149
|
+
## Blocked
|
|
150
|
+
|
|
151
|
+
- TASK-NNNN — <title> — waits on TASK-MMMM (<state>), ADR-NNNN#DM (proposed)
|
|
152
|
+
```
|
|
153
|
+
|
|
154
|
+
List each blocked item with exactly what it waits on. Also list soft-blocked-for-closure tasks here (started, but waiting on a prerequisite's UAT).
|
|
155
|
+
|
|
156
|
+
### 5e. Warnings (omit if none found)
|
|
157
|
+
|
|
158
|
+
Flag, each as its own short block:
|
|
159
|
+
|
|
160
|
+
- dependency cycles and asymmetric edges from Step 2 (name the pairs);
|
|
161
|
+
- stale references and broken links;
|
|
162
|
+
- index drift — a family `index.md` whose listing disagrees with the frontmatter sweep;
|
|
163
|
+
- the **orphan count** — `N of M active tasks sit outside every active roadmap` — with a suggestion to adopt them via `/roadmap-create`;
|
|
164
|
+
- **empty-sweep suspicion** — any family whose sweep returned nothing while its index or directory shows items (see Step 1).
|
|
165
|
+
|
|
166
|
+
Footer, when any closed item was excluded: `Closed: N (not assessed)`.
|
|
167
|
+
|
|
168
|
+
---
|
|
169
|
+
|
|
170
|
+
## Constraints
|
|
171
|
+
|
|
172
|
+
- Read-only — no exception. No file edits, no shell, no prompts, no log or index changes, no status flips. The commands in each `Next` cell are the follow-up actions the user runs once they act on this report.
|
|
173
|
+
- Permitted tools: `list_dir`, `find_file`, `search_for_pattern`, `Read`.
|
|
174
|
+
- Never bash reads (`cat`/`find`/`grep`/`sed`/`ls`).
|
|
175
|
+
- Never run a case's `Unit Test Command` — ranking is not executing; `/uat-auto` and `/uat-walk` do that.
|
|
176
|
+
- Handing a whole wave to `/power-mode` awaits a task-ID-list dispatch there; until then the report prints one copy-pasteable command per item.
|
|
177
|
+
- Keep the report terse — no preamble, no closing summary beyond the sections above.
|
|
@@ -1,13 +1,13 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: wiki-archive
|
|
3
|
-
description: Cleanup tool — sweep
|
|
3
|
+
description: Cleanup tool — sweep tasks, UAT and bugs with terminal status that were not auto-archived by their originating skill, and move them to archive/ (roadmaps, decisions and requirements close in place)
|
|
4
4
|
category: wiki
|
|
5
5
|
model: claude-sonnet-5
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# Wiki Archive
|
|
9
9
|
|
|
10
|
-
> **Recovery sweep.** Skills that set terminal statuses (`uat-auto`, `uat-skip`, `bug-close`, etc.)
|
|
10
|
+
> **Recovery sweep.** Skills that set terminal statuses on tasks, UAT and bugs (`uat-auto`, `uat-skip`, `bug-close`, etc.) automatically move files to `archive/` at the time of completion. This skill finds any items that were missed — for example, items from before the auto-archive update, or edge cases where the originating skill didn't complete the move. In a healthy wiki, this skill finds nothing to do. Roadmaps, decisions and requirements are **not** swept: they close in place (see Step 1).
|
|
11
11
|
|
|
12
12
|
Move terminal work items from a family directory into `archive/` to reduce directory clutter. **Terminal items only** — items with active statuses are never moved. Safe because links use stable IDs, not paths.
|
|
13
13
|
|
|
@@ -19,28 +19,29 @@ Move terminal work items from a family directory into `archive/` to reduce direc
|
|
|
19
19
|
/wiki-archive [family]
|
|
20
20
|
```
|
|
21
21
|
|
|
22
|
-
`family` — one of `tasks`, `uat`, `bugs
|
|
22
|
+
`family` — one of `tasks`, `uat`, `bugs`. Omit to show a count summary across those three families without moving anything. If `family` is `roadmaps`, `decisions` or `requirements`, report `Roadmaps, decisions and requirements are closed in place (Closed section of the family index) — nothing to archive.` and STOP.
|
|
23
23
|
|
|
24
24
|
---
|
|
25
25
|
|
|
26
26
|
## Step 1: Determine scope
|
|
27
27
|
|
|
28
|
-
If a family was specified, process only that family. Otherwise, scan
|
|
28
|
+
If a family was specified, process only that family (validate it per Usage). Otherwise, scan the 3 archiving families (`tasks`, `uat`, `bugs`) and report terminal item counts, then ask the user which families to archive.
|
|
29
29
|
|
|
30
30
|
For each family to process, read its `lifecycle.md` to confirm the **terminal statuses** for that family:
|
|
31
31
|
- **tasks**: `done`, `trashed`
|
|
32
32
|
- **uat**: `passed`, `skipped`, `trashed`
|
|
33
33
|
- **bugs**: `closed`, `wontfix`, `duplicate`, `cannot-reproduce`
|
|
34
|
-
- **requirements**: `retired`
|
|
35
|
-
- **decisions**: all decisions in the group are `accepted` or `superseded`
|
|
36
|
-
- **roadmaps**: `done`
|
|
37
34
|
|
|
38
|
-
|
|
35
|
+
Roadmaps, decisions and requirements are never swept: they close in place, with the family `index.md` moving the row from `## Active` to `## Closed` (see `~/.claude/skills/_shared/ARCHIVE-WORK-ITEM.md` § In-place close). Items closed by `prd-deprecate` / `adr-deprecate` are status-only and stay in place (no archive move), exactly like every other closed roadmap, decision and requirement.
|
|
36
|
+
|
|
37
|
+
**Stray-archive note.** In a sweep with no family argument, also check whether `wiki/work/roadmaps/archive/`, `wiki/work/decisions/archive/` or `wiki/work/requirements/archive/` still exists and is non-empty (`mcp__serena__list_dir`). If so, do not move anything — report `wiki/work/<family>/archive/ is a leftover from the old archive model — run npx @codewizard-dt/bootstrap update to migrate`.
|
|
38
|
+
|
|
39
|
+
Do NOT hardcode the terminal statuses — read `lifecycle.md` to confirm them before moving anything.
|
|
39
40
|
|
|
40
41
|
## Step 2: Identify terminal items
|
|
41
42
|
|
|
42
43
|
Use `mcp__serena__list_dir` on the family directory. For each file (excluding `lifecycle.md`, `index.md`, `.gitkeep`, and everything under `archive/`):
|
|
43
|
-
1. Read the file's `status:` frontmatter field
|
|
44
|
+
1. Read the file's `status:` frontmatter field.
|
|
44
45
|
2. If the status is terminal → add to the move list.
|
|
45
46
|
3. If the status is active → skip; never touch it.
|
|
46
47
|
|
|
@@ -62,16 +63,7 @@ Wait for confirmation before moving.
|
|
|
62
63
|
|
|
63
64
|
## Step 4: Move files and update archive/index.md
|
|
64
65
|
|
|
65
|
-
|
|
66
|
-
1. Use `Bash` with `mv` to move the file: `mv wiki/work/<family>/<file> wiki/work/<family>/archive/<file>`
|
|
67
|
-
2. Read the file's `id`, `title`, `status`, and `updated` frontmatter fields.
|
|
68
|
-
3. Append a row to `wiki/work/<family>/archive/index.md`:
|
|
69
|
-
```
|
|
70
|
-
| [[ID]] | Title | final-status | YYYY-MM-DD |
|
|
71
|
-
```
|
|
72
|
-
where the date is today's date.
|
|
73
|
-
|
|
74
|
-
Do NOT edit the moved file itself — its frontmatter and content are preserved exactly.
|
|
66
|
+
Read `~/.claude/skills/_shared/ARCHIVE-WORK-ITEM.md` now and run its Procedure once per confirmed file: `terminal_status` is the file's existing `status:`, `log: skip` (Step 5 writes the single batch entry).
|
|
75
67
|
|
|
76
68
|
## Step 5: Update wiki/log.md
|
|
77
69
|
|
|
@@ -90,7 +82,4 @@ Print a summary of what was moved. If any files were skipped (e.g., active statu
|
|
|
90
82
|
## CRITICAL rules
|
|
91
83
|
|
|
92
84
|
- **Never move an active item.** If a file's status is not in the terminal set for its family, skip it and warn.
|
|
93
|
-
-
|
|
94
|
-
- **Never delete** — archiving is moving, not deleting.
|
|
95
|
-
- **`archive/index.md` is append-only** — only add rows, never remove or edit existing rows.
|
|
96
|
-
- The `archive/` directory already exists in every family — do not create it.
|
|
85
|
+
- Move mechanics and their invariants: ARCHIVE-WORK-ITEM.md.
|
|
@@ -28,7 +28,7 @@ Build a complete file list.
|
|
|
28
28
|
|
|
29
29
|
### 2.0 Stranded terminal files (HIGH)
|
|
30
30
|
|
|
31
|
-
For each work family, scan the active directory (excluding `lifecycle.md`, `index.md`, `.gitkeep`, and anything under `archive/`). For each file, read its `status:` frontmatter. If the status is in the terminal set for that family (read each family's `lifecycle.md` — do NOT hardcode), report it as a stranded file.
|
|
31
|
+
For each **archiving** work family (`tasks`, `uat`, `bugs` only), scan the active directory (excluding `lifecycle.md`, `index.md`, `.gitkeep`, and anything under `archive/`). For each file, read its `status:` frontmatter. If the status is in the terminal set for that family (read each family's `lifecycle.md` — do NOT hardcode), report it as a stranded file. Roadmaps, decisions and requirements close in place — a terminal file in those families is correct where it is and is never reported here (check 2.1 verifies its index section instead).
|
|
32
32
|
|
|
33
33
|
Report format:
|
|
34
34
|
```
|
|
@@ -41,21 +41,29 @@ These should have been auto-archived by the skill that set the terminal status.
|
|
|
41
41
|
|
|
42
42
|
### 2.1 Family-index drift (HIGH)
|
|
43
43
|
|
|
44
|
-
For each work family (`requirements`, `decisions`, `roadmaps`, `tasks`, `uat`, `bugs`):
|
|
44
|
+
For each work family (`requirements`, `decisions`, `roadmaps`, `tasks`, `uat`, `bugs`), branching on how the family closes items:
|
|
45
|
+
|
|
46
|
+
**Archiving families (`tasks`, `uat`, `bugs`):**
|
|
45
47
|
1. Read the family's `index.md`.
|
|
46
48
|
2. For each row in the index: verify the linked file exists in the family directory; verify the file's `status:` frontmatter matches an **active** status for that family (read each family's `lifecycle.md` for the valid active statuses — do NOT hardcode them).
|
|
47
49
|
3. For each file in the family directory (excluding `lifecycle.md`, `index.md`, `.gitkeep`, and anything under `archive/`): read its `status:` frontmatter; if the status is **not** in the active set, verify its row is absent from the active index. Files in `archive/` are terminal by definition — they should not appear in the active `index.md` but their presence in `archive/` is correct.
|
|
48
50
|
|
|
51
|
+
**In-place families (`requirements`, `decisions`, `roadmaps`):** finished items stay in the family directory and the family `index.md` moves the row from `## Active` to `## Closed`.
|
|
52
|
+
1. Read the family's `index.md`; each row must link to an existing file in the family directory.
|
|
53
|
+
2. For each file in the family directory (excluding `lifecycle.md`, `index.md`, `.gitkeep`): read its `status:` frontmatter (for decisions, a group is Active while any block is `proposed`, otherwise Closed) and verify its row sits in the right section — `## Active` for active statuses, `## Closed` for terminal ones (read each family's `lifecycle.md`; do NOT hardcode) — and is absent from the wrong one.
|
|
54
|
+
3. If `wiki/work/<family>/archive/` still exists and is non-empty, report it as `[MEDIUM] un-migrated archive/` — informational, leftover from the old archive model; the fix is `npx @codewizard-dt/bootstrap update`, not a manual move.
|
|
55
|
+
|
|
49
56
|
Report:
|
|
50
|
-
- Active item missing from index
|
|
51
|
-
- Non-active item still listed in index
|
|
57
|
+
- Active item missing from index (or in-place item missing from its correct section)
|
|
58
|
+
- Non-active item still listed in index (or in-place item listed in the wrong section)
|
|
52
59
|
- Index row pointing at a missing file
|
|
60
|
+
- `[MEDIUM] un-migrated archive/ — wiki/work/<family>/archive/ still holds N files (run npx @codewizard-dt/bootstrap update to migrate)`
|
|
53
61
|
|
|
54
62
|
### 2.2 Two-domain violations (HIGH)
|
|
55
63
|
|
|
56
64
|
- Any file under `wiki/knowledge/` that has a `status:` frontmatter key (stateful artifacts don't belong in knowledge)
|
|
57
65
|
- Any file under `wiki/work/` that lacks a `status:` frontmatter key (work artifacts must be status-driven)
|
|
58
|
-
- Any file under `wiki/knowledge/` whose name matches a work-family ID pattern (REQ-NNNN, TASK-NNNN, BUG-NNNN, etc.)
|
|
66
|
+
- Any file under `wiki/knowledge/` whose name matches a work-family ID pattern (PRD-NNNN, REQ-NNNN, TASK-NNNN, BUG-NNNN, etc.)
|
|
59
67
|
|
|
60
68
|
### 2.3 ID / filename mismatch (MEDIUM)
|
|
61
69
|
|
|
@@ -109,31 +117,33 @@ Report-only — provenance is a human judgment (whether a page is genuinely `inf
|
|
|
109
117
|
|
|
110
118
|
### 2.11 Typed-link target resolution (MEDIUM)
|
|
111
119
|
|
|
112
|
-
|
|
120
|
+
Reuse the `::[[` scan from 2.5 (`mcp__serena__search_for_pattern` across `wiki/`) rather than running a second scanner — 2.5 validates the keyword before `::` (vocabulary in `wiki/conventions.md` §3); this check validates the target after it. For each `keyword::[[target]]` match, resolve the target to confirm it exists:
|
|
113
121
|
|
|
114
122
|
**Resolution logic:**
|
|
115
|
-
- **Decision targets** (`DEC-NNNN` or `DEC-NNNN#DM`): Confirm the file exists in `wiki/work/decisions/` or `wiki/work/decisions/archive
|
|
116
|
-
- **Work-family targets** (`TASK-NNNN`, `BUG-NNNN`, `UAT-NNNN`, `REQ-NNNN`, `ROADMAP-NNNN`): Confirm the file exists in the respective family directory (`wiki/work/<family>/`) or `wiki/work/<family>/archive
|
|
117
|
-
- **Knowledge page targets** (bare slugs, e.g. `[[typed-wiki-links]]`): Confirm a page with a matching `id:` or entry in `aliases:` frontmatter exists under `wiki/knowledge/`.
|
|
123
|
+
- **Decision targets** (`ADR-NNNN` or `ADR-NNNN#DM`, plus legacy `DEC-NNNN` or `DEC-NNNN#DM` until migrated — the number, not the prefix, selects the file): Confirm the file exists in `wiki/work/decisions/` or, for legacy un-migrated wikis, `wiki/work/decisions/archive/` (`mcp__serena__find_file`). If a `#DM` anchor is present, confirm that decision block exists in the file — an H2 matching `## DM.` (e.g. `## D2.`) with a `- **Status**: <status>` line.
|
|
124
|
+
- **Work-family targets** (`TASK-NNNN`, `BUG-NNNN`, `UAT-NNNN`, `PRD-NNNN`, `REQ-NNNN`, `ROADMAP-NNNN`): Confirm the file exists in the respective family directory (`wiki/work/<family>/`) or `wiki/work/<family>/archive/` (`mcp__serena__find_file`; `archive/` is the normal location only for `tasks`, `uat` and `bugs` — for the other families it is a legacy-tolerance fallback).
|
|
125
|
+
- **Knowledge page targets** (bare slugs, e.g. `[[typed-wiki-links]]`): Confirm a page with a matching `id:` or entry in `aliases:` frontmatter, or a matching filename, exists under `wiki/knowledge/`.
|
|
118
126
|
|
|
119
127
|
**Reporting:**
|
|
120
128
|
- **Unresolved targets** — report as `[MEDIUM] dangling typed link — <file>:<line> — <keyword>::[[<target>]] does not resolve to any existing page or work item`.
|
|
121
|
-
- **Superseded decision targets** — if a target resolves to a decision block
|
|
129
|
+
- **Superseded decision targets** — if a target resolves to a decision block whose status is `superseded by ADR-N#DX` (or legacy `superseded by DEC-N#DX`), report separately as `[LOW] typed link to superseded decision — <file>:<line> — consider updating to ADR-N#DX` (informational, not broken; the link still resolves).
|
|
122
130
|
|
|
123
131
|
### 2.12 Task-less accepted decisions (MEDIUM)
|
|
124
132
|
|
|
125
|
-
For each decision file in `wiki/work/decisions/` (excluding `lifecycle.md`; include `archive/`), parse every `## D*` decision block — each H2 matching `## D\d+\.` is a decision block, collected in document order. For each block:
|
|
133
|
+
For each decision file in `wiki/work/decisions/` (excluding `lifecycle.md`; include `archive/` for legacy un-migrated wikis), parse every `## D*` decision block — each H2 matching `## D\d+\.` is a decision block, collected in document order. For each block:
|
|
126
134
|
|
|
127
135
|
- Skip unless `Status: accepted` — only accepted decisions need a follow-up task; skip `proposed`, `deprecated`, `superseded by …`.
|
|
128
136
|
- A decision is task-less if its `### Links` section is absent, or has no `Source task(s):` line, or the `Source task(s):` line is blank / contains only a placeholder (e.g. "none yet").
|
|
129
137
|
|
|
130
|
-
Unlike `/
|
|
138
|
+
Unlike `/adr-next` (which stops at the first gap), report **every** task-less accepted decision found across all decision files — matching this skill's "report all, fix none without approval" contract.
|
|
131
139
|
|
|
132
140
|
Report format:
|
|
133
141
|
```
|
|
134
|
-
[MEDIUM] task-less accepted decision —
|
|
142
|
+
[MEDIUM] task-less accepted decision — ADR-NNNN#DM (<title>) has no Source task(s) link
|
|
135
143
|
```
|
|
136
144
|
|
|
145
|
+
Report each file's own `id:` in place of `ADR-NNNN` (a not-yet-migrated file reports its legacy `DEC-NNNN`).
|
|
146
|
+
|
|
137
147
|
## Step 3: Report findings
|
|
138
148
|
|
|
139
149
|
Group by severity (HIGH / MEDIUM / LOW). For each finding:
|
|
@@ -90,7 +90,7 @@ Worth filing this answer as a new wiki page?
|
|
|
90
90
|
Target: wiki/knowledge/concepts/<concept-slug>.md
|
|
91
91
|
```
|
|
92
92
|
|
|
93
|
-
**Never file stateful work artifacts here** — requirements, decisions, tasks, bugs belong in `wiki/work/` and are created by their own skills (`/
|
|
93
|
+
**Never file stateful work artifacts here** — requirements, decisions, tasks, bugs belong in `wiki/work/` and are created by their own skills (`/prd-create`, `/adr-create`, etc.).
|
|
94
94
|
|
|
95
95
|
If the user says yes:
|
|
96
96
|
1. Create `wiki/knowledge/concepts/<concept-slug>.md` with proper frontmatter (`id`, `title`, `updated`, `tags`, `sources` if derived from a raw source).
|
|
@@ -59,7 +59,7 @@ Entry format (consistent prefix keeps the log greppable — `grep "^## \[" log.m
|
|
|
59
59
|
1–3 sentences on what happened.
|
|
60
60
|
```
|
|
61
61
|
|
|
62
|
-
Operations: `scaffold`, `ingest`, `query`, `lint`, `decision`, `task`, `bug`, `requirement`, `roadmap`, `archive`, `rotate`.
|
|
62
|
+
Operations: `scaffold`, `ingest`, `query`, `lint`, `decision`, `task`, `bug`, `requirement`, `roadmap`, `archive`, `close`, `rotate`.
|
|
63
63
|
|
|
64
64
|
> Archives: [2026_06_14_153012](log-2026_06_14_153012.md)
|
|
65
65
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: wiki-tidy
|
|
3
|
-
description: One-shot wiki cleanup — runs lint, archives terminal
|
|
3
|
+
description: One-shot wiki cleanup — runs lint, archives terminal tasks/UAT/bugs, and rotates the log if overgrown, in sequence with user confirmation at each phase
|
|
4
4
|
category: wiki
|
|
5
5
|
model: claude-sonnet-5
|
|
6
6
|
user-invocable: true
|
|
@@ -17,7 +17,7 @@ Three-phase cleanup for a neglected wiki. Runs in order: **lint → archive →
|
|
|
17
17
|
Run the full wiki-lint audit by following every step in `/wiki-lint` exactly as written:
|
|
18
18
|
|
|
19
19
|
1. Inventory the wiki tree.
|
|
20
|
-
2. Run all
|
|
20
|
+
2. Run all 13 checks, 2.0–2.12 (stranded terminal files, family-index drift, two-domain violations, ID/filename mismatch, UAT↔task cross-links, typed-link vocabulary, orphan pages, never-ingested raw sources, contradictions, stale frontmatter, provenance/confidence, typed-link target resolution, task-less accepted decisions) — each check's logic lives in `/wiki-lint`.
|
|
21
21
|
3. Report findings grouped by severity (HIGH / MEDIUM / LOW).
|
|
22
22
|
4. For each HIGH finding, propose the exact fix.
|
|
23
23
|
5. Ask: **"Which findings should I fix? Reply with 'all', specific IDs, or 'none' to skip. Type 'stop' to end wiki-tidy here."**
|
|
@@ -29,25 +29,22 @@ If the user types `stop`, end the skill here. Otherwise continue to Phase 2.
|
|
|
29
29
|
|
|
30
30
|
## Phase 2: Archive
|
|
31
31
|
|
|
32
|
-
Run `/wiki-archive` as a cleanup sweep — it scans for any
|
|
32
|
+
Run `/wiki-archive` as a cleanup sweep — it scans for any tasks, UAT or bugs with terminal status that were not automatically moved to `archive/` by their originating skill (`uat-auto`, `bug-close`, `task-close`, etc.). In a healthy wiki this phase finds nothing; it exists as a safety net. Roadmaps, decisions and requirements close in place (Closed section of the family index) and are never swept; a leftover non-empty `archive/` in one of those families is only reported (`run npx @codewizard-dt/bootstrap update to migrate`), never moved.
|
|
33
33
|
|
|
34
|
-
Scan
|
|
34
|
+
Scan the 3 archiving families in sequence: `tasks`, `uat`, `bugs`.
|
|
35
35
|
|
|
36
36
|
For each family:
|
|
37
37
|
1. Read its `lifecycle.md` to confirm the terminal statuses (do NOT hardcode).
|
|
38
38
|
2. Use `mcp__serena__list_dir` on the family directory.
|
|
39
39
|
3. Identify files whose `status:` frontmatter is terminal (exclude `lifecycle.md`, `index.md`, `.gitkeep`, and anything already under `archive/`).
|
|
40
40
|
|
|
41
|
-
After scanning all
|
|
41
|
+
After scanning all 3 families, show a combined summary:
|
|
42
42
|
|
|
43
43
|
```
|
|
44
44
|
Archive candidates:
|
|
45
45
|
tasks — N items (TASK-012 done, TASK-019 trashed, …)
|
|
46
46
|
uat — N items (UAT-012 passed, …)
|
|
47
47
|
bugs — N items
|
|
48
|
-
requirements— N items
|
|
49
|
-
decisions — N items
|
|
50
|
-
roadmaps — N items
|
|
51
48
|
|
|
52
49
|
Total: N items across N families.
|
|
53
50
|
```
|
|
@@ -102,6 +99,6 @@ Wiki tidy complete.
|
|
|
102
99
|
## CRITICAL rules
|
|
103
100
|
|
|
104
101
|
- Follow each sub-skill's CRITICAL rules exactly — they take precedence over brevity.
|
|
105
|
-
- Never move an active item. Never edit archived file content. Never delete anything.
|
|
102
|
+
- Never move an active item. Never move a roadmap, decision or requirement (they close in place). Never edit archived file content (tasks/UAT/bugs). Never delete anything.
|
|
106
103
|
- Always confirm with the user before applying changes in each phase.
|
|
107
104
|
- `stop` at any phase prompt ends the skill immediately without proceeding further.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@codewizard-dt/bootstrap",
|
|
3
|
-
"version": "
|
|
3
|
+
"version": "6.0.0",
|
|
4
4
|
"description": "Bootstrap Claude Code projects with an LLM Wiki, reusable skills, hooks, and MCP setup",
|
|
5
5
|
"homepage": "https://github.com/codewizard-dt/bootstrap-wiki#readme",
|
|
6
6
|
"bugs": {
|
|
@@ -1,10 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: Decisions Archive
|
|
3
|
-
---
|
|
4
|
-
|
|
5
|
-
# Decisions Archive
|
|
6
|
-
|
|
7
|
-
Decision group files where all decisions are `accepted` or `superseded`, moved here by `/wiki-archive` to reduce directory clutter. **Append-only** — archived items never move again.
|
|
8
|
-
|
|
9
|
-
| ID | Title | Final Status | Archived |
|
|
10
|
-
|----|-------|--------------|----------|
|
|
@@ -1,10 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: Requirements Archive
|
|
3
|
-
---
|
|
4
|
-
|
|
5
|
-
# Requirements Archive
|
|
6
|
-
|
|
7
|
-
Terminal requirement files (`retired`) moved here by `/wiki-archive` to reduce directory clutter. **Append-only** — archived items never move again.
|
|
8
|
-
|
|
9
|
-
| ID | Title | Final Status | Archived |
|
|
10
|
-
|----|-------|--------------|----------|
|
|
@@ -1,10 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
title: Roadmaps Archive
|
|
3
|
-
---
|
|
4
|
-
|
|
5
|
-
# Roadmaps Archive
|
|
6
|
-
|
|
7
|
-
Terminal roadmap files (`done`) moved here by `/wiki-archive` to reduce directory clutter. **Append-only** — archived items never move again.
|
|
8
|
-
|
|
9
|
-
| ID | Title | Final Status | Archived |
|
|
10
|
-
|----|-------|--------------|----------|
|