code-anchored-context 0.1.0 → 0.2.0

package/bin/code-anchored-context.js

@@ -18,7 +18,7 @@ import { fileURLToPath } from 'node:url';
 const packageRoot = path.resolve(path.dirname(fileURLToPath(import.meta.url)), '..');
 const defaultRelease = 'v0_1_0';
 const defaultReleaseLabel = 'v0.1.0';
-const skillName = 'development-initiative-context';
+const skillName = 'code-anchored-context';
 const agentSectionStart = '<!-- code-anchored-context:start -->';
 const agentSectionEnd = '<!-- code-anchored-context:end -->';
 
@@ -54,7 +54,7 @@ async function main() {
     dryRun: args.dryRun
   });
 
-  await installer.init({ includeDocumentation: args.documentation });
+  await installer.init({ includeDocs: args.docs });
 }
 
 function parseArgs(argv) {
@@ -65,7 +65,7 @@ function parseArgs(argv) {
     release: defaultRelease,
     force: false,
     dryRun: false,
-    documentation: true,
+    docs: true,
     help: false,
     version: false
   };
@@ -95,8 +95,8 @@ function parseArgs(argv) {
       continue;
     }
 
-    if (arg === '--no-documentation') {
-      options.documentation = false;
+    if (arg === '--no-docs') {
+      options.docs = false;
       continue;
     }
 
@@ -170,7 +170,7 @@ Options:
   --target <path>          Project root to install into. Defaults to cwd.
   --project-name <name>   Name used to replace PROJECT_NAME placeholders.
   --release <slug>        Initial release slug. Defaults to ${defaultRelease}.
-  --no-documentation      Skip the Documentation/ starter files.
+  --no-docs               Skip the docs/ starter files.
   --force                 Replace existing generated directories.
   --dry-run               Show planned changes without writing files.
   -h, --help              Show help.
@@ -178,7 +178,7 @@ Options:
 
 Examples:
   npx code-anchored-context init --project-name "My App"
-  npx code-anchored-context init --release v1_0_0 --no-documentation
+  npx code-anchored-context init --release v1_0_0 --no-docs
 `);
 }
 
@@ -212,30 +212,34 @@ class Installer {
     this.force = force;
     this.dryRun = dryRun;
     this.actions = [];
+    this.agentsFilePath = path.join(targetRoot, 'AGENTS.md');
   }
 
-  async init({ includeDocumentation }) {
+  async init({ includeDocs }) {
     await this.ensureDirectory(this.targetRoot);
 
     await this.installAgentsFile();
     await this.installSkill();
-    await this.copyTemplatePath('Development', 'Development');
+    await this.copyTemplatePath('context', 'context');
     await this.renameReleasePaths();
 
-    if (includeDocumentation) {
-      await this.copyTemplatePath('Documentation', 'Documentation');
+    if (includeDocs) {
+      await this.copyTemplatePath('docs', 'docs');
     } else {
-      this.note('skip Documentation/ (--no-documentation)');
+      this.note('skip docs/ (--no-docs)');
     }
 
     this.printSummary();
   }
 
   async installAgentsFile() {
-    const targetFile = path.join(this.targetRoot, 'AGENTS.md');
+    const targetFile = await this.findAgentsFile();
+    const targetDisplay = path.basename(targetFile);
+    this.agentsFilePath = targetFile;
 
     if (!await exists(targetFile)) {
       await this.copyTemplatePath('AGENTS.md', 'AGENTS.md');
+      this.agentsFilePath = path.join(this.targetRoot, 'AGENTS.md');
       return;
     }
 
@@ -249,16 +253,16 @@ class Installer {
       );
 
       if (updated === current) {
-        this.note('AGENTS.md already has Code-Anchored Context guidance');
+        this.note(`${targetDisplay} already has Code-Anchored Context guidance`);
         return;
       }
 
-      await this.writeFile(targetFile, updated, 'update AGENTS.md Code-Anchored Context section');
+      await this.writeFile(targetFile, updated, `update ${targetDisplay} Code-Anchored Context section`);
       return;
     }
 
-    if (current.includes('.agents/skills/development-initiative-context/SKILL.md')) {
-      this.note('AGENTS.md already points to the development initiative skill');
+    if (current.includes(`.agents/skills/${skillName}/SKILL.md`)) {
+      this.note(`${targetDisplay} already points to the Code-Anchored Context skill`);
       return;
     }
 
@@ -266,21 +270,44 @@ class Installer {
     await this.writeFile(
       targetFile,
       `${current}${separator}${section}\n`,
-      'append Code-Anchored Context guidance to AGENTS.md'
+      `append Code-Anchored Context guidance to ${targetDisplay}`
     );
   }
 
+  async findAgentsFile() {
+    const canonicalPath = path.join(this.targetRoot, 'AGENTS.md');
+
+    let entries;
+
+    try {
+      entries = await readdir(this.targetRoot, { withFileTypes: true });
+    } catch {
+      return canonicalPath;
+    }
+
+    if (entries.some((entry) => entry.isFile() && entry.name === 'AGENTS.md')) {
+      return canonicalPath;
+    }
+
+    const match = entries
+      .filter((entry) => entry.isFile() && entry.name.toLowerCase() === 'agents.md')
+      .map((entry) => entry.name)
+      .sort((left, right) => left.localeCompare(right))[0];
+
+    return match ? path.join(this.targetRoot, match) : canonicalPath;
+  }
+
   renderAgentSection() {
     return `${agentSectionStart}
 ## Code-Anchored Context
 
 In-progress specs, plans, ADRs, backlog, implementation context, and
-release-documentation notes live under [\`Development/\`](Development/).
-Start with [\`Development/current.md\`](Development/current.md).
+release-documentation notes live under [\`context/\`](context/).
+Start with [\`context/current.md\`](context/current.md).
 
 For behavior-changing work, use the repo-wide skill at
-[\`.agents/skills/development-initiative-context/SKILL.md\`](.agents/skills/development-initiative-context/SKILL.md).
-Keep initiative knowledge centralized under \`Development/\`; area
+[\`.agents/skills/${skillName}/SKILL.md\`](.agents/skills/${skillName}/SKILL.md).
+Keep initiative knowledge centralized under \`context/\`; area
 \`AGENTS.md\` files should point there rather than copying active plans.
 ${agentSectionEnd}`;
   }
@@ -291,7 +318,13 @@ ${agentSectionEnd}`;
       `.agents/skills/${skillName}`
     );
 
-    const readmePath = path.join(this.targetRoot, '.agents/skills/README.md');
+    const readmeTarget = await this.findExistingTargetPath('.agents/skills/README.md');
+    const readmePath = readmeTarget.exists
+      ? readmeTarget.path
+      : path.join(this.targetRoot, '.agents/skills/README.md');
+    const readmeDisplay = readmeTarget.exists
+      ? readmeTarget.display
+      : '.agents/skills/README.md';
 
     if (!await exists(readmePath)) {
       await this.copyTemplatePath('.agents/skills/README.md', '.agents/skills/README.md');
@@ -301,7 +334,7 @@ ${agentSectionEnd}`;
     const current = await readFile(readmePath, 'utf8');
 
     if (current.includes(skillName)) {
-      this.note('.agents/skills/README.md already lists the development initiative skill');
+      this.note(`${readmeDisplay} already lists the Code-Anchored Context skill`);
       return;
     }
 
@@ -309,33 +342,82 @@ ${agentSectionEnd}`;
       '',
       '## Code-Anchored Context',
       '',
-      `- \`${skillName}\` - use central \`Development/\` initiatives for planning, implementation context, programs, planned initiatives, ADRs, backlog, and release-documentation notes.`,
+      `- \`${skillName}\` - use central \`context/\` initiatives for planning, implementation context, programs, planned initiatives, ADRs, backlog, and release-documentation notes.`,
       ''
     ].join('\n');
 
     await this.writeFile(
       readmePath,
       `${current.trimEnd()}\n${entry}`,
-      'append development initiative skill to .agents/skills/README.md'
+      `append Code-Anchored Context skill to ${readmeDisplay}`
     );
   }
 
   async copyTemplatePath(sourceRelative, targetRelative) {
     const sourcePath = path.join(packageRoot, sourceRelative);
+    const targetInfo = await this.findExistingTargetPath(targetRelative);
     const targetPath = path.join(this.targetRoot, targetRelative);
 
-    if (await exists(targetPath)) {
+    if (targetInfo.exists) {
+      const variantNote = targetInfo.caseVariant ? ` at ${targetInfo.display}` : '';
+
       if (!this.force) {
-        this.note(`skip ${targetRelative} (already exists; use --force to replace)`);
+        this.note(`skip ${targetRelative} (already exists${variantNote}; use --force to replace)`);
         return;
       }
 
-      await this.removePath(targetPath, `replace ${targetRelative}`);
+      await this.removePath(targetInfo.path, `replace ${targetInfo.display}`);
     }
 
     await this.copyRecursive(sourcePath, targetPath, targetRelative);
   }
 
+  async findExistingTargetPath(targetRelative) {
+    const parts = targetRelative.split('/').filter(Boolean);
+    let currentPath = this.targetRoot;
+    const displayParts = [];
+
+    for (const part of parts) {
+      let entries;
+
+      try {
+        entries = await readdir(currentPath, { withFileTypes: true });
+      } catch {
+        return this.missingTargetPath(targetRelative);
+      }
+
+      const exactMatch = entries.find((entry) => entry.name === part);
+      const caseMatch = exactMatch ?? entries.find(
+        (entry) => entry.name.toLowerCase() === part.toLowerCase()
+      );
+
+      if (!caseMatch) {
+        return this.missingTargetPath(targetRelative);
+      }
+
+      currentPath = path.join(currentPath, caseMatch.name);
+      displayParts.push(caseMatch.name);
+    }
+
+    const display = displayParts.join('/');
+
+    return {
+      caseVariant: display !== targetRelative,
+      display,
+      exists: true,
+      path: currentPath
+    };
+  }
+
+  missingTargetPath(targetRelative) {
+    return {
+      caseVariant: false,
+      display: targetRelative,
+      exists: false,
+      path: path.join(this.targetRoot, targetRelative)
+    };
+  }
+
   async copyRecursive(sourcePath, targetPath, displayPath) {
     if (this.shouldSkipTemplatePath(displayPath)) {
       this.note(`skip ${displayPath} (template repository context)`);
@@ -369,7 +451,7 @@ ${agentSectionEnd}`;
   }
 
   shouldSkipTemplatePath(displayPath) {
-    const initiativePrefix = `Development/releases/${defaultRelease}/initiatives/`;
+    const initiativePrefix = `context/releases/${defaultRelease}/initiatives/`;
 
     return (
       displayPath.startsWith(initiativePrefix) &&
@@ -378,11 +460,11 @@ ${agentSectionEnd}`;
   }
 
   transformText(contents, displayPath) {
-    if (displayPath === 'Development/current.md') {
+    if (displayPath === 'context/current.md') {
       return this.renderStarterCurrent();
     }
 
-    if (displayPath === `Development/releases/${defaultRelease}/backlog.md`) {
+    if (displayPath === `context/releases/${defaultRelease}/backlog.md`) {
       return this.renderStarterReleaseBacklog();
     }
 
@@ -394,7 +476,7 @@ ${agentSectionEnd}`;
   }
 
   renderStarterCurrent() {
-    return `# Current Development Context
+    return `# Current Context
 
 Current release: \`${this.release}\`
 
@@ -421,8 +503,8 @@ Registered initiatives:
 
 - None yet.
 
-To start an initiative, copy \`Development/_templates/initiative/\` into
-\`Development/releases/${this.release}/initiatives/<initiative-slug>/\`, then update the
+To start an initiative, copy \`context/_templates/initiative/\` into
+\`context/releases/${this.release}/initiatives/<initiative-slug>/\`, then update the
 copied \`README.md\` first so agents have a clear entry point before editing the
 supporting files.
 `;
@@ -431,7 +513,7 @@ supporting files.
   renderStarterReleaseBacklog() {
     return `# ${this.releaseLabel()} Backlog
 
-This file tracks release-level development context that is not yet captured
+This file tracks release-level working context that is not yet captured
 by an initiative, plus a short summary of initiative progress once
 initiatives exist.
 
@@ -455,15 +537,15 @@ No initiatives registered yet.
     }
 
     await this.renamePath(
-      path.join(this.targetRoot, 'Development/releases', defaultRelease),
-      path.join(this.targetRoot, 'Development/releases', this.release),
-      `rename Development/releases/${defaultRelease} to Development/releases/${this.release}`
+      path.join(this.targetRoot, 'context/releases', defaultRelease),
+      path.join(this.targetRoot, 'context/releases', this.release),
+      `rename context/releases/${defaultRelease} to context/releases/${this.release}`
     );
 
     await this.renamePath(
-      path.join(this.targetRoot, 'Development/_templates/program/releases', `${defaultRelease}.md`),
-      path.join(this.targetRoot, 'Development/_templates/program/releases', `${this.release}.md`),
-      `rename Development/_templates/program/releases/${defaultRelease}.md to ${this.release}.md`
+      path.join(this.targetRoot, 'context/_templates/program/releases', `${defaultRelease}.md`),
+      path.join(this.targetRoot, 'context/_templates/program/releases', `${this.release}.md`),
+      `rename context/_templates/program/releases/${defaultRelease}.md to ${this.release}.md`
     );
   }
 
@@ -533,7 +615,7 @@ No initiatives registered yet.
     console.log(`${prefix}Code-Anchored Context ready for ${this.projectName}.`);
 
     if (!this.dryRun) {
-      console.log(`Next: ask your agent to read ${path.join(this.targetRoot, 'AGENTS.md')}.`);
+      console.log(`Next: ask your agent to read ${this.agentsFilePath}.`);
     }
   }
 }

package/{Development → context}/AGENTS.md

@@ -1,10 +1,10 @@
-# Agent Guidance - Development
+# Agent Guidance - context/
 
-Scope: everything under `/Development`.
+Scope: everything under `/context`.
 
 ## Purpose
 
-This folder is the canonical home for in-progress development context: specs,
+This folder is the canonical home for in-progress working context: specs,
 interface notes, architecture notes, actionable operations notes, ADRs,
 backlogs, implementation plans, and release-documentation notes.
 
@@ -13,30 +13,30 @@ work is verified, shipped, deployed, or hosted. Operational notes belong here
 only when they are actionable runtime, support, observability, rollback, or
 repair context.
 
-`Development/` describes what is being planned, built, debated, or validated.
-`Documentation/` describes what has shipped for a release.
+`context/` describes what is being planned, built, debated, or validated.
+`docs/` describes what has shipped for a release.
 
 ## Editing Rules
 
-- Use `Development/terminology.md` as the canonical vocabulary for programs,
+- Use `context/terminology.md` as the canonical vocabulary for programs,
   planned initiatives, release initiatives, backlog items, and promotion.
 - Keep initiative knowledge centralized here. Area `AGENTS.md` files may point
   here, but they should not duplicate initiative content.
-- Do not move in-progress plans into `Documentation/`.
+- Do not move in-progress plans into `docs/`.
 - Use `release-doc-notes.md` inside an initiative to capture what may need to
   become product documentation later.
-- Create initiatives from `Development/_templates/initiative/`.
-- Create durable multi-release programs from `Development/_templates/program/`.
+- Create initiatives from `context/_templates/initiative/`.
+- Create durable multi-release programs from `context/_templates/program/`.
 - Create scoped future program work from
-  `Development/_templates/planned-initiative/` under a program's
+  `context/_templates/planned-initiative/` under a program's
   `planned-initiatives/` folder.
 - Create deferred isolated backlog items from
-  `Development/_templates/backlog-item.md`.
+  `context/_templates/backlog-item.md`.
 - Keep release initiative history in the release folder. Use `programs/` for
   multi-release context, `planned-initiatives/` for scoped future program work,
   and `backlog/items/` for isolated deferred work.
-- Treat changes to `Development/current.md` as release transitions. Use
-  `Development/_templates/release-transition.md` and promote matching planned
+- Treat changes to `context/current.md` as release transitions. Use
+  `context/_templates/release-transition.md` and promote matching planned
   initiatives for the new current release.
 - When a backlog item is picked up later, mark it as promoted and link to the
   new release initiative instead of rewriting the item into an active plan.

package/{Development → context}/README.md

@@ -1,12 +1,12 @@
-# Development
+# context/
 
-This folder is the working memory for active and historical development
-context in this repository.
+This folder is the working memory for active and historical context in this
+repository.
 
 Use it for specs, interface notes, architecture notes, testing notes, delivery
 notes, infrastructure notes, actionable operations notes, ADRs, backlog items,
 implementation plans, and release-documentation notes. Do not use
-`Documentation/` for in-progress development planning.
+`docs/` for in-progress development planning.
 
 ## Start Here
 
@@ -16,24 +16,24 @@ implementation plans, and release-documentation notes. Do not use
   Code-Anchored Context for human-agent collaboration.
 - `terminology.md` defines the shared vocabulary.
 - `current.md` points to the active release context.
-- `programs/` contains durable multi-release development context.
+- `programs/` contains durable multi-release working context.
 - `backlog/` contains deferred isolated work cut from initiatives.
-- `releases/` contains release-scoped development context.
+- `releases/` contains release-scoped working context.
 - `_templates/initiative/` contains the standard initiative shape.
 - `_templates/planned-initiative/` contains the standard future initiative
   shape for scoped program work outside the current release.
 - `_templates/release-context/` contains the standard release folder shell.
 
-## Relationship To Documentation
+## Relationship To docs/
 
-`Development/` and `Documentation/` serve different jobs:
+`context/` and `docs/` serve different jobs:
 
 | Folder | Meaning | Updated when |
 | --- | --- | --- |
-| `Development/` | What we are planning, building, deciding, or validating. | During normal development. |
-| `Documentation/` | What the product does as of a release or tag. | Only during explicit documentation refresh work. |
+| `context/` | What we are planning, building, deciding, or validating. | During normal development. |
+| `docs/` | What the product does as of a release or tag. | Only during explicit documentation refresh work. |
 
-Development notes can feed release documentation, but they are not product
+Working context can feed release documentation, but it is not product
 documentation. Capture that bridge in each initiative's
 `release-doc-notes.md`.
 
@@ -50,16 +50,16 @@ Some context needs to outlive a single release initiative:
 
 | Place | Use for |
 | --- | --- |
-| `Development/programs/` | Long-lived multi-release efforts, phase history, roadmaps, and durable decisions. |
-| `Development/programs/<program>/planned-initiatives/` | Scoped future delivery slices that belong to a program but are not in the current release yet. |
-| `Development/backlog/items/` | Deferred isolated work cut from an initiative but worth preserving. |
-| `Development/releases/<version>/initiatives/` | Release-scoped delivery slices and historical implementation context. |
+| `context/programs/` | Long-lived multi-release efforts, phase history, roadmaps, and durable decisions. |
+| `context/programs/<program>/planned-initiatives/` | Scoped future delivery slices that belong to a program but are not in the current release yet. |
+| `context/backlog/items/` | Deferred isolated work cut from an initiative but worth preserving. |
+| `context/releases/<version>/initiatives/` | Release-scoped delivery slices and historical implementation context. |
 
 The rule is:
 
 > Active work belongs in a release initiative. Multi-release context belongs in
 > a program. Scoped future program work belongs in a planned initiative.
-> Deferred isolated work belongs in the development backlog.
+> Deferred isolated work belongs in the context backlog.
 
 The delivery-surface rule is:
 
@@ -82,7 +82,7 @@ not copy specs, plans, or ADRs into area-local documents.
 ## Standard Layout
 
 ```text
-Development/
+context/
   current.md
   programs/
     <program-slug>/
@@ -140,11 +140,11 @@ Release initiatives should link to their program when one exists. Programs
 should link back to the release initiatives that delivered each slice.
 
 Do not use a program for a small leftover task. Use
-`Development/backlog/items/` for deferred isolated work.
+`context/backlog/items/` for deferred isolated work.
 
-## Development Backlog
+## Context Backlog
 
-Use `Development/backlog/items/` for isolated work that was taken out of an
+Use `context/backlog/items/` for isolated work that was taken out of an
 initiative's scope but should be kept for later. Each backlog item records its
 origin initiative and release.
 
@@ -214,23 +214,23 @@ Use when relevant:
 When an initiative produces context that needs to survive after the release:
 
 - Move multi-release strategy, roadmap, and durable decisions into
-  `Development/programs/<program-slug>/`.
+  `context/programs/<program-slug>/`.
 - Move scoped future delivery slices into
-  `Development/programs/<program-slug>/planned-initiatives/<initiative-slug>/`.
+  `context/programs/<program-slug>/planned-initiatives/<initiative-slug>/`.
 - Move isolated deferred work into
-  `Development/backlog/items/<originating-initiative-slug>--<item-slug>.md`.
+  `context/backlog/items/<originating-initiative-slug>--<item-slug>.md`.
 - Keep release-scoped plans, implementation history, and final release notes
   inside the original initiative.
 
 ## Changing The Current Release
 
-Changing `Development/current.md` is a release transition, not just a line
-edit. Use `Development/_templates/release-transition.md` as the checklist.
-Create missing release folders from `Development/_templates/release-context/`.
+Changing `context/current.md` is a release transition, not just a line
+edit. Use `context/_templates/release-transition.md` as the checklist.
+Create missing release folders from `context/_templates/release-context/`.
 
 When setting a release as current, agents should scan all program planned
 initiatives for matching `Target release:` metadata and promote matching items
-into `Development/releases/<version>/initiatives/`.
+into `context/releases/<version>/initiatives/`.
 
 The promotion rule is:
 
@@ -241,7 +241,7 @@ The promotion rule is:
 When changing behavior, agents should:
 
 1. Read the local `AGENTS.md`.
-2. Open `Development/current.md`.
+2. Open `context/current.md`.
 3. Check the current release's initiatives for matching context.
 4. Use `plan.md` for live alignment, open questions, and rough thinking.
    Promote settled conclusions into the stable initiative files.
@@ -251,7 +251,7 @@ When changing behavior, agents should:
 7. Create or update a program planned initiative when future scoped work is
    clear but belongs outside the current release.
 8. Record future product-doc impact in `release-doc-notes.md`, not in
-   `Documentation/`, unless a human explicitly asks for documentation refresh.
+   `docs/`, unless a human explicitly asks for documentation refresh.
 
 The key rule for planning is:
 

package/{Development → context}/_templates/backlog-item.md

@@ -1,7 +1,7 @@
 # Backlog Item Title
 
 Status: Candidate
-Originating initiative: `Development/releases/v0_1_0/initiatives/<initiative-slug>/`
+Originating initiative: `context/releases/v0_1_0/initiatives/<initiative-slug>/`
 Originating release: `v0_1_0`
 Area: TBD
 Reason deferred: TBD
@@ -35,6 +35,6 @@ section and leave the item as a historical record.
 
 ```md
 Status: Promoted
-Promoted to: `Development/releases/<version>/initiatives/<initiative-slug>/`
+Promoted to: `context/releases/<version>/initiatives/<initiative-slug>/`
 ```
 

package/{Development → context}/_templates/initiative/README.md

@@ -12,11 +12,15 @@ produce.
 
 ## Touched Areas
 
-- `src/<area>/...`
-- `deploy/...`
-- `automation/...`
+- Product or runtime code: `path/to/...`
+- Interfaces, APIs, or contracts: `path/to/...`
+- Tests or verification: `path/to/...`
+- Delivery, CI/CD, build, or artifacts: `path/to/...`
+- Infrastructure, IaC, or environment config: `path/to/...`
+- Docs or release notes: `path/to/...`
 
-Remove entries that do not apply and add the real paths.
+Remove entries that do not apply and add the real paths. Prefer naming the
+delivery concern over assuming a specific folder layout.
 
 ## Current Source Of Truth
 
@@ -55,5 +59,5 @@ support, observability, rollback, or repair context.
   Promote settled conclusions into the stable initiative files.
 - Update `release-doc-notes.md` when shipped behavior or product-facing
   behavior changes.
-- Do not update `Documentation/` from this initiative unless a human
+- Do not update `docs/` from this initiative unless a human
   explicitly asks for release documentation work.

package/{Development → context}/_templates/initiative/backlog.md

@@ -19,10 +19,10 @@
 Use this section only for work deferred within the active initiative.
 
 If a deferred item should outlive this initiative as future isolated work,
-create a backlog item from `Development/_templates/backlog-item.md` under:
+create a backlog item from `context/_templates/backlog-item.md` under:
 
 ```text
-Development/backlog/items/<originating-initiative-slug>--<item-slug>.md
+context/backlog/items/<originating-initiative-slug>--<item-slug>.md
 ```
 
 - None yet.

package/{Development → context}/_templates/initiative/plan.md

@@ -51,7 +51,7 @@ the canonical initiative files.
 - [ ] Move settled environment and IaC context into `infrastructure.md`
 - [ ] Move actionable runtime/support concerns into `operations.md`
 - [ ] Move executable work into `backlog.md`
-- [ ] Move multi-release context into `Development/programs/`
-- [ ] Move isolated deferred work into `Development/backlog/items/`
+- [ ] Move multi-release context into `context/programs/`
+- [ ] Move isolated deferred work into `context/backlog/items/`
 - [ ] Move durable decisions into `decisions/`
 - [ ] Move product-documentation impact into `release-doc-notes.md`

package/{Development → context}/_templates/initiative/release-doc-notes.md

@@ -1,20 +1,20 @@
-# Release Documentation Notes
+# Release Doc Notes
 
 Use this file to capture product-documentation impact while development is
-in progress. At release time, these notes help refresh `Documentation/`
+in progress. At release time, these notes help refresh `docs/`
 against the final shipped behavior.
 
-Do not edit `Documentation/` from normal development work unless a human
+Do not edit `docs/` from normal development work unless a human
 explicitly asks for a documentation refresh or a specific documentation fix.
 
 ## Product Behavior Changes
 
 - None yet.
 
-## Candidate Documentation Areas
+## Candidate Docs Areas
 
-- `Documentation/<Area>/README.md`
-- `Documentation/<Area>/features/<feature>.md`
+- `docs/<Area>/README.md`
+- `docs/<Area>/features/<feature>.md`
 
 ## QA Or Support Notes