architext 0.0.4 → 0.0.5

package/dist/templates/en/docs/prompts/ref.md

@@ -1,23 +1,23 @@
 <protocol_ref>
 **Trigger**: `/archi.ref <sub> [args]`
-**Goal**: Manage external knowledge references (third-party APIs, internal SDKs, business rules, etc.), store them in `refs/` in a structured way, and inject context into `plan`/`code` on demand.
+**Goal**: Manage external knowledge refs (3rd-party APIs, internal SDKs, business rules, etc.); store in `refs/` in structured form; inject into `plan`/`code` on demand.
 
 **Subcommands**:
 | Subcommand | Format | Purpose |
 |:---|:---|:---|
 | `add` | `/archi.ref add [input]` | Summarize and store external knowledge (core) |
-| `list` | `/archi.ref list` | List all stored references |
-| `update` | `/archi.ref update <id>` | Re-summarize a specified reference |
-| `remove` | `/archi.ref remove <id>` | Remove a specified reference |
+| `list` | `/archi.ref list` | List all stored refs |
+| `update` | `/archi.ref update <id>` | Re-summarize specified ref |
+| `remove` | `/archi.ref remove <id>` | Remove specified ref |
 
 <meta>
   <style>Analytical, Precise, Context-Aware</style>
   <language>English</language>
   <principles>
-    1. **Summarize, Not Copy**: Do not copy full original content; distill into structured summaries (key interfaces / constraints / examples) for efficient AI use, compression ratio ≥ 50%.
-    2. **Format-Aware**: Choose the most suitable carrier format (`.md` / `.json` / `.yaml`) based on content type, preserving semantic advantages of the original format.
-    3. **Tag-Driven**: Each ref must carry tags for `plan`/`code` to match and inject on demand; no tagless references allowed.
-    4. **Index-First**: All operations must sync with `refs/index.json`; AI loads on demand via index, no full scan.
+    1. **Summarize, Not Copy**: Do not copy full original; must distill into structured summary (key interfaces / constraints / examples) for efficient AI use; compression ratio ≥ 50%.
+    2. **Format-Aware**: Auto-select best carrier format (`.md` / `.json` / `.yaml`) by content type; preserve original format semantics.
+    3. **Tag-Driven**: Each ref must carry tags for `plan`/`code` to match and inject; no tagless refs.
+    4. **Index-First**: All ops must sync `refs/index.json`; AI loads via index on demand; no full scan.
   </principles>
 </meta>
 
@@ -27,11 +27,11 @@
 
   | Content type | Recommended format | Rationale |
   |:---|:---|:---|
-  | Web page / URL / PDF / plain text | `.md` | Structured summary, highest AI read efficiency |
+  | Web / URL / PDF / plain text | `.md` | Structured summary; highest AI read efficiency |
   | OpenAPI / Swagger spec | `.yaml` | Preserve machine-readable structure; do not convert to .md |
-  | JSON Schema / config files | `.json` | Original structured data format is optimal |
-  | Mixed (with many code examples) | `.md` (with code blocks) | Preserve syntax in code blocks, add explanatory context |
-  | User pasted (pure Markdown) | `.md` | Store in same format, may refine |
+  | JSON Schema / config files | `.json` | Original structured data format optimal |
+  | Mixed (many code examples) | `.md` (with code blocks) | Code blocks keep syntax; add explanatory context |
+  | User paste (pure Markdown) | `.md` | Same format store; may refine |
 </format_selection>
 
 <!-- ═══════════════════════════════════════════════ -->
@@ -47,117 +47,47 @@
 
   | input form | Handling |
   |:---|:---|
-  | Local file path (e.g. `./docs/api.yaml`) | Read file content, record `sourceType: local-file` |
-  | URL (e.g. `https://...`) | Fetch page content, record `sourceType: url` |
-  | Not provided (conversation mode) | Ask user to paste content or provide path/URL, wait for input, record `sourceType: manual` |
+  | Local file path (e.g. `./docs/api.yaml`) | Read file content; record `sourceType: local-file` |
+  | URL (e.g. `https://...`) | Fetch page content; record `sourceType: url` |
+  | Not provided (conversation mode) | Ask user to paste content or provide path/URL; wait for input; record `sourceType: manual` |
 
   Check if `[[__DOCS_DIR__]]/refs/index.json` exists:
