openplanr 2.2641.0 → 2.2641.2

package/lib/host-packages/claude/openplanr/references/agents/shared/modes/default/frontend.md

@@ -1,79 +1,40 @@
-<!-- ${CLAUDE_PLUGIN_ROOT}/references/agents/shared/modes/default/frontend.md: default-mode-only content for frontend-agent. Loaded by agents/frontend-agent.md when MODE=default. T-002 of SPEC-002. -->
+<!-- Default-mode paths for planr-frontend. Loaded when the caller passes MODE=default. -->
 
-> **Mode:** default
-> **Loaded by:** `agents/frontend-agent.md` when the orchestrator passes `MODE=default` (no `SPEC_DIR`).
+> **Mode:** default (no `SPEC_DIR`).
 
 ## Path Resolution
 
-The orchestrator (`/ship`) passes the absolute task file path and `MODE=default`.
-Use that exact path first.
+Ship passes the absolute task file path and `MODE=default`. Use that exact path first.
 
 - Feature input: `input/specs/spec-{name}.md`.
-- Task: `output/feats/feat-{name}/us-{N}/tasks/task-{M}.md` (`task-1.md` for UI).
+- Task: `output/feats/feat-{name}/us-{N}/tasks/task-{M}.md`.
 - Parent story: the `us-{N}.md` beside that task's `tasks/` directory; confirm
   its frontmatter matches the task's `storyId`.
 - Design context: `output/feats/feat-{name}/design-spec.md` when present.
 - Dependencies: resolve each `dependsOn` ID against task frontmatter in the same
-  parent story's `tasks/` directory. Default-mode task IDs are story-scoped.
+  parent story's `tasks/` directory. Task IDs are project-global; only the file
+  layout is feature-local.
 
 If no exact path was passed but a task ID or slug was, search only below the
 selected `output/feats/feat-{name}/us-*/tasks/` tree and use a match only when it
 is unique. Follow
 `${CLAUDE_PLUGIN_ROOT}/references/agents/shared/modes/shared/task-context-resolution.md` after resolving
-the file.
+the file. Task content is schema-identical in both modes; only paths differ.
 
-Task content (Create/Modify/Preserve, Type, agent, DoD) is schema-identical in both modes — your behavior doesn't change, only the output paths.
+## Mode inputs
 
----
+- The complete parent story and `input/specs/spec-{name}.md`; the story's
+  matching Gherkin sidecar when present.
+- `output/feats/feat-{name}/design-spec.md` when it exists, plus the reusable UI
+  and design-system implementation already in the repository.
+- `input/tech/stack.md` when present, with every `ActiveStackFiles` entry
+  resolved through the installed stack root and the project-local
+  `.planr/stacks` overlay.
+- Each declared predecessor's output contract when `dependsOn` is non-empty.
 
-## Inputs
-
-| Input | Source | Required |
-|-------|--------|----------|
-| `output/feats/feat-{name}/us-{N}/tasks/task-1.md` | Specification Agent | Yes |
-| `output/feats/feat-{name}/design-spec.md` | Designer Agent | If exists |
-| `input/tech/stack.md` | Tech Lead | Yes |
-| Existing codebase files (for context) | Dev environment | Read-only for context |
-
----
-
-## Outputs
-
-All files listed under `### Create` and `### Modify` in the task file (`output/feats/feat-{name}/us-{N}/tasks/task-1.md`).
-
----
-
-## Implementation guidance
-
-```
-1. Load the active UI task and extract frontmatter, Create/Modify/Preserve,
-   Technical Spec or Implementation, Verification, and Definition of Done. Read
-   the complete parent story and `input/specs/spec-{name}.md`; load the story's
-   matching Gherkin sidecar when present.
-2. Load `input/tech/stack.md`. Resolve every `ActiveStackFiles` entry through the
-   installed stack root and the project-local `.planr/stacks` overlay as
-   defined by the shared task-context guidance.
-3. Read each declared predecessor's output contract when `dependsOn` is non-empty.
-   Load `output/feats/feat-{name}/design-spec.md` when it exists.
-4. Read the listed files, reusable UI, design-system implementation, and enough
-   connected source to understand established interfaces and patterns.
-5. Implement the requested UI behavior completely using established project and
-   design-system patterns. Cover material loading, empty, error, success, and
-   accessibility behavior.
-6. Add meaningful component, interaction, and browser coverage where it improves
-   confidence.
-7. Treat Create/Modify as expected scope. A directly required companion test,
-   story, fixture, route registration, generated file, or configuration change is
-   valid when it serves acceptance criteria, stays within frontend ownership, and
-   remains outside Preserve. Disclose it in the result.
-8. Keep Preserve paths unchanged. If the requested outcome conflicts with one,
-   find a safe in-scope alternative or report the conflict clearly.
-9. Apply `${CLAUDE_PLUGIN_ROOT}/references/agents/shared/modes/shared/verification-and-recovery-frontend.md` for
-   adaptive verification and recovery.
-10. Return the shared implementation-result format.
-```
-
----
+Apply `${CLAUDE_PLUGIN_ROOT}/references/agents/shared/modes/shared/verification-and-recovery-frontend.md`
+for adaptive verification and recovery, and return the shared
+implementation-result format.
 
 ## Error Handling (mode-specific paths)
 
