chore(M001/S02): auto-commit after plan-slice
This commit is contained in:
TÂCHES
parent
adf7101883
commit
b2a88d5645
4 changed files with 238 additions and 0 deletions
73
.gsd/milestones/M001/slices/S02/S02-PLAN.md
Normal file
73
.gsd/milestones/M001/slices/S02/S02-PLAN.md
Normal file
|
|
@ -0,0 +1,73 @@
|
|||
# S02: plan_slice + plan_task tools + PLAN/task-plan renderers
|
||||
|
||||
**Goal:** Add DB-backed slice and task planning write paths that persist flat planning payloads, render parse-compatible `S##-PLAN.md` and `tasks/T##-PLAN.md` artifacts from DB state, and keep task plan files present on disk so planning/execution recovery continues to work.
|
||||
**Demo:** Running the S02 planning proof writes slice/task planning data through `gsd_plan_slice` and `gsd_plan_task`, regenerates `S02-PLAN.md` and `tasks/T01-PLAN.md`/`tasks/T02-PLAN.md` from DB, and passes runtime checks that reject missing task plan files.
|
||||
|
||||
## Must-Haves
|
||||
|
||||
- `gsd_plan_slice` validates a flat payload, requires an existing slice, writes slice planning plus task rows transactionally, renders `S##-PLAN.md`, and clears both state and parse caches. (R003)
|
||||
- `gsd_plan_task` validates a flat payload, requires an existing parent slice, writes task planning fields, renders `tasks/T##-PLAN.md`, and clears both caches. (R004)
|
||||
- `renderPlanFromDb()` and `renderTaskPlanFromDb()` emit markdown that still round-trips through `parsePlan()` / `parseTaskPlanFile()` and satisfies `auto-recovery.ts` plan-slice artifact checks, including on-disk task plan existence. (R008, R019)
|
||||
- Prompt and tool registration surfaces expose the new DB-backed planning path instead of leaving slice/task planning as direct file writes.
|
||||
|
||||
## Proof Level
|
||||
|
||||
- This slice proves: integration
|
||||
- Real runtime required: yes
|
||||
- Human/UAT required: no
|
||||
|
||||
## Verification
|
||||
|
||||
- `node --import ./src/resources/extensions/gsd/tests/resolve-ts.mjs --experimental-strip-types --test src/resources/extensions/gsd/tests/plan-slice.test.ts src/resources/extensions/gsd/tests/plan-task.test.ts`
|
||||
- `node --import ./src/resources/extensions/gsd/tests/resolve-ts.mjs --experimental-strip-types --test src/resources/extensions/gsd/tests/markdown-renderer.test.ts src/resources/extensions/gsd/tests/auto-recovery.test.ts src/resources/extensions/gsd/tests/prompt-contracts.test.ts --test-name-pattern="plan-slice|plan-task|renderPlanFromDb|renderTaskPlanFromDb|task plan|DB-backed planning"`
|
||||
|
||||
## Observability / Diagnostics
|
||||
|
||||
- Runtime signals: handler error strings for validation / DB write / render failure, plus stale-render diagnostics from `markdown-renderer.ts` when rendered plan artifacts drift from DB state.
|
||||
- Inspection surfaces: `src/resources/extensions/gsd/tests/plan-slice.test.ts`, `src/resources/extensions/gsd/tests/plan-task.test.ts`, `src/resources/extensions/gsd/tests/markdown-renderer.test.ts`, `src/resources/extensions/gsd/tests/auto-recovery.test.ts`, and SQLite rows returned by `getSlice()`, `getTask()`, and `getSliceTasks()`.
|
||||
- Failure visibility: failed handler result payloads, missing `tasks/T##-PLAN.md` artifact assertions, and renderer/parser mismatches surfaced by the resolver-based test harness.
|
||||
- Redaction constraints: no secrets expected; task-plan frontmatter must expose skill names only, never secret values or environment data.
|
||||
|
||||
## Integration Closure
|
||||
|
||||
- Upstream surfaces consumed: `src/resources/extensions/gsd/tools/plan-milestone.ts`, `src/resources/extensions/gsd/bootstrap/db-tools.ts`, `src/resources/extensions/gsd/gsd-db.ts`, `src/resources/extensions/gsd/markdown-renderer.ts`, `src/resources/extensions/gsd/files.ts`, `src/resources/extensions/gsd/auto-recovery.ts`, and `src/resources/extensions/gsd/prompts/plan-slice.md`.
|
||||
- New wiring introduced in this slice: canonical tool handlers/registrations for `gsd_plan_slice` and `gsd_plan_task`, DB→markdown renderers for slice and task plans, and prompt-contract coverage that points planning flows at those tools.
|
||||
- What remains before the milestone is truly usable end-to-end: S03 still needs replan/reassess structural enforcement, and S04 still needs hot-path caller migration plus DB↔rendered cross-validation.
|
||||
|
||||
## Tasks
|
||||
|
||||
I’m splitting this into three tasks because there are three distinct failure boundaries and each needs its own proof. The highest-risk boundary is renderer compatibility: if the generated `PLAN.md` or task-plan markdown drifts from parser/runtime expectations, the rest of the slice is fake progress. That work goes first and includes the runtime contract around `skills_used` frontmatter and task-plan file existence. Once the render target is stable, the handler/registration work becomes straightforward because S01 already established the validation → transaction → render → invalidate pattern. The last task is prompt/tool-surface closure, which is intentionally small but necessary: without it, the system still has a gap between the new DB-backed implementation and the planning instructions/registrations the LLM actually sees.
|
||||
|
||||
- [ ] **T01: Add DB-backed slice and task plan renderers with compatibility tests** `est:1.5h`
|
||||
- Why: This closes the main transition-window risk first: rendered plan artifacts must stay parse-compatible and satisfy runtime recovery checks before any new planning handler can be trusted.
|
||||
- Files: `src/resources/extensions/gsd/markdown-renderer.ts`, `src/resources/extensions/gsd/tests/markdown-renderer.test.ts`, `src/resources/extensions/gsd/tests/auto-recovery.test.ts`, `src/resources/extensions/gsd/files.ts`
|
||||
- Do: Implement `renderPlanFromDb()` and `renderTaskPlanFromDb()` using existing DB query helpers, emit slice/task markdown that preserves `parsePlan()` and `parseTaskPlanFile()` expectations, include conservative task-plan frontmatter (`estimated_steps`, `estimated_files`, `skills_used`), and add tests that prove rendered slice plans plus task plan files satisfy `verifyExpectedArtifact("plan-slice", ...)`.
|
||||
- Verify: `node --import ./src/resources/extensions/gsd/tests/resolve-ts.mjs --experimental-strip-types --test src/resources/extensions/gsd/tests/markdown-renderer.test.ts src/resources/extensions/gsd/tests/auto-recovery.test.ts --test-name-pattern="renderPlanFromDb|renderTaskPlanFromDb|plan-slice|task plan"`
|
||||
- Done when: DB rows can be rendered into `S##-PLAN.md` and `tasks/T##-PLAN.md` files that parse cleanly and pass the existing plan-slice runtime artifact checks.
|
||||
- [ ] **T02: Implement and register gsd_plan_slice and gsd_plan_task** `est:1.5h`
|
||||
- Why: This delivers the actual S02 capability: flat DB-backed planning tools for slices and tasks that write structured planning state, render truthful markdown, and clear stale caches after success.
|
||||
- Files: `src/resources/extensions/gsd/tools/plan-slice.ts`, `src/resources/extensions/gsd/tools/plan-task.ts`, `src/resources/extensions/gsd/bootstrap/db-tools.ts`, `src/resources/extensions/gsd/gsd-db.ts`, `src/resources/extensions/gsd/tests/plan-slice.test.ts`, `src/resources/extensions/gsd/tests/plan-task.test.ts`
|
||||
- Do: Follow the S01 handler pattern exactly for both tools, add any missing DB upsert/query helpers needed to populate task planning fields and retrieve slice/task planning state, register canonical tools plus aliases in `db-tools.ts`, and test validation, missing-parent rejection, transactional DB writes, render-failure handling, idempotent reruns, and observable cache invalidation.
|
||||
- Verify: `node --import ./src/resources/extensions/gsd/tests/resolve-ts.mjs --experimental-strip-types --test src/resources/extensions/gsd/tests/plan-slice.test.ts src/resources/extensions/gsd/tests/plan-task.test.ts`
|
||||
- Done when: `gsd_plan_slice` and `gsd_plan_task` exist as registered DB tools, reject malformed input, render plan artifacts after successful writes, and refresh parse-visible state immediately.
|
||||
- [ ] **T03: Close prompt and contract coverage around DB-backed slice planning** `est:45m`
|
||||
- Why: The implementation is incomplete until the planning prompt/test surface actually points at the new tools and proves the DB-backed route is the expected contract instead of manual markdown edits.
|
||||
- Files: `src/resources/extensions/gsd/prompts/plan-slice.md`, `src/resources/extensions/gsd/tests/prompt-contracts.test.ts`, `src/resources/extensions/gsd/bootstrap/db-tools.ts`, `src/resources/extensions/gsd/tests/plan-slice-prompt.test.ts`
|
||||
- Do: Update the slice planning prompt text to require tool-backed planning state when `gsd_plan_slice` / `gsd_plan_task` are available, tighten prompt-contract assertions for the new tools, and add/adjust prompt template tests so the planning surface stays aligned with the registered tool path.
|
||||
- Verify: `node --import ./src/resources/extensions/gsd/tests/resolve-ts.mjs --experimental-strip-types --test src/resources/extensions/gsd/tests/prompt-contracts.test.ts src/resources/extensions/gsd/tests/plan-slice-prompt.test.ts --test-name-pattern="plan-slice|plan task|DB-backed"`
|
||||
- Done when: slice planning prompts and prompt tests explicitly reference the DB-backed slice/task planning tools and no longer leave direct plan-file writes as the intended path.
|
||||
|
||||
## Files Likely Touched
|
||||
|
||||
- `src/resources/extensions/gsd/gsd-db.ts`
|
||||
- `src/resources/extensions/gsd/markdown-renderer.ts`
|
||||
- `src/resources/extensions/gsd/tools/plan-slice.ts`
|
||||
- `src/resources/extensions/gsd/tools/plan-task.ts`
|
||||
- `src/resources/extensions/gsd/bootstrap/db-tools.ts`
|
||||
- `src/resources/extensions/gsd/prompts/plan-slice.md`
|
||||
- `src/resources/extensions/gsd/tests/plan-slice.test.ts`
|
||||
- `src/resources/extensions/gsd/tests/plan-task.test.ts`
|
||||
- `src/resources/extensions/gsd/tests/markdown-renderer.test.ts`
|
||||
- `src/resources/extensions/gsd/tests/auto-recovery.test.ts`
|
||||
- `src/resources/extensions/gsd/tests/prompt-contracts.test.ts`
|
||||
- `src/resources/extensions/gsd/tests/plan-slice-prompt.test.ts`
|
||||
58
.gsd/milestones/M001/slices/S02/tasks/T01-PLAN.md
Normal file
58
.gsd/milestones/M001/slices/S02/tasks/T01-PLAN.md
Normal file
|
|
@ -0,0 +1,58 @@
|
|||
---
|
||||
estimated_steps: 5
|
||||
estimated_files: 4
|
||||
skills_used:
|
||||
- create-gsd-extension
|
||||
- test
|
||||
- debug-like-expert
|
||||
---
|
||||
|
||||
# T01: Add DB-backed slice and task plan renderers with compatibility tests
|
||||
|
||||
**Slice:** S02 — plan_slice + plan_task tools + PLAN/task-plan renderers
|
||||
**Milestone:** M001
|
||||
|
||||
## Description
|
||||
|
||||
Implement the missing DB→markdown renderers for slice plans and task plans before touching tool handlers. This task owns the compatibility boundary for S02: the generated `S##-PLAN.md` and `tasks/T##-PLAN.md` files must still satisfy `parsePlan()`, `parseTaskPlanFile()`, `auto-recovery.ts`, and executor skill activation via `skills_used` frontmatter.
|
||||
|
||||
## Steps
|
||||
|
||||
1. Read the existing renderer helpers in `src/resources/extensions/gsd/markdown-renderer.ts` and the parser/runtime expectations in `src/resources/extensions/gsd/files.ts` and `src/resources/extensions/gsd/auto-recovery.ts`.
|
||||
2. Implement `renderPlanFromDb()` so it reads slice/task rows from `src/resources/extensions/gsd/gsd-db.ts`, emits a complete slice plan document with goal, demo, must-haves, verification, and task checklist entries, and writes/stores the artifact through the existing renderer helpers.
|
||||
3. Implement `renderTaskPlanFromDb()` so it emits a task plan file with valid frontmatter fields (`estimated_steps`, `estimated_files`, `skills_used`) and the required markdown sections from the task row.
|
||||
4. Add renderer tests in `src/resources/extensions/gsd/tests/markdown-renderer.test.ts` covering parse compatibility, DB artifact persistence, and on-disk output shape for both renderers.
|
||||
5. Extend `src/resources/extensions/gsd/tests/auto-recovery.test.ts` to prove a rendered slice plan plus rendered task plan files passes `verifyExpectedArtifact("plan-slice", ...)`, and that missing task-plan files still fail.
|
||||
|
||||
## Must-Haves
|
||||
|
||||
- [ ] `renderPlanFromDb()` generates parse-compatible `S##-PLAN.md` content from DB state.
|
||||
- [ ] `renderTaskPlanFromDb()` generates parse-compatible `tasks/T##-PLAN.md` content with conservative `skills_used` frontmatter.
|
||||
- [ ] Renderer tests cover both happy-path rendering and the runtime contract that task plan files must exist on disk for `plan-slice` verification.
|
||||
|
||||
## Verification
|
||||
|
||||
- `node --import ./src/resources/extensions/gsd/tests/resolve-ts.mjs --experimental-strip-types --test src/resources/extensions/gsd/tests/markdown-renderer.test.ts src/resources/extensions/gsd/tests/auto-recovery.test.ts --test-name-pattern="renderPlanFromDb|renderTaskPlanFromDb|plan-slice|task plan"`
|
||||
- Inspect the passing assertions in `src/resources/extensions/gsd/tests/markdown-renderer.test.ts` and `src/resources/extensions/gsd/tests/auto-recovery.test.ts` for rendered `PLAN.md` / `T##-PLAN.md` behavior.
|
||||
|
||||
## Observability Impact
|
||||
|
||||
- Signals added/changed: stale-render diagnostics and renderer test assertions now cover slice/task plan artifacts in addition to roadmap/summary artifacts.
|
||||
- How a future agent inspects this: run the targeted resolver-harness test command above and inspect generated artifacts via `getArtifact()` / disk files from the renderer tests.
|
||||
- Failure state exposed: parser incompatibility, missing task-plan files, and DB/artifact drift become explicit test failures instead of silent execution-time regressions.
|
||||
|
||||
## Inputs
|
||||
|
||||
- `src/resources/extensions/gsd/markdown-renderer.ts` — existing render helper patterns and artifact persistence hooks
|
||||
- `src/resources/extensions/gsd/gsd-db.ts` — slice/task query fields available to renderers
|
||||
- `src/resources/extensions/gsd/files.ts` — parser expectations for `PLAN.md` and task-plan frontmatter
|
||||
- `src/resources/extensions/gsd/auto-recovery.ts` — runtime artifact checks that the rendered files must satisfy
|
||||
- `src/resources/extensions/gsd/tests/markdown-renderer.test.ts` — current renderer test patterns to extend
|
||||
- `src/resources/extensions/gsd/tests/auto-recovery.test.ts` — existing `plan-slice` artifact enforcement tests
|
||||
|
||||
## Expected Output
|
||||
|
||||
- `src/resources/extensions/gsd/markdown-renderer.ts` — new `renderPlanFromDb()` and `renderTaskPlanFromDb()` implementations
|
||||
- `src/resources/extensions/gsd/tests/markdown-renderer.test.ts` — coverage for slice/task plan rendering and parse compatibility
|
||||
- `src/resources/extensions/gsd/tests/auto-recovery.test.ts` — coverage proving rendered task-plan files satisfy `plan-slice` runtime checks
|
||||
- `src/resources/extensions/gsd/files.ts` — only if a parser-facing compatibility adjustment is required by the new truthful renderer output
|
||||
60
.gsd/milestones/M001/slices/S02/tasks/T02-PLAN.md
Normal file
60
.gsd/milestones/M001/slices/S02/tasks/T02-PLAN.md
Normal file
|
|
@ -0,0 +1,60 @@
|
|||
---
|
||||
estimated_steps: 5
|
||||
estimated_files: 6
|
||||
skills_used:
|
||||
- create-gsd-extension
|
||||
- test
|
||||
- debug-like-expert
|
||||
---
|
||||
|
||||
# T02: Implement and register gsd_plan_slice and gsd_plan_task
|
||||
|
||||
**Slice:** S02 — plan_slice + plan_task tools + PLAN/task-plan renderers
|
||||
**Milestone:** M001
|
||||
|
||||
## Description
|
||||
|
||||
Add the actual DB-backed planning tools for slices and tasks, reusing the S01 handler pattern instead of inventing new plumbing. This task should leave the extension with canonical `gsd_plan_slice` and `gsd_plan_task` registrations, flat validation, transactional DB writes, truthful plan rendering, and observable cache invalidation proof.
|
||||
|
||||
## Steps
|
||||
|
||||
1. Read `src/resources/extensions/gsd/tools/plan-milestone.ts` and mirror its validate → transaction → render → invalidate flow for slice/task planning.
|
||||
2. Add any missing DB helpers in `src/resources/extensions/gsd/gsd-db.ts` needed to upsert slice planning fields, create/update task planning rows, and query the rendered state used by the handlers.
|
||||
3. Implement `src/resources/extensions/gsd/tools/plan-slice.ts` with flat input validation, parent-slice existence checks, transactional writes of slice planning plus task rows, renderer invocation, and cache invalidation after successful render.
|
||||
4. Implement `src/resources/extensions/gsd/tools/plan-task.ts` with flat input validation, parent-slice existence checks, task row upsert logic, task-plan rendering, and post-success cache invalidation.
|
||||
5. Register both tools and any aliases in `src/resources/extensions/gsd/bootstrap/db-tools.ts`, then add focused handler tests in `src/resources/extensions/gsd/tests/plan-slice.test.ts` and `src/resources/extensions/gsd/tests/plan-task.test.ts` for validation, idempotence, render failure behavior, and parse-visible cache updates.
|
||||
|
||||
## Must-Haves
|
||||
|
||||
- [ ] `gsd_plan_slice` exists as a registered DB-backed tool and writes/renders slice planning state from a flat payload.
|
||||
- [ ] `gsd_plan_task` exists as a registered DB-backed tool and writes/renders task planning state from a flat payload.
|
||||
- [ ] Both handlers invalidate `invalidateStateCache()` and `clearParseCache()` only after successful DB write + render, with observable tests proving parse-visible state updates.
|
||||
|
||||
## Verification
|
||||
|
||||
- `node --import ./src/resources/extensions/gsd/tests/resolve-ts.mjs --experimental-strip-types --test src/resources/extensions/gsd/tests/plan-slice.test.ts src/resources/extensions/gsd/tests/plan-task.test.ts`
|
||||
- `node --import ./src/resources/extensions/gsd/tests/resolve-ts.mjs --experimental-strip-types --test src/resources/extensions/gsd/tests/plan-slice.test.ts src/resources/extensions/gsd/tests/plan-task.test.ts src/resources/extensions/gsd/tests/markdown-renderer.test.ts --test-name-pattern="cache|idempotent|render failed|validation failed|plan-slice|plan-task"`
|
||||
|
||||
## Observability Impact
|
||||
|
||||
- Signals added/changed: new handler error payloads for validation / DB write / render failures, plus observable cache-invalidation assertions for slice/task planning writes.
|
||||
- How a future agent inspects this: run the targeted plan-slice/plan-task test files and inspect `details.operation`, DB rows, and rendered artifacts captured by those tests.
|
||||
- Failure state exposed: malformed input, missing parent slice, renderer failure, and stale parse-visible state become direct testable outcomes.
|
||||
|
||||
## Inputs
|
||||
|
||||
- `src/resources/extensions/gsd/tools/plan-milestone.ts` — canonical planning handler pattern from S01
|
||||
- `src/resources/extensions/gsd/bootstrap/db-tools.ts` — current DB tool registration surface
|
||||
- `src/resources/extensions/gsd/gsd-db.ts` — existing slice/task storage and query primitives
|
||||
- `src/resources/extensions/gsd/markdown-renderer.ts` — renderer functions produced by T01
|
||||
- `src/resources/extensions/gsd/tests/plan-milestone.test.ts` — reference shape for planning handler tests
|
||||
- `src/resources/extensions/gsd/tests/markdown-renderer.test.ts` — renderer proof surfaces the handlers rely on
|
||||
|
||||
## Expected Output
|
||||
|
||||
- `src/resources/extensions/gsd/tools/plan-slice.ts` — DB-backed slice planning handler
|
||||
- `src/resources/extensions/gsd/tools/plan-task.ts` — DB-backed task planning handler
|
||||
- `src/resources/extensions/gsd/bootstrap/db-tools.ts` — tool registration for `gsd_plan_slice` and `gsd_plan_task`
|
||||
- `src/resources/extensions/gsd/gsd-db.ts` — any missing upsert/query helpers for slice/task planning state
|
||||
- `src/resources/extensions/gsd/tests/plan-slice.test.ts` — slice planning handler regression coverage
|
||||
- `src/resources/extensions/gsd/tests/plan-task.test.ts` — task planning handler regression coverage
|
||||
47
.gsd/milestones/M001/slices/S02/tasks/T03-PLAN.md
Normal file
47
.gsd/milestones/M001/slices/S02/tasks/T03-PLAN.md
Normal file
|
|
@ -0,0 +1,47 @@
|
|||
---
|
||||
estimated_steps: 4
|
||||
estimated_files: 4
|
||||
skills_used:
|
||||
- create-gsd-extension
|
||||
- test
|
||||
---
|
||||
|
||||
# T03: Close prompt and contract coverage around DB-backed slice planning
|
||||
|
||||
**Slice:** S02 — plan_slice + plan_task tools + PLAN/task-plan renderers
|
||||
**Milestone:** M001
|
||||
|
||||
## Description
|
||||
|
||||
Finish the slice by aligning the planning prompt surface with the new implementation. This task is intentionally smaller: once the renderer and handlers exist, the remaining risk is the LLM still being told to treat direct markdown writes as normal. Tighten the prompt wording and contract tests so the DB-backed slice/task planning route is the explicit expected behavior.
|
||||
|
||||
## Steps
|
||||
|
||||
1. Read the current planning prompt text in `src/resources/extensions/gsd/prompts/plan-slice.md` and the existing assertions in `src/resources/extensions/gsd/tests/prompt-contracts.test.ts` and `src/resources/extensions/gsd/tests/plan-slice-prompt.test.ts`.
|
||||
2. Update `src/resources/extensions/gsd/prompts/plan-slice.md` to explicitly direct slice/task planning through `gsd_plan_slice` and `gsd_plan_task` when the tool path exists, while preserving the existing decomposition instructions and output requirements.
|
||||
3. Extend prompt contract tests so they assert the new tool-backed instructions and reject regressions back to manual `PLAN.md` / task-plan writes as the intended source of truth.
|
||||
4. Update prompt template tests if needed so variable substitution and template integrity still pass with the new instructions.
|
||||
|
||||
## Must-Haves
|
||||
|
||||
- [ ] `plan-slice.md` explicitly points planning at `gsd_plan_slice` / `gsd_plan_task` instead of only warning about direct `PLAN.md` writes.
|
||||
- [ ] Prompt contract tests fail if the DB-backed slice/task planning tool instructions regress.
|
||||
- [ ] Prompt template tests still pass after the wording change.
|
||||
|
||||
## Verification
|
||||
|
||||
- `node --import ./src/resources/extensions/gsd/tests/resolve-ts.mjs --experimental-strip-types --test src/resources/extensions/gsd/tests/prompt-contracts.test.ts src/resources/extensions/gsd/tests/plan-slice-prompt.test.ts --test-name-pattern="plan-slice|plan task|DB-backed"`
|
||||
- Read the relevant assertions in `src/resources/extensions/gsd/tests/prompt-contracts.test.ts` to confirm they mention `gsd_plan_slice` / `gsd_plan_task`.
|
||||
|
||||
## Inputs
|
||||
|
||||
- `src/resources/extensions/gsd/prompts/plan-slice.md` — current slice planning prompt
|
||||
- `src/resources/extensions/gsd/tests/prompt-contracts.test.ts` — prompt regression contract tests
|
||||
- `src/resources/extensions/gsd/tests/plan-slice-prompt.test.ts` — template substitution/integrity tests
|
||||
- `src/resources/extensions/gsd/bootstrap/db-tools.ts` — canonical tool names to reference in the prompt/tests
|
||||
|
||||
## Expected Output
|
||||
|
||||
- `src/resources/extensions/gsd/prompts/plan-slice.md` — updated DB-backed slice/task planning instructions
|
||||
- `src/resources/extensions/gsd/tests/prompt-contracts.test.ts` — stronger prompt contract coverage for `gsd_plan_slice` / `gsd_plan_task`
|
||||
- `src/resources/extensions/gsd/tests/plan-slice-prompt.test.ts` — updated template tests if prompt wording changes affect expectations
|
||||
Loading…
Add table
Reference in a new issue