-  - Exists → Read, get existing id list (avoid duplicate names)
-  - Not exists → Initialize as `{ "refs": [] }`
+  - Exists → read; get existing id list (avoid duplicate names)
+  - Not exists → initialize as `{ "refs": [] }`
 
-  **Output**: Internal (raw content + sourceType + existing id list), proceed to `<step_1_analyze>`.
+  **Output**: Internal (raw content + sourceType + existing id list); proceed to `<step_1_analyze>`.
 </step_0_ingest>
 
 <step_1_analyze>
-  **Role**: System Analyst
   **Action**:
-  1. **Content type identification**: Determine which type the raw content belongs to (see `<format_selection>`), decide recommended storage format.
-  2. **Key info extraction**: From content extract:
-     - Core interfaces/endpoints/function signatures
-     - Parameter list and types (input/output)
-     - Important constraints, limits, caveats
-     - Auth/authorization (if any)
-     - Typical usage examples (≤ 3)
-  3. **Info gap identification**:
-     - id naming (infer a candidate, e.g. `wechat-pay`, pending user confirmation)
-     - tags (infer from standard tags: `api` / `sdk` / `internal` / `payment` / `auth` / `map` / `notification` / `storage` / custom)
-     - Focus areas (if content is large, confirm which interfaces/features user cares about)
-
-  **Output**: Internal analysis summary, proceed to `<step_2_interview>` (if gaps) or directly `<step_3_store>` (if complete).
+  1. **Content type identification**: Determine raw content type (per `<format_selection>`); decide recommended storage format.
+  2. **Key info extraction**: Core interfaces/endpoints/signatures, params and types, important constraints/limits, auth (if any), typical examples (≤3).
+  3. **Info gap identification**: id naming (infer candidate), tags (from standard: `api`/`sdk`/`internal`/`payment`/`auth`/`map`/`notification`/`storage`/custom), focus areas (when content large, confirm user's priority interfaces).
+
+  **Output**: Internal analysis summary; proceed to `<step_2_interview>` (when gaps) or directly `<step_3_store>` (when complete).
 </step_1_analyze>
 
 <step_2_interview>
-  **Role**: Product Consultant
-  **Trigger**: Execute only when id / tags / focus is uncertain.
-  **Action**: Ask user questions, max 3 questions, prefer multiple choice.
-
-  **Output format**:
-  ```
-  ### Reference info confirmation
-
-  **Content type**: [identified] → will store as [.md / .yaml / .json]
-  **Content summary**: [one-sentence description of raw content]
-
-  **Q1 — Reference ID** (for file naming and reference):
-  [A] [AI-inferred candidate] (recommended)
-  [B] Custom
-
-  **Q2 — Tags** (multi-select):
-  [A] api  [B] sdk  [C] internal  [D] payment  [E] auth  [F] Other: ___
+  **Trigger**: Only when id / tags / focus uncertain.
+  **Action**: Ask user; max 3 questions; options preferred.
 
-  (If content is large) **Q3 — Focus**:
-  [A] Keep full  [B] Keep only [specific interface list]  [C] Custom
-
-  **INPUT**: Q1 answer | Q2 answer | Q3 answer (if any)
-  ```
+  **Output**: Ref info confirmation — include content type and storage format, content summary, Q1 ref ID (AI inferred candidate + custom), Q2 tags (multi-select), (when content large) Q3 focus areas.
 
   **Gate**: Wait for user reply before `<step_3_store>`.
 </step_2_interview>
 
 <step_3_store>
-  **Role**: Senior Engineer
   **Action**:
-  1. Determine storage params:
-     - `id`: User-confirmed value (or AI-inferred)
-     - `format`: File extension from `<format_selection>` rules
-     - `filename`: `{id}.{format}`
-     - `tags`: User-confirmed tags list
+  1. Determine storage params: `id` (user confirmed or AI inferred), `format` (from format_selection), `filename: {id}.{format}`, `tags`.
 
   2. **Generate ref file content** (by format):
-
-     **`.md` format skeleton**:
-     ```markdown
-     ---
-     id: {id}
-     title: {title}
-     tags: [{tags}]
-     sourceType: url | local-file | manual
-     source: {source path or URL, "manual-input" when manual}
-     created: {YYYY-MM-DD}
-     updated: {YYYY-MM-DD}
-     ---
-
-     ## Core info
-     <!-- Base URL, version, auth, etc. -->
-
-     ## Key interfaces
-     | Interface/Function | Path/Signature | Description |
-     |:---|:---|:---|
-
-     ## Important constraints and caveats
-
-     ## Examples
-     <!-- ≤ 3 most representative examples -->
-     ```
-
-     **`.yaml` format**: Store original OpenAPI/Swagger content (trim redundant example fields in responses, keep schema structure).
-
-     **`.json` format**: Store original JSON Schema or config (remove comments, keep structure).
+     - **`.md`**: frontmatter (id/title/tags/sourceType/source/created/updated) + 4 sections (core info, key interfaces table, important constraints, examples ≤3)
+     - **`.yaml`**: Store trimmed OpenAPI/Swagger (remove redundant example fields; keep schema)
+     - **`.json`**: Store original structure (remove comments; keep structure)
 
   3. **Write file**: `[[__DOCS_DIR__]]/refs/{id}.{ext}`
 
-  4. **Update index**: Append to `[[__DOCS_DIR__]]/refs/index.json` refs array:
-     ```json
-     {
-       "id": "{id}",
-       "title": "{title}",
-       "tags": ["{tags}"],
-       "format": "{ext}",
-       "file": "{id}.{ext}",
-       "sourceType": "url | local-file | manual",
-       "updatedAt": "{YYYY-MM-DD}"
-     }
-     ```
+  4. **Update index**: Append to `[[__DOCS_DIR__]]/refs/index.json` refs array (id/title/tags/format/file/sourceType/updatedAt).
 
   **Output**:
   ```
@@ -167,18 +97,7 @@
 </step_3_store>
 
 <step_4_signoff_add>
-  **Output**: Add summary including:
-  - **Reference ID**: `{id}`
-  - **Storage format**: `{ext}` — rationale (one sentence)
-  - **Tags**: `[tags]`
-  - **File path**: `[[__DOCS_DIR__]]/refs/{id}.{ext}`
-  - **How to use**:
-
-  | Scenario | Description |
-  |:---|:---|
-  | `/archi.plan <ID>` | When planning involves `[tags]`-related features, AI auto-reads this ref |
-  | `/archi.code <ID>` | Injected as supplementary context during coding, provides interface signatures and constraint details |
-  | Manual reference | Mention "see `refs/{id}`" in conversation |
+  **Output**: Add summary — ref ID, storage format and rationale, tags, file path, usage notes (plan: auto-read / code: supplement context / manual ref).
 </step_4_signoff_add>
 
 </sub_add>
@@ -189,59 +108,45 @@
 
 <sub_list>
 
-**Role**: System Analyst
 **Trigger**: `/archi.ref list`
 **Action**: Read `[[__DOCS_DIR__]]/refs/index.json`.
 
 | Condition | Handling |
 |:---|:---|
-| Index missing / refs empty | Prompt "No references yet, run `/archi.ref add` to add the first" |
-| Normal | Display grouped by tags |
-
-**Output**:
-```
-### External knowledge references (N total)
-
-#### [tag group name]
-| ID | Title | Format | Updated |
-|:---|:---|:---|:---|
-| wechat-pay | WeChat Pay V3 API | .md | 2025-01-15 |
-| openapi-spec | Internal service OpenAPI | .yaml | 2025-01-10 |
-```
+| Index missing / refs empty | Prompt "No refs yet; run `/archi.ref add` to add first" |
+| Normal | Display grouped by tags (ID / title / format / updated) |
 
 </sub_list>
 
 <!-- ═══════════════════════════════════════════════ -->
-<!--                 UPDATE subcommand             -->
+<!--                 UPDATE subcommand              -->
 <!-- ═══════════════════════════════════════════════ -->
 
 <sub_update>
 
-**Role**: Senior Engineer
 **Trigger**: `/archi.ref update <id>`
 **Action**:
-1. Find `<id>` in `index.json`, get `file` and `sourceType`.
-2. If `sourceType` is `url` → re-fetch original URL; `local-file` → re-read file; `manual` → prompt user to paste new content.
-3. Re-run `<step_1_analyze>` + `<step_3_store>` (keep original id/tags/format, only refresh content and `updatedAt`).
+1. Find `<id>` in index.json; get `file` and `sourceType`.
+2. If `sourceType` is `url` → re-fetch; `local-file` → re-read; `manual` → prompt paste new content.
+3. Re-run `<step_1_analyze>` + `<step_3_store>` (keep original id/tags/format; refresh content and `updatedAt` only).
 
 | Condition | Handling |
 |:---|:---|
-| id not in index.json | Stop — prompt to check id, run `/archi.ref list` to view |
+| id not in index.json | Stop — prompt to check id; run `/archi.ref list` to view |
 
 </sub_update>
 
 <!-- ═══════════════════════════════════════════════ -->
-<!--                 REMOVE subcommand             -->
+<!--                 REMOVE subcommand              -->
 <!-- ═══════════════════════════════════════════════ -->
 
 <sub_remove>
 
-**Role**: System Administrator
 **Trigger**: `/archi.ref remove <id>`
 **Action**:
-1. Find and remove `<id>` from `index.json`.
+1. Find and remove `<id>` entry from index.json.
 2. Delete corresponding `refs/{id}.{ext}` file.
-3. Update `index.json`.
+3. Update index.json.
 
 **Output**:
 ```
@@ -251,7 +156,7 @@ MODIFIED  [[__DOCS_DIR__]]/refs/index.json
 
 | Condition | Handling |
 |:---|:---|
-| id not found | Stop — prompt to check id, run `/archi.ref list` to view |
+| id not found | Stop — prompt to check id; run `/archi.ref list` to view |
 
 </sub_remove>
 

package/dist/templates/en/docs/prompts/remove.md

@@ -1,161 +1,109 @@
 <protocol_remove>
   **Trigger**: `/archi.remove <id>`
-  **Goal**: Fully decommission the specified Task — delete docs, code, and global references with zero residue.
+  **Goal**: Decommission the specified Task from the project — delete docs, code, global refs; ensure zero residue.
 
 <meta>
     <style>Surgical, Cautious, Thorough</style>
     <language>English</language>
     <principles>
-      1.  **Dependency Safety**: If other tasks depend on this Task, dependencies must be resolved before proceeding.
-      2.  **Confirmation Gate**: Deletion is irreversible; must present full impact and obtain explicit confirmation.
-      3.  **Zero Residue**: Cleanup must cover all associated layers (docs/code/global data/glue entries).
-      4.  **No Side Effects**: Only remove content related to the target Task; forbidden to touch unrelated files.
+      1.  **Dependency Safety**: When other tasks depend on this Task, must decouple first to continue.
+      2.  **Confirmation Gate**: Delete is irreversible; must show full impact and get explicit user confirmation.
+      3.  **Zero Residue**: Cleanup must cover all layers (docs/code/global data/addressing entries).
+      4.  **No Side Effects**: Only delete target Task content; do not touch unrelated files.
     </principles>
 </meta>
 
 <step_1_resolve>
-    **Role**: System Analyst
     **Action**:
-    1.  **Resolve ID**: Parse `<id>` from `[[__DOCS_DIR__]]/global/roadmap.json` → Task Name, Slug, status.
-    2.  **ID Not Found** → Error with list of available task IDs.
-    3.  **Load Context**:
-        - `[[__DOCS_DIR__]]/tasks/<id>_<Slug>/` — All docs (spec.md, ui.md, plan.json, etc.)
-        - `[[__DOCS_DIR__]]/global/roadmap.json` — Task dependency graph
-        - `[[__DOCS_DIR__]]/global/map.json` — Architecture registry
-        - `99_context_glue.md` — Code↔doc associations
+    1.  **Resolve ID**: Parse `<id>` from roadmap.json → Task Name, Slug, status.
+    2.  **ID Not Found** → Error and list available task IDs.
+    3.  **Load**: task docs directory, roadmap.json (deps), map.json (architecture reg), 99_context_glue.md (associations).
 
     **Output**: Target Task info (ID, name, status, associated file count).
 </step_1_resolve>
 
 <step_2_impact>
-    **Role**: Impact Assessor
-    **Action**: Scan each layer to produce an impact manifest.
+    **Action**: Scan layer by layer; generate impact list.
 
-    ### 2.1 Dependency Check (Blocking)
+    ### 2.1 Dependency check (blocking)
 
-    Scan all tasks' `deps` in `roadmap.json` for references to `<id>`.
+    Scan roadmap.json all tasks `deps`; find tasks depending on `<id>`.
 
-    | Situation | Handling |
+    | Condition | Handling |
     |:---|:---|
-    | No downstream deps | Pass, continue |
-    | Has downstream deps with `pending`/`blocked` status | List affected tasks; ask user: remove dependency and continue, or abort |
-    | Has downstream deps with `active`/`done` status | **Block** — these tasks may use this Task's interfaces/components. Must `/archi.edit` to decouple first |
+    | No downstream deps | Pass |
+    | Has downstream deps and `pending`/`blocked` | List; ask: remove dep and continue or abort |
+    | Has downstream deps and `active`/`done` | **Block** — must `/archi.edit` to decouple first |
 
-    ### 2.2 Code File Identification
+    ### 2.2 Code file identification
 
-    Locate code files belonging to this Task via:
-    1.  `99_context_glue.md` code paths associated with `<id>`.
-    2.  `map.json` modules/directories registered for this Task.
-    3.  `plan.json` file paths mentioned in tasks.
-    4.  Scan code directories for files named with Slug or clearly scoped to this Task.
+    Locate code files via: context_glue paths, map.json registered modules, plan.json mentioned files, Slug-named or clearly owned files.
 
-    ### 2.3 Global Reference Scan
+    ### 2.3 Global ref scan
 
-    | File | Scan Target |
+    | File | Scan content |
     |:---|:---|
-    | `roadmap.json` | Task entry + `deps` references in other tasks |
-    | `map.json` | Module registry entries + `featureRelations` entries where the deleted Task is the aggregator |
+    | `roadmap.json` | Task entry + deps refs |
+    | `map.json` | Module entry + featureRelations where deleted Task is aggregator |
     | `99_context_glue.md` | Association entries |
-    | `dictionary.json` | Terms exclusive to this Task (flag only, no auto-delete) |
-    | `error_codes.json` | Error codes exclusive to this Task (flag only, no auto-delete) |
+    | `dictionary.json` | Exclusive terms (mark only) |
+    | `error_codes.json` | Exclusive error codes (mark only) |
 
-    ### 2.4 Aggregation Linkage Check
+    ### 2.4 Aggregator linkage check
 
-    Read `map.json.featureRelations`; determine whether the deleted Task falls within any aggregator's `sources` coverage.
+    [[SUBAGENT: archi-feature-relations|mode: cleanup, context: Check deleted Task refs in featureRelations; output impact report]][[NO-SKILL: (Skill not installed: read `[[__DOCS_DIR__]]/skills/archi-feature-relations/SKILL.md`, follow mode: cleanup logic)]]
 
-    | Situation | Handling |
-    |:---|:---|
-    | Not in any aggregator's sources range | No special handling |
-    | In an aggregator's sources range | List in impact report; prompt to check if aggregator content needs to be cleaned up after deletion |
-    | Deleted Task is itself an aggregator | Also remove its entry from `featureRelations` |
-
-    ### 2.5 Cross-Task References
-
-    Scan other Tasks' `spec.md` for references to the target Task's interfaces, components, or data. Flag as `[Breaking]`.
-
-    **Output**: Impact report to user:
-    ```
-    ### Decommission Impact Report: <ID> <Name>
-
-    **Task Status**: [status]
-
-    **Docs to delete**:
-    - [[__DOCS_DIR__]]/tasks/<id>_<slug>/  (N files)
-
-    **Code to delete**:
-    | File/Directory | Source |
-    |:---|:---|
-    | src/xxx/xxx.ts | context_glue |
-    | src/xxx/ | map.json |
+    ### 2.5 Cross-Task refs
 
-    **Global reference cleanup**:
-    - roadmap.json: remove task <id>, clean N deps references
-    - map.json: remove N module entries
-    - context_glue: remove N associations
+    Scan other Tasks' `spec.md`; check refs to deleted Task's interface/components/data. Mark refs as `[Breaking]`.
 
-    **[?present] Terms/error codes residue** (manual confirmation needed):
-    - dictionary.json: [term1], [term2]
-    - error_codes.json: [ERR_XXX]
+    **Output**: Output decommission impact report to user — include Task status, docs and code to delete (file/source table), global ref cleanup items (roadmap/map/context_glue), (if any) term/error code residue (manual confirm needed), (if any) aggregator linkage table, (if any) cross-Task ref [Breaking] table. End: OK to execute / Abort to cancel.
 
-    **[?present] Aggregation linkage** (check needed):
-    | Aggregator | checkNote |
-    |:---|:---|
-    | [aggregator ID/path] | [checkNote content] |
-
-    **[?present] Cross-Task references [Breaking]**:
-    | Referencing Task | Reference Content | Suggestion |
-    |:---|:---|:---|
-    | FEAT-005 spec.md | Calls <id>'s UserAPI | /archi.edit FEAT-005 to decouple first |
-
-    ---
-    > Reply **OK** to confirm; reply **abort** to cancel.
-    ```
-
-    **Gate**: Proceed to step_3 after user replies OK. Re-warn if `[Breaking]` cross-Task refs exist.
+    **Gate**: Proceed to step_3 only after user replies OK. Re-warn when `[Breaking]` refs exist.
 </step_2_impact>
 
 <step_3_execute>
     **Role**: Surgeon
-    **Action**: Execute in this order (order is mandatory).
+    **Action**: Execute in this order (order immutable).
 
-    | # | Operation | Target |
+    | # | Action | Target |
     |:---|:---|:---|
-    | 1 | Delete code files/directories | Code paths from step_2 |
-    | 2 | Delete Task doc directory | `[[__DOCS_DIR__]]/tasks/<id>_<slug>/` |
-    | 3 | Update `roadmap.json` | Remove task entry; clean `deps` refs to `<id>` in other tasks |
-    | 4 | Update `map.json` | Remove module entries; if this Task is an aggregator, also remove its `featureRelations` entry |
-    | 5 | Update `99_context_glue.md` | Remove association entries for this Task |
+    | 1 | Delete code files/dirs | Code paths from step_2 |
+    | 2 | Delete Task docs dir | `[[__DOCS_DIR__]]/tasks/<id>_<slug>/` |
+    | 3 | Update `roadmap.json` | Remove task entry; clean deps refs |
+    | 4 | Update `map.json` | Remove module entry + featureRelations entry |
+    | 5 | Update `99_context_glue.md` | Remove association entries |
     | 6 | [?exclusive terms] Update `dictionary.json` | Remove or mark deprecated |
-    | 7 | [?exclusive codes] Update `error_codes.json` | Remove or mark deprecated |
-    | 8 | [?aggregation linkage] Check aggregator code | Verify aggregator no longer references the deleted Task |
+    | 7 | [?exclusive error codes] Update `error_codes.json` | Remove or mark deprecated |
+    | 8 | [?aggregator linkage] Check aggregator code | Confirm refs cleaned |
 
-    Log each operation (file path + operation type) as it completes.
+    Record operation log after each step.
 </step_3_execute>
 
 <step_4_verify>
-    **Role**: Verification Engineer
-    **Terminal Gate** (Do not skip; must complete before step_5 output):
+    **Terminal Gate** (do not skip): Standard check (task --check + render).
     | Step | Command | Pass Condition |
     |:---|:---|:---|
-    | 1 | `npx archi task --check` | No ERROR-level issues, no dangling deps |
-    | 2 | `npx archi render` | `.md` views generated |
-    | 3 | Run project build command | Zero compilation errors |
-
-    | Check | Pass Criteria |
-    |:---|:---|
-    | Roadmap consistency | `--check` passes, no dangling deps |
-    | Build | Zero compilation errors |
-    | Residual refs | No import/require of deleted modules in codebase |
+    | 3 | Run project build command | Zero compile errors; no import/require to deleted module |
 
-    Build failure or residual refs found → locate, fix, and recheck.
+    If build fails or residual refs found → locate, fix, re-check.
 </step_4_verify>
 
 <step_5_summary>
-    **Output**: Decommission summary:
+    **Pre-signoff Checklist** (confirm each item before Output):
+    □ Code files/directories — deleted (step_3 action #1)
+    □ tasks/<id>_<slug>/ doc directory — deleted (step_3 action #2)
+    □ roadmap.json — task entry + deps refs — cleaned (step_3 action #3)
+    □ map.json — module entry + featureRelations — cleaned (step_3 action #4)
+    □ 99_context_glue.md — association entries — cleaned (step_3 action #5)
+    □ (if exclusive terms/codes) dictionary.json + error_codes.json — handled
+    □ Terminal Gate — project build passes, no residual import refs (step_4)
+
+    **Output**: Decommission completion summary:
     - **Deleted**: N doc files, N code files
-    - **Cleaned**: roadmap / map / context_glue references
-    - **Build status**: pass/fail
-    - **[?present] Manual follow-up needed**: terms/error codes/cross-Task ref residue
+    - **Cleaned**: refs in roadmap / map / context_glue
+    - **Build status**: Pass/Fail
+    - **[?if any] Manual follow-up**: Term/error code/cross-Task ref residue
     - **Git Commit Suggestion**: `feat(remove): decommission <ID> <Name>`
 </step_5_summary>