@theglitchking/persistent-planning 3.1.0 → 3.4.0

package/.claude-plugin/marketplace.json

@@ -6,13 +6,13 @@
   },
   "metadata": {
     "description": "Official marketplace for persistent-planning - Persistent markdown-based planning for Claude Code. Context engineering pattern with task directories, progress tracking, and working memory that persists across sessions.",
-    "version": "3.1.0"
+    "version": "3.4.0"
   },
   "plugins": [
     {
       "name": "persistent-planning",
       "description": "Persistent markdown-based planning for Claude Code. Uses on-disk markdown files as working memory for planning, progress tracking, and knowledge storage. Plans persist across sessions and support multiple concurrent tasks.",
-      "version": "3.1.0",
+      "version": "3.4.0",
       "author": {
         "name": "TheGlitchKing"
       },

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "persistent-planning",
-  "version": "3.1.0",
+  "version": "3.4.0",
   "description": "Persistent markdown-based planning with task directories, progress tracking, and context engineering for multi-step Claude Code workflows",
   "author": {
     "name": "TheGlitchKing"

package/.documentation/INDEX.md

@@ -3,7 +3,7 @@ title: Documentation Index
 tier: reference
 domains: [root]
 status: active
-last_updated: '2026-08-31'
+last_updated: '2026-09-04'
 version: '1.0.0'
 purpose: Navigation hub for all documentation
 ---
@@ -18,20 +18,20 @@ purpose: Navigation hub for all documentation
 |--------|-----------|-------------|
 | [Agents](#agents) | 0 | Expert agent documentation, specialty matrix |
 | [API](#api) | 0 | API endpoints, routes, specifications, contracts |
-| [Architecture](#architecture) | 2 | System design, AI coach, project registry, patterns |
+| [Architecture](#architecture) | 4 | System design, AI coach, project registry, patterns |
 | [Backups](#backups) | 0 | Backup/restore guides, disaster recovery |
 | [Database](#database) | 0 | Schema, migrations, RLS, queries, procedures |
 | [DevOps](#devops) | 0 | Deployment, CI/CD, Docker, environments, infrastructure |
 | [Features](#features) | 0 | Feature implementation guides, admin docs |
 | [Plans](#plans) | 0 | Planning documents, roadmaps, proposals |
-| [Procedures](#procedures) | 1 | Step-by-step operational procedures (SOP) |
+| [Procedures](#procedures) | 2 | Step-by-step operational procedures (SOP) |
 | [Quickstart](#quickstart) | 1 | Setup guides, dev workflow, onboarding |
 | [Security](#security) | 0 | Security, auth, Vault, Keycloak, RLS |
 | [Standards](#standards) | 2 | Coding standards (backend, frontend, database, devops, security) |
 | [Testing](#testing) | 1 | Test strategies, fixtures, patterns, integration/e2e |
-| [Troubleshooting](#troubleshooting) | 0 | Debug guides, common issues, solutions |
+| [Troubleshooting](#troubleshooting) | 2 | Debug guides, common issues, solutions |
 | [Workflows](#workflows) | 0 | Process documentation, multi-step operations |
-| [Reference](#reference) | 1 | Schema, frontmatter, and CLI reference material for the planning artifacts |
+| [Reference](#reference) | 3 | Schema, frontmatter, and CLI reference material for the planning artifacts |
 
 ---
 
@@ -65,6 +65,8 @@ purpose: Navigation hub for all documentation
 |----------|------|--------|----------|
 | [Manus Context Engineering Principles](architecture/context-engineering-principles.md) | reference | active | 2026-08-31 |
 | [Lg-Mode Layered Planning Guide](architecture/lg-mode.md) | guide | active | 2026-05-07 |
+| [lg plan artifact lifecycle — who writes what](architecture/lg-plan-artifact-lifecycle.md) | reference | active | 2026-09-04 |
+| [Skill linking and reclaim](architecture/skill-linking-and-reclaim.md) | reference | active | 2026-09-04 |
 
 ---
 
@@ -127,6 +129,7 @@ purpose: Navigation hub for all documentation
 | Document | Tier | Status | Updated |
 |----------|------|--------|----------|
 | [Plan Completion and Archive](procedures/plan-completion-and-archive.md) | guide | active | 2026-08-31 |
+| [Plugin update delivery — what actually runs, and when](procedures/plugin-update-delivery.md) | guide | active | 2026-09-04 |
 
 ---
 
@@ -183,7 +186,10 @@ purpose: Navigation hub for all documentation
 
 **Path:** `troubleshooting/`
 
-*No documents yet.*
+| Document | Tier | Status | Updated |
+|----------|------|--------|----------|
+| [A plan won't read COMPLETE](troubleshooting/plan-never-reads-complete.md) | guide | active | 2026-09-04 |
+| [Stale skill directory — commands run frozen code](troubleshooting/stale-skill-dir-drift.md) | guide | active | 2026-09-04 |
 
 ---
 
@@ -205,12 +211,14 @@ purpose: Navigation hub for all documentation
 
 | Document | Tier | Status | Updated |
 |----------|------|--------|----------|
+| [`mandatory:` task frontmatter](reference/mandatory-frontmatter.md) | reference | active | 2026-09-04 |
+| [Skill version marker (`.version`)](reference/skill-version-marker.md) | reference | active | 2026-09-04 |
 | [workspace.json schema](reference/workspace-json.md) | standard | active | 2026-05-07 |
 
 ---
 
 ## Maintenance
 
-- **Last generated:** 2026-08-31
+- **Last generated:** 2026-09-04
 - **Run maintenance:** `npx hit-em-with-the-docs maintain`
 - **Regenerate index:** `npx hit-em-with-the-docs index`

package/.documentation/REGISTRY.md

@@ -3,7 +3,7 @@ title: Documentation Registry
 tier: reference
 domains: [root]
 status: active
-last_updated: '2026-08-31'
+last_updated: '2026-09-04'
 version: '1.0.0'
 purpose: Quick reference for all documentation domains
 ---
@@ -77,4 +77,4 @@ purpose: Quick reference for all documentation domains
 
 ---
 
-*Last updated: 2026-08-31*
+*Last updated: 2026-09-04*

package/.documentation/agents/INDEX.md

@@ -3,7 +3,7 @@ title: Agents Documentation Index
 tier: reference
 domains: [agents]
 status: active
-last_updated: '2026-08-31'
+last_updated: '2026-09-04'
 version: '1.0.0'
 purpose: Complete listing of agents documentation
 ---
@@ -40,4 +40,4 @@ This domain covers: agent, agents, ai, assistant, expert, specialist, llm, langc
 
 ---
 
-*Last updated: 2026-08-31*
+*Last updated: 2026-09-04*

package/.documentation/agents/REGISTRY.md

@@ -3,7 +3,7 @@ title: Agents Registry
 tier: reference
 domains: [agents]
 status: active
-last_updated: '2026-08-31'
+last_updated: '2026-09-04'
 version: '1.0.0'
 purpose: Quick reference for agents documentation
 ---
@@ -35,4 +35,4 @@ purpose: Quick reference for agents documentation
 
 ---
 
-*Last updated: 2026-08-31*
+*Last updated: 2026-09-04*

package/.documentation/api/INDEX.md

@@ -3,7 +3,7 @@ title: API Documentation Index
 tier: reference
 domains: [api]
 status: active
-last_updated: '2026-08-31'
+last_updated: '2026-09-04'
 version: '1.0.0'
 purpose: Complete listing of api documentation
 ---
@@ -40,4 +40,4 @@ This domain covers: api, endpoint, endpoints, route, routes, rest, restful, grap
 
 ---
 
-*Last updated: 2026-08-31*
+*Last updated: 2026-09-04*

package/.documentation/api/REGISTRY.md

@@ -3,7 +3,7 @@ title: API Registry
 tier: reference
 domains: [api]
 status: active
-last_updated: '2026-08-31'
+last_updated: '2026-09-04'
 version: '1.0.0'
 purpose: Quick reference for api documentation
 ---
@@ -35,4 +35,4 @@ purpose: Quick reference for api documentation
 
 ---
 
-*Last updated: 2026-08-31*
+*Last updated: 2026-09-04*

package/.documentation/architecture/INDEX.md

@@ -3,7 +3,7 @@ title: Architecture Documentation Index
 tier: reference
 domains: [architecture]
 status: active
-last_updated: '2026-08-31'
+last_updated: '2026-09-04'
 version: '1.0.0'
 purpose: Complete listing of architecture documentation
 ---
@@ -14,7 +14,7 @@ purpose: Complete listing of architecture documentation
 
 ## Overview
 
-- **Total Documents:** 2
+- **Total Documents:** 4
 - **Domain:** `architecture/`
 - **Category:** development
 - **Load Priority:** 7/10
@@ -32,6 +32,8 @@ purpose: Complete listing of architecture documentation
 | Document | Status | Updated | Words |
 |----------|--------|---------|-------|
 | [Manus Context Engineering Principles](context-engineering-principles.md) | active | 2026-08-31 | 428 |
+| [lg plan artifact lifecycle — who writes what](lg-plan-artifact-lifecycle.md) | active | 2026-09-04 | 438 |
+| [Skill linking and reclaim](skill-linking-and-reclaim.md) | active | 2026-09-04 | 348 |
 
 ## Keywords
 
@@ -45,4 +47,4 @@ This domain covers: architecture, design, system, system-design, pattern, patter
 
 ---
 
-*Last updated: 2026-08-31*
+*Last updated: 2026-09-04*

package/.documentation/architecture/REGISTRY.md

@@ -3,7 +3,7 @@ title: Architecture Registry
 tier: reference
 domains: [architecture]
 status: active
-last_updated: '2026-08-31'
+last_updated: '2026-09-04'
 version: '1.0.0'
 purpose: Quick reference for architecture documentation
 ---
@@ -16,7 +16,7 @@ purpose: Quick reference for architecture documentation
 
 | Metric | Value |
 |--------|-------|
-| Documents | 2 |
+| Documents | 4 |
 | Category | development |
 | Load Priority | 7/10 |
 
@@ -24,9 +24,13 @@ purpose: Quick reference for architecture documentation
 
 - [Manus Context Engineering Principles](context-engineering-principles.md)
 - [Lg-Mode Layered Planning Guide](lg-mode.md)
+- [lg plan artifact lifecycle — who writes what](lg-plan-artifact-lifecycle.md)
+- [Skill linking and reclaim](skill-linking-and-reclaim.md)
 
 ## Recently Updated
 
+- [lg plan artifact lifecycle — who writes what](lg-plan-artifact-lifecycle.md) - 2026-09-04
+- [Skill linking and reclaim](skill-linking-and-reclaim.md) - 2026-09-04
 - [Manus Context Engineering Principles](context-engineering-principles.md) - 2026-08-31
 - [Lg-Mode Layered Planning Guide](lg-mode.md) - 2026-05-07
 
@@ -34,7 +38,7 @@ purpose: Quick reference for architecture documentation
 
 | Status | Count |
 |--------|-------|
-| active | 2 |
+| active | 4 |
 | draft | 0 |
 | deprecated | 0 |
 | archived | 0 |
@@ -50,4 +54,4 @@ purpose: Quick reference for architecture documentation
 
 ---
 
-*Last updated: 2026-08-31*
+*Last updated: 2026-09-04*

package/.documentation/architecture/lg-mode.md

@@ -142,3 +142,19 @@ To explicitly migrate a v2 plan to lg, manually:
 - `templates/lg/{phase,task,atom,notes}.md` — frontmatter shapes
 - `scripts/detect-mode.sh` — mode resolution logic
 - `scripts/init-{phase,task,atom}.sh` — init script implementations
+
+
+## How the skill reaches a consumer repo
+
+`.claude/skills/persistent-planning` is a **symlink** into the installed package, created
+by `scripts/link-skills.js`. A real directory there is stale v1 debris and means commands
+are running frozen code — see
+[Skill linking and reclaim](skill-linking-and-reclaim.md) and
+[Stale skill directory](../troubleshooting/stale-skill-dir-drift.md).
+
+
+## Who writes which artifact
+
+Creating a task writes it into its phase's list; creating an atom writes it into its
+task's list. Full ownership table and the insertion rule:
+[lg plan artifact lifecycle](lg-plan-artifact-lifecycle.md).

package/.documentation/architecture/lg-plan-artifact-lifecycle.md

@@ -0,0 +1,104 @@
+---
+title: lg plan artifact lifecycle — who writes what
+tier: reference
+domains:
+  - architecture
+audience:
+  - developers
+tags: []
+status: active
+last_updated: '2026-09-04'
+version: 1.0.0
+purpose: >-
+  Which script writes which lg plan artifact, the rule that creating a child writes it
+  into its parent's list, and how insertion keeps the mandatory closers last.
+estimated_read_time: 3 minutes
+word_count: 438
+last_validated: '2026-09-04'
+backlinks: []
+---
+
+# lg plan artifact lifecycle — who writes what
+
+In lg mode a plan is a tree of markdown artifacts, and more than one thing writes
+into them. This page states the ownership, because for a long time nothing did —
+and the gap it left is [issue #12](https://github.com/the-glitch-kingdom/persistent-planning/issues/12).
+
+## Ownership
+
+| Artifact | Created by | Its list is written by |
+|---|---|---|
+| `<phase>/phase.md` | `init-phase.sh` | `init-task.sh`, on every new task |
+| `<phase>/notes.md` | `init-phase.sh` | humans |
+| `<phase>/<task>/task.md` | `init-task.sh` (closers: `init-phase.sh`) | `init-atom.sh`, on every new atom |
+| `<phase>/<task>/notes.md` | `init-task.sh` | humans |
+| `<phase>/<task>/atoms/<atom>.md` | `init-atom.sh` | humans |
+
+The rule worth remembering: **creating a child writes it into its parent's list.**
+Before 3.3.0, `init-task.sh` referenced `phase.md` only in an existence check and
+`init-atom.sh` never touched `task.md`, so every list was maintained by hand — and a
+phase could report "no tasks yet" with six task directories on disk.
+
+## The insertion rule
+
+`planning_insert_list_item <file> <section> <line>` in `scripts/lib/planning.sh`:
+
+- inserts **above the first item marked MANDATORY**, so the closers stay last by
+  construction rather than by anyone remembering the rule;
+- appends after the last item when the section has no MANDATORY entries (atom lists);
+- drops the `(no … yet)` placeholder, including indented continuation lines, the
+  first time a real item lands;
+- is idempotent — an identical line already present is left alone, so re-running
+  under `PLANNING_FORCE=1` cannot double-insert;
+- is section-scoped (`## Heading` to the next `## `), so it cannot wander into a
+  neighbouring list.
+
+It **anchors on the MANDATORY marker, never on line numbers.** The list is a
+human-editable surface; positions do not survive contact with editing. This is tested
+against a hand-reordered, partially-checked, annotated list.
+
+## The two closers
+
+Every phase is scaffolded with both closing tasks as real directories:
+
+```
+<phase>/validate-success-through-comprehensive-testing/
+<phase>/documentation-pass-create-update-deprecate-docs/
+```
+
+Each gets `task.md` (with `mandatory: true`, `parallelizable: false`), `notes.md`,
+`atoms/`, and seeded atoms — not empty placeholders. They were previously two lines
+of prose in `phase.md`, which made the most important tasks in every plan the only
+ones with no artifact a subagent could read and nowhere to record decisions.
+
+See [Mandatory frontmatter](../reference/mandatory-frontmatter.md) for what
+`mandatory: true` does, and
+[Mandatory closing phases](../standards/mandatory-closing-phases.md) for why they exist.
+
+## Placeholders are not work
+
+`(no tasks yet …)` and `(no atoms yet …)` are **italic text, not checkboxes**. They
+used to ship as `- [ ]`, and `plan-status.sh` counts every checkbox under a plan — so
+a fresh phase with two tasks reported `0/5 boxes` and a plan could reach 100% by
+ticking lines asserting that nothing existed. See
+[Plan never reads complete](../troubleshooting/plan-never-reads-complete.md).
+
+## What is version-controlled
+
+Active plans are **tracked**. They are the artifact a team coordinates around and that
+subagents read via the planning MCP — and lg mode is selected precisely because there is
+a team (≥2 git authors in 90 days). Ignoring them would defeat the mode's purpose.
+
+Only `.planning/.archive/` is ignored: a completed plan is local history. Both init
+scripts and `archive-plan.sh` write that one entry through
+`planning_ensure_archive_gitignored` (sm keeps its own self-contained copy).
+
+A repo that already carries a blanket `.planning/` line from v1 keeps it — the tool warns
+once and never rewrites a user's `.gitignore`. To start sharing plans, replace that line
+with `.planning/.archive/`.
+
+## sm mode is different, on purpose
+
+`scripts/init-planning.sh` writes a single flat `task_plan.md` where phases-as-checkboxes
+*is* the entire artifact. None of the above applies, and per `CLAUDE.md` its v2 behavior
+is preserved bit-for-bit — the test suite diffs its output against the pre-change render.

package/.documentation/architecture/skill-linking-and-reclaim.md

@@ -0,0 +1,84 @@
+---
+title: Skill linking and reclaim
+tier: reference
+domains:
+  - architecture
+audience:
+  - developers
+tags: []
+status: active
+last_updated: '2026-09-04'
+version: 1.0.0
+purpose: How the skill directory reaches a consumer repo as a symlink, the four states it can
+  be in, and how a stale real directory is reclaimed without ever deleting it.
+estimated_read_time: 2 minutes
+word_count: 348
+last_validated: '2026-09-04'
+backlinks: []
+---
+
+# Skill linking and reclaim
+
+How `skills/persistent-planning/` reaches a consumer repo, and how a stale copy is
+reclaimed. Implemented in `scripts/lib/skill-link.js` and `scripts/link-skills.js`.
+
+## The link
+
+`scripts/link-skills.js` runs as npm `postinstall` and delegates to
+`@theglitchking/claude-plugin-runtime`'s `runPostinstall()`, which symlinks each
+directory under `skills/` into the consumer's `.claude/skills/`.
+
+The runtime's linker reconciles a symlink but **skips a real directory** — it warns
+and moves on, every time, forever. That is correct caution (the directory might be
+hand-managed) and it is also how v1 debris survived five months: v1's
+`persistent-planning install`, removed in 2.0.0, *copied* the skill dir, and nothing
+since could reclaim it.
+
+## The reclaim
+
+`reclaimStaleSkillDirs()` runs **before** the delegation. It renames a real directory
+to `<name>.bak-<ISO8601>`, which leaves a clean destination the runtime's linker then
+symlinks normally.
+
+That ordering is the whole trick — it needs no change to `claude-plugin-runtime`, so
+the fix ships as one release of this package rather than a runtime publish plus a
+coordinated rollout. The runtime's skip is still worth fixing upstream; this shim is
+written to be harmless if that ever lands.
+
+Rules the implementation holds to:
+
+- **Never delete.** A failed rename falls through to the runtime's old skip, but says
+  so loudly and names `relink`. The directory may contain hand edits.
+- **Idempotent.** A healthy symlink is left completely alone, so a second run makes no
+  second backup.
+- **Best-effort.** Any failure is caught; a reclaim problem never blocks an install.
+
+## The four states
+
+`describeSkill()` classifies `.claude/skills/<name>`:
+
+| State | Meaning |
+|---|---|
+| `absent` | nothing there; the linker will create the symlink |
+| `symlink-ok` | points at this package (relative or absolute, both accepted) |
+| `symlink-foreign` | points somewhere else — another install owns it |
+| `real-dir` | **drift.** Nothing in the current system creates one |
+
+`real-dir` and `symlink-foreign` are what `driftedSkills()` reports and what the
+SessionStart hook warns about.
+
+## Escape hatches
+
+| Variable | Effect |
+|---|---|
+| `PERSISTENT_PLANNING_SKIP_LINK=1` | no linking at all (runtime convention) |
+| `PERSISTENT_PLANNING_NO_RECLAIM=1` | link, but never move an existing directory aside |
+
+`updatePolicy: off` in `.claude/persistent-planning.json` suppresses the warning and
+the automatic repair.
+
+## Related
+
+- [Plugin update delivery](../procedures/plugin-update-delivery.md)
+- [Skill version marker](../reference/skill-version-marker.md)
+- [Stale skill directory](../troubleshooting/stale-skill-dir-drift.md)

package/.documentation/backups/INDEX.md

@@ -3,7 +3,7 @@ title: Backups Documentation Index
 tier: reference
 domains: [backups]
 status: active
-last_updated: '2026-08-31'
+last_updated: '2026-09-04'
 version: '1.0.0'
 purpose: Complete listing of backups documentation
 ---
@@ -40,4 +40,4 @@ This domain covers: backup, backups, restore, recovery, disaster, disaster-recov
 
 ---
 
-*Last updated: 2026-08-31*
+*Last updated: 2026-09-04*

package/.documentation/backups/REGISTRY.md

@@ -3,7 +3,7 @@ title: Backups Registry
 tier: reference
 domains: [backups]
 status: active
-last_updated: '2026-08-31'
+last_updated: '2026-09-04'
 version: '1.0.0'
 purpose: Quick reference for backups documentation
 ---
@@ -35,4 +35,4 @@ purpose: Quick reference for backups documentation
 
 ---
 
-*Last updated: 2026-08-31*
+*Last updated: 2026-09-04*

package/.documentation/database/INDEX.md

@@ -3,7 +3,7 @@ title: Database Documentation Index
 tier: reference
 domains: [database]
 status: active
-last_updated: '2026-08-31'
+last_updated: '2026-09-04'
 version: '1.0.0'
 purpose: Complete listing of database documentation
 ---
@@ -40,4 +40,4 @@ This domain covers: database, db, postgres, postgresql, mysql, sql, schema, migr
 
 ---
 
-*Last updated: 2026-08-31*
+*Last updated: 2026-09-04*

package/.documentation/database/REGISTRY.md

@@ -3,7 +3,7 @@ title: Database Registry
 tier: reference
 domains: [database]
 status: active
-last_updated: '2026-08-31'
+last_updated: '2026-09-04'
 version: '1.0.0'
 purpose: Quick reference for database documentation
 ---
@@ -35,4 +35,4 @@ purpose: Quick reference for database documentation
 
 ---
 
-*Last updated: 2026-08-31*
+*Last updated: 2026-09-04*

package/.documentation/devops/INDEX.md

@@ -3,7 +3,7 @@ title: DevOps Documentation Index
 tier: reference
 domains: [devops]
 status: active
-last_updated: '2026-08-31'
+last_updated: '2026-09-04'
 version: '1.0.0'
 purpose: Complete listing of devops documentation
 ---
@@ -40,4 +40,4 @@ This domain covers: devops, deployment, deploy, ci, cd, ci/cd, pipeline, docker,
 
 ---
 
-*Last updated: 2026-08-31*
+*Last updated: 2026-09-04*

package/.documentation/devops/REGISTRY.md

@@ -3,7 +3,7 @@ title: DevOps Registry
 tier: reference
 domains: [devops]
 status: active
-last_updated: '2026-08-31'
+last_updated: '2026-09-04'
 version: '1.0.0'
 purpose: Quick reference for devops documentation
 ---
@@ -35,4 +35,4 @@ purpose: Quick reference for devops documentation
 
 ---
 
-*Last updated: 2026-08-31*
+*Last updated: 2026-09-04*

package/.documentation/features/INDEX.md

@@ -3,7 +3,7 @@ title: Features Documentation Index
 tier: reference
 domains: [features]
 status: active
-last_updated: '2026-08-31'
+last_updated: '2026-09-04'
 version: '1.0.0'
 purpose: Complete listing of features documentation
 ---
@@ -40,4 +40,4 @@ This domain covers: feature, features, implementation, guide, how-to, tutorial,
 
 ---
 
-*Last updated: 2026-08-31*
+*Last updated: 2026-09-04*

package/.documentation/features/REGISTRY.md

@@ -3,7 +3,7 @@ title: Features Registry
 tier: reference
 domains: [features]
 status: active
-last_updated: '2026-08-31'
+last_updated: '2026-09-04'
 version: '1.0.0'
 purpose: Quick reference for features documentation
 ---
@@ -35,4 +35,4 @@ purpose: Quick reference for features documentation
 
 ---
 
-*Last updated: 2026-08-31*
+*Last updated: 2026-09-04*

package/.documentation/plans/INDEX.md

@@ -3,7 +3,7 @@ title: Plans Documentation Index
 tier: reference
 domains: [plans]
 status: active
-last_updated: '2026-08-31'
+last_updated: '2026-09-04'
 version: '1.0.0'
 purpose: Complete listing of plans documentation
 ---
@@ -40,4 +40,4 @@ This domain covers: plan, plans, planning, roadmap, proposal, proposals, rfc, de
 
 ---
 
-*Last updated: 2026-08-31*
+*Last updated: 2026-09-04*

package/.documentation/plans/REGISTRY.md

@@ -3,7 +3,7 @@ title: Plans Registry
 tier: reference
 domains: [plans]
 status: active
-last_updated: '2026-08-31'
+last_updated: '2026-09-04'
 version: '1.0.0'
 purpose: Quick reference for plans documentation
 ---
@@ -35,4 +35,4 @@ purpose: Quick reference for plans documentation
 
 ---
 
-*Last updated: 2026-08-31*
+*Last updated: 2026-09-04*

package/.documentation/procedures/INDEX.md

@@ -3,7 +3,7 @@ title: Procedures Documentation Index
 tier: reference
 domains: [procedures]
 status: active
-last_updated: '2026-08-31'
+last_updated: '2026-09-04'
 version: '1.0.0'
 purpose: Complete listing of procedures documentation
 ---
@@ -14,7 +14,7 @@ purpose: Complete listing of procedures documentation
 
 ## Overview
 
-- **Total Documents:** 1
+- **Total Documents:** 2
 - **Domain:** `procedures/`
 - **Category:** features
 - **Load Priority:** 6/10
@@ -26,6 +26,7 @@ purpose: Complete listing of procedures documentation
 | Document | Status | Updated | Words |
 |----------|--------|---------|-------|
 | [Plan Completion and Archive](plan-completion-and-archive.md) | active | 2026-08-31 | 812 |
+| [Plugin update delivery — what actually runs, and when](plugin-update-delivery.md) | active | 2026-09-04 | 539 |
 
 ## Keywords
 
@@ -39,4 +40,4 @@ This domain covers: procedure, procedures, sop, standard-operating-procedure, st
 
 ---
 
-*Last updated: 2026-08-31*
+*Last updated: 2026-09-04*