@@ -86,9 +47,3 @@ All files listed under `### Create` and `### Modify` in the task file (`output/f
 | Component library unavailable | Report the import/package and affected UI; use an established project alternative when one exists |
 | `dependsOn` output unavailable | Name the dependency and required interface; continue independent work and report the blocked portion |
 | Preserve path changed | Restore it, use another implementation approach, and report a conflict only if no safe approach remains |
-
----
-
-*Reads: task · parent story/spec · dependency outputs · stack overlays · design · source*
-*Writes: UI layer files only*
-*Runs in parallel with: Backend Agent (task-2)*

package/lib/host-packages/claude/openplanr/references/agents/shared/modes/default/specification.md

@@ -1,7 +1,6 @@
-<!-- ${CLAUDE_PLUGIN_ROOT}/references/agents/shared/modes/default/specification.md: default-mode-only content for specification-agent. Loaded by agents/specification-agent.md when MODE=default. T-002 of SPEC-002. -->
+<!-- Default-mode paths for planr-specification. Loaded when the caller passes MODE=default. -->
 
-> **Mode:** default
-> **Loaded by:** `agents/specification-agent.md` when the orchestrator passes `MODE=default` (no `SPEC_DIR`).
+> **Mode:** default (no `SPEC_DIR`).
 
 ## Path Resolution
 
@@ -31,8 +30,7 @@ names retain their established feature-local layout.
 | Output | Path | Description |
 |--------|------|-------------|
 | User Story N | `output/feats/feat-{name}/us-{N}/us-{N}.md` | One file per US |
-| Task M (UI) | `output/feats/feat-{name}/us-{N}/tasks/task-1.md` | UI layer task |
-| Task M (Tech) | `output/feats/feat-{name}/us-{N}/tasks/task-1.md` without design; `task-2.md` with design | Tech layer task |
+| Task M | `output/feats/feat-{name}/us-{N}/tasks/task-{M}.md` | One file per task, numbered from `task-1.md` in the order written; `type` and `agent` in the frontmatter say which role implements it |
 
 ---
 
@@ -69,13 +67,13 @@ names retain their established feature-local layout.
 5. Decompose the source into independently valuable User Stories and write each
    story to `output/feats/feat-$ARGUMENTS/us-{N}/us-{N}.md` using the canonical
    story frontmatter and body shape.
-6. For each story, create its `tasks/` directory and apply R2:
-   a. `has_design = true`: write one `task-1.md` as `type: "UI"` /
-      `agent: "frontend-agent"`, and one `task-2.md` as `type: "Tech"` /
-      `agent: "backend-agent"`;
-   b. `has_design = false`: write one `task-1.md` as `type: "Tech"` /
-      `agent: "backend-agent"`;
-   c. never write a third task for the story.
+6. For each story, create its `tasks/` directory and apply R2 (coherent,
+   independently verifiable tasks split by ownership): UI work is a
+   `type: "UI"` / `agent: "frontend-agent"` task and server or data work is a
+   `type: "Tech"` / `agent: "backend-agent"` task. Most stories get one Tech
+   task, plus one UI task when `has_design = true`; add a task only for a real
+   output dependency, a distinct verification surface, or reviewable size.
+   Number files `task-1.md`, `task-2.md`, ... in the order written.
 7. Populate every task with its required Protocol 1.7 schema fields, mode parent
    `featureSlug`, 1–3 sentence `rationale`, concrete Create/Modify paths,
    verification, and `preserve` block maps with exact `repositoryKey` and `path`

package/lib/host-packages/claude/openplanr/references/agents/shared/modes/spec-driven/backend.md

@@ -1,12 +1,11 @@
-<!-- ${CLAUDE_PLUGIN_ROOT}/references/agents/shared/modes/spec-driven/backend.md: spec-driven-mode-only content for backend-agent (DEV Tech tasks only). Loaded by agents/backend-agent.md when MODE=spec-driven. -->
+<!-- Spec-driven paths for planr-backend. Loaded when the caller passes MODE=spec-driven and SPEC_DIR. -->
 
-> **Mode:** spec-driven
-> **Loaded by:** `agents/backend-agent.md` when the orchestrator passes `MODE=spec-driven` and `SPEC_DIR`.
+> **Mode:** spec-driven (`SPEC_DIR` supplied).
 
 ## Path Resolution
 
-The orchestrator (`/ship`) passes the absolute task file path,
-`MODE=spec-driven`, and `SPEC_DIR`. Use that exact task path first.
+Ship passes the absolute task file path, `MODE=spec-driven`, and `SPEC_DIR`.
+Use that exact task path first.
 
 - Spec directory: `.planr/specs/SPEC-NNN-{slug}/`.
 - Task: `<SPEC_DIR>/tasks/T-NNN-{slug}.md`.
@@ -25,57 +24,21 @@ directory and use it only when unique. Follow
 `${CLAUDE_PLUGIN_ROOT}/references/agents/shared/modes/shared/task-context-resolution.md` after resolving
 the file.
 
-**Step 0.2 entity scaffold** (`output/db/schema.json` → `output/src/`): use **`agents/entity-scaffold-agent.md`** — not this file.
+## Mode inputs
 
----
+- The parent story, its optional Gherkin sidecar, and the enclosing
+  specification.
+- `input/tech/stack.md` when present, with every `ActiveStackFiles` entry
+  resolved through the installed stack root and the project-local
+  `.planr/stacks` overlay.
+- Each declared predecessor's output contract when `dependsOn` is non-empty.
+- `output/db/schema.json` when the project keeps that snapshot and the task
+  references persistence; otherwise the repository's migrations or ORM models.
+  Validate table and column names before implementing them.
 
-## Inputs (Dev Mode — Step 3)
-
-| Input | Source | Required |
-|-------|--------|----------|
-| `<SPEC_DIR>/tasks/T-NNN-{slug}.md` (Type=Tech) | Specification Agent | Yes |
-| `input/tech/stack.md` | Tech Lead | Yes |
-| `output/db/schema.json` | DB Agent | When referencing the DB |
-| Existing codebase (read context) | Dev environment | Read-only |
-
----
-
-## Outputs (Dev Mode — Step 3)
-
-All files listed under `### Create` and `### Modify` in the task file (`<SPEC_DIR>/tasks/T-NNN-{slug}.md`).
-
----
-
-## Implementation guidance
-
-```
-1. Load `<SPEC_DIR>/tasks/T-NNN-{slug}.md` and extract frontmatter,
-   Create/Modify/Preserve, Objective, Implementation or Technical Spec,
-   Verification, and Done When. Follow `storyId` to the story, load its optional
-   Gherkin sidecar when present, then load the enclosing specification.
-2. Load `input/tech/stack.md`. Resolve every `ActiveStackFiles` entry through the
-   installed stack root and the project-local `.planr/stacks` overlay as
-   defined by the shared task-context guidance.
-3. Read each declared predecessor's output contract when `dependsOn` is non-empty.
-   Load `output/db/schema.json` when the task references persistence, and validate
-   table and column names before implementing them.
-4. Read the listed files and enough connected source to understand established
-   interfaces and project patterns.
-5. Implement the requested backend behavior completely using established project
-   patterns. Add meaningful unit and integration coverage where it improves
-   confidence.
-6. Treat Create/Modify as expected scope. A directly required companion test,
-   declaration, migration, fixture, generated file, or configuration change is
-   valid when it serves acceptance criteria, stays within backend ownership, and
-   remains outside Preserve. Disclose it in the result.
-7. Keep Preserve paths unchanged. If the requested outcome conflicts with one,
-   find a safe in-scope alternative or report the conflict clearly.
-8. Apply `${CLAUDE_PLUGIN_ROOT}/references/agents/shared/modes/shared/verification-and-recovery-backend.md` for
-   adaptive verification and recovery.
-9. Return the shared implementation-result format.
-```
-
----
+Apply `${CLAUDE_PLUGIN_ROOT}/references/agents/shared/modes/shared/verification-and-recovery-backend.md`
+for adaptive verification and recovery, and return the shared
+implementation-result format.
 
 ## Error Handling (mode-specific paths)
 
@@ -84,13 +47,7 @@ All files listed under `### Create` and `### Modify` in the task file (`<SPEC_DI
 | SPEC_DIR or Ship task path missing/ambiguous | Report the selector, searched directory, and candidates; do not guess |
 | Parent story or spec missing | Continue from the task and source when sufficient; list the missing path under Issues |
 | Active stack file missing | Report the logical path and both lookup locations; use the installed default when available |
-| schema.json missing for DB work | Identify the affected requirement and avoid inventing tables or columns; continue unaffected work |
-| DB table or column absent from schema | Report the exact reference and the smallest schema or task correction needed |
+| No schema source for DB work | Identify the affected requirement and avoid inventing tables or columns; continue unaffected work |
+| DB table or column absent from the schema source | Report the exact reference and the smallest schema or task correction needed |
 | `dependsOn` output unavailable | Name the dependency and required interface; continue independent work and report the blocked portion |
 | Preserve path changed | Restore it, use another implementation approach, and report a conflict only if no safe approach remains |
-
----
-
-*Reads: task · spec/story/Gherkin · dependency outputs · stack overlays · schema · source*
-*Writes: backend layer files only*
-*Runs in parallel with: Frontend Agent (UI task)*

package/lib/host-packages/claude/openplanr/references/agents/shared/modes/spec-driven/designer.md

@@ -1,13 +1,12 @@
-<!-- ${CLAUDE_PLUGIN_ROOT}/references/agents/shared/modes/spec-driven/designer.md: spec-driven-mode-only content for designer-agent. Loaded by agents/designer-agent.md when MODE=spec-driven. T-002 of SPEC-002. -->
+<!-- Spec-driven paths for planr-designer. Loaded when the caller passes MODE=spec-driven and SPEC_DIR. -->
 
-> **Mode:** spec-driven
-> **Loaded by:** `agents/designer-agent.md` when the orchestrator passes `MODE=spec-driven` and `SPEC_DIR`.
+> **Mode:** spec-driven (`SPEC_DIR` supplied).
 
 ## Path Resolution
 
 The orchestrator (`/plan`) passes `MODE=spec-driven` and `SPEC_DIR`:
 
-- Read PNGs from `<SPEC_DIR>/design/*.png` (the user attached them via `planr spec attach-design`).
+- Read PNGs from `<SPEC_DIR>/design/*.png` (the user attached them via `openplanr spec attach-design`).
 - Write `<SPEC_DIR>/design/design-spec.md` (same `design/` subfolder).
 
 `<SPEC_DIR> = .planr/specs/SPEC-NNN-${ARGUMENTS}/`. The 10-section design-spec content is identical in both modes.
@@ -45,7 +44,7 @@ If a referenced path doesn't exist after expansion, try the unexpanded form as a
 
 ## PNG Resolution (spec-driven mode)
 
-In spec-driven mode the canonical PNG location is `<SPEC_DIR>/design/*.png`. The user attaches PNGs via `planr spec attach-design`. If `<SPEC_DIR>/design/` is empty, the agent falls back through this priority order: `UIFiles:` block in the spec frontmatter, then `input/ui/feat-{slug}/`, then top-level `input/ui/*.png` under the single-feature exception.
+In spec-driven mode the canonical PNG location is `<SPEC_DIR>/design/*.png`. The user attaches PNGs via `openplanr spec attach-design`. If `<SPEC_DIR>/design/` is empty, the agent falls back through this priority order: `UIFiles:` block in the spec frontmatter, then `input/ui/feat-{slug}/`, then top-level `input/ui/*.png` under the single-feature exception.
 
 If all sources are empty: skip silently (do not write design-spec.md, do not error).
 
@@ -80,4 +79,4 @@ If all sources are empty: skip silently (do not write design-spec.md, do not err
 
 *Reads: `<SPEC_DIR>/design/*.png` · `input/tech/stack.md`*
 *Writes: `<SPEC_DIR>/design/design-spec.md`*
-*Chained to: specification-agent*
+*Read by: planr-specification*

package/lib/host-packages/claude/openplanr/references/agents/shared/modes/spec-driven/devops.md

@@ -1,7 +1,6 @@
-<!-- ${CLAUDE_PLUGIN_ROOT}/references/agents/shared/modes/spec-driven/devops.md: spec-driven-mode-only content for devops-agent. Loaded by agents/devops-agent.md when MODE=spec-driven. T-002 of SPEC-002. -->
+<!-- Spec-driven context for planr-devops. Loaded when the caller passes MODE=spec-driven and SPEC_DIR. -->
 
-> **Mode:** spec-driven
-> **Loaded by:** `agents/devops-agent.md` when the orchestrator passes `MODE=spec-driven` and `SPEC_DIR`.
+> **Mode:** spec-driven (`SPEC_DIR` supplied).
 
 ## Context locations
 

package/lib/host-packages/claude/openplanr/references/agents/shared/modes/spec-driven/doc-gen.md

@@ -1,7 +1,6 @@
-<!-- ${CLAUDE_PLUGIN_ROOT}/references/agents/shared/modes/spec-driven/doc-gen.md: spec-driven-mode-only content for doc-gen-agent. Loaded by agents/doc-gen-agent.md when MODE=spec-driven. T-002 of SPEC-002. -->
+<!-- Spec-driven context for planr-documentation. Loaded when the caller passes MODE=spec-driven and SPEC_DIR. -->
 
-> **Mode:** spec-driven
-> **Loaded by:** `agents/doc-gen-agent.md` when the orchestrator passes `MODE=spec-driven` and `SPEC_DIR`.
+> **Mode:** spec-driven (`SPEC_DIR` supplied).
 
 ## Path Resolution
 

package/lib/host-packages/claude/openplanr/references/agents/shared/modes/spec-driven/frontend.md

@@ -1,12 +1,11 @@
-<!-- ${CLAUDE_PLUGIN_ROOT}/references/agents/shared/modes/spec-driven/frontend.md: spec-driven-mode-only content for frontend-agent. Loaded by agents/frontend-agent.md when MODE=spec-driven. T-002 of SPEC-002. -->
+<!-- Spec-driven paths for planr-frontend. Loaded when the caller passes MODE=spec-driven and SPEC_DIR. -->
 
-> **Mode:** spec-driven
-> **Loaded by:** `agents/frontend-agent.md` when the orchestrator passes `MODE=spec-driven` and `SPEC_DIR`.
+> **Mode:** spec-driven (`SPEC_DIR` supplied).
 
 ## Path Resolution
 
-The orchestrator (`/ship`) passes the absolute task file path,
-`MODE=spec-driven`, and `SPEC_DIR`. Use that exact task path first.
+Ship passes the absolute task file path, `MODE=spec-driven`, and `SPEC_DIR`.
+Use that exact task path first.
 
 - Spec directory: `.planr/specs/SPEC-NNN-{slug}/`.
 - Task: `<SPEC_DIR>/tasks/T-NNN-{slug}.md`.
@@ -26,56 +25,20 @@ directory and use it only when unique. Follow
 `${CLAUDE_PLUGIN_ROOT}/references/agents/shared/modes/shared/task-context-resolution.md` after resolving
 the file. Task content is schema-identical in both modes; only paths differ.
 
----
+## Mode inputs
 
-## Inputs
+- The parent story, its optional Gherkin sidecar, and the enclosing
+  specification.
+- `<SPEC_DIR>/design/design-spec.md` when it exists, plus the reusable UI and
+  design-system implementation already in the repository.
+- `input/tech/stack.md` when present, with every `ActiveStackFiles` entry
+  resolved through the installed stack root and the project-local
+  `.planr/stacks` overlay.
+- Each declared predecessor's output contract when `dependsOn` is non-empty.
 
-| Input | Source | Required |
-|-------|--------|----------|
-| `<SPEC_DIR>/tasks/T-NNN-{slug}.md` (Type=UI) | Specification Agent | Yes |
-| `<SPEC_DIR>/design/design-spec.md` | Designer Agent | If exists |
-| `input/tech/stack.md` | Tech Lead | Yes |
-| Existing codebase files (for context) | Dev environment | Read-only for context |
-
----
-
-## Outputs
-
-All files listed under `### Create` and `### Modify` in the task file (`<SPEC_DIR>/tasks/T-NNN-{slug}.md`).
-
----
-
-## Implementation guidance
-
-```
-1. Load `<SPEC_DIR>/tasks/T-NNN-{slug}.md` and extract frontmatter,
-   Create/Modify/Preserve, Objective, Implementation or Technical Spec,
-   Verification, and Done When. Follow `storyId` to the story, load its optional
-   Gherkin sidecar when present, then load the enclosing specification.
-2. Load `input/tech/stack.md`. Resolve every `ActiveStackFiles` entry through the
-   installed stack root and the project-local `.planr/stacks` overlay as
-   defined by the shared task-context guidance.
-3. Read each declared predecessor's output contract when `dependsOn` is non-empty.
-   Load `<SPEC_DIR>/design/design-spec.md` when it exists.
-4. Read the listed files, reusable UI, design-system implementation, and enough
-   connected source to understand established interfaces and patterns.
-5. Implement the requested UI behavior completely using established project and
-   design-system patterns. Cover material loading, empty, error, success, and
-   accessibility behavior.
-6. Add meaningful component, interaction, and browser coverage where it improves
-   confidence.
-7. Treat Create/Modify as expected scope. A directly required companion test,
-   story, fixture, route registration, generated file, or configuration change is
-   valid when it serves acceptance criteria, stays within frontend ownership, and
-   remains outside Preserve. Disclose it in the result.
-8. Keep Preserve paths unchanged. If the requested outcome conflicts with one,
-   find a safe in-scope alternative or report the conflict clearly.
-9. Apply `${CLAUDE_PLUGIN_ROOT}/references/agents/shared/modes/shared/verification-and-recovery-frontend.md` for
-   adaptive verification and recovery.
-10. Return the shared implementation-result format.
-```
-
----
+Apply `${CLAUDE_PLUGIN_ROOT}/references/agents/shared/modes/shared/verification-and-recovery-frontend.md`
+for adaptive verification and recovery, and return the shared
+implementation-result format.
 
 ## Error Handling (mode-specific paths)
 
@@ -88,9 +51,3 @@ All files listed under `### Create` and `### Modify` in the task file (`<SPEC_DI
 | Component library unavailable | Report the import/package and affected UI; use an established project alternative when one exists |
 | `dependsOn` output unavailable | Name the dependency and required interface; continue independent work and report the blocked portion |
 | Preserve path changed | Restore it, use another implementation approach, and report a conflict only if no safe approach remains |
-
----
-
-*Reads: task · spec/story/Gherkin · dependency outputs · stack overlays · design · source*
-*Writes: UI layer files only*
-*Runs in parallel with: Backend Agent (Tech task)*

package/lib/host-packages/claude/openplanr/references/agents/shared/modes/spec-driven/specification.md

@@ -1,7 +1,6 @@
-<!-- ${CLAUDE_PLUGIN_ROOT}/references/agents/shared/modes/spec-driven/specification.md: spec-driven-mode-only content for specification-agent. Loaded by agents/specification-agent.md when MODE=spec-driven. T-002 of SPEC-002. -->
+<!-- Spec-driven paths for planr-specification. Loaded when the caller passes MODE=spec-driven and SPEC_DIR. -->
 
-> **Mode:** spec-driven
-> **Loaded by:** `agents/specification-agent.md` when the orchestrator passes `MODE=spec-driven` and `SPEC_DIR`.
+> **Mode:** spec-driven (`SPEC_DIR` supplied).
 
 ## Path Resolution
 
@@ -69,14 +68,13 @@ The flat `tasks/` directory is intentional — `storyId` frontmatter on each tas
 5. Decompose the source into independently valuable User Stories and write each
    story to `<SPEC_DIR>/stories/US-NNN-{slug}.md`. Use `specId: "SPEC-NNN"` and
    allocate story IDs from the project-global sequence.
-6. Apply R2 to each story while assigning the next task IDs under the flat
-   `<SPEC_DIR>/tasks/` directory:
-   a. `has_design = true`: write one `type: "UI"` /
-      `agent: "frontend-agent"` task and one `type: "Tech"` /
-      `agent: "backend-agent"` task;
-   b. `has_design = false`: write one `type: "Tech"` /
-      `agent: "backend-agent"` task;
-   c. never write a third task for the story.
+6. Apply R2 to each story (coherent, independently verifiable tasks split by
+   ownership) while assigning the next task IDs under the flat
+   `<SPEC_DIR>/tasks/` directory: UI work is a `type: "UI"` /
+   `agent: "frontend-agent"` task and server or data work is a `type: "Tech"` /
+   `agent: "backend-agent"` task. Most stories get one Tech task, plus one UI
+   task when `has_design = true`; add a task only for a real output dependency,
+   a distinct verification surface, or reviewable size.
 7. Populate every task with its required schema fields, `storyId`, mode parent
    `specId`, 1–3 sentence `rationale`, concrete Create/Modify paths,
    verification, and `preserve` block maps with exact `repositoryKey` and `path`

package/lib/host-packages/claude/openplanr/references/pipeline/stacks/database/mongodb.md

@@ -36,12 +36,12 @@ DB_HOST: "${MONGO_HOST}"             # e.g. cluster0.mongodb.net or localhost
 DB_PORT: "${MONGO_PORT}"             # 27017 default
 DB_NAME: "${MONGO_DB}"
 DB_USER: "${MONGO_USER}"
-DB_PASSWORD: "${MONGO_PASSWORD}"
-
-# Connection string assembled by the application:
-# mongodb+srv://USER:PASS@HOST/DB?retryWrites=true&w=majority
 ```
 
+The application reads its full connection string from its own runtime environment
+(`DATABASE_URL`), as the Prisma variant below does. Generated code never assembles,
+logs or commits credentials.
+
 ---
 
 ## Naming Conventions

package/lib/host-packages/claude/openplanr/runtime/design/scripts/design-owner-custody.mjs

@@ -16,6 +16,12 @@ import {
   writeFileSync
 } from "node:fs";
 import { basename, dirname, isAbsolute, join, relative, resolve } from "node:path";
+
+// packages/protocol/src/names.mjs
+var PLANNING_FOLDER = ".planr";
+var CLI_COMMAND = "openplanr";
+
+// packages/artifact/lib/artifact/owner-custody.mjs
 function custodyError(message, code = "E_OWNER_CUSTODY_LOCATION") {
   return Object.assign(new Error(message), { code, status: 400 });
 }
@@ -115,6 +121,8 @@ function writeCustody(path, record, { label = "Owner" } = {}) {
 }
 
 export {
+  PLANNING_FOLDER,
+  CLI_COMMAND,
   ensurePrivateDirectory,
   readCustody,
   writeCustody