WORK-516
ID:WORK-516Status:ready

Remove bespoke plan build/serve render stack

Realize SPEC-120: remove the plan build / plan serve commands and the private static-site generator behind them, now that a plan site is an ordinary refrakt site (entityRoutes + collection, scaffolded by create-refrakt --type plan). This is the deferred removal phase — WORK-273 shipped the deprecation in v0.16.0, and SPEC-071 § Deprecation of plan build / plan serve (step 3) anticipated but scoped it out. The authoring CLI, plan runes, and register/aggregate hooks are untouched.

Priority:mediumComplexity:moderateMilestone:v0.30.0Source:SPEC-120
claude/plan-cli-docs-review-o4nmn6 View source

Criteria completion

Criteria completion: 0 of 9 (0%) checked; tracking started on Jul 23, no incremental history yet0%25%50%75%100%Jul 23Jul 30

Tracking started Jul 23 — check back for trends.

Relationships

Implements 1
Related 5
Branches 2
claude/plan-cli-docs-review-o4nmn6 current ready
claude/v0-30-milestone-review-hg592h donemain ready
History 2
  1. abea158
    Content editedby bjornolofandersson
  2. 0ebc115
    Created (ready)by bjornolofandersson

Acceptance Criteria

  • plan build and plan serve are removed from the CLI (command registration + --help); invoking them yields an unknown-command error, not the deprecation notice
  • The bespoke render stack is deleted: plugins/plan/src/commands/build.ts, serve.ts, render-pipeline.ts (its three-family router + resolveThemeCss), bundle-behaviors.ts, the private HTTP dev server + file watcher + SSE reload, the planLayout shell, and the pagefind invocation
  • Any now-orphaned dependencies (e.g. pagefind) are dropped from plugins/plan/package.json
  • The authoring/management CLI is unchanged and still passes: create / next / update / validate / status / migrate / next-id / history / init
  • The plan plugin's runes, register/aggregate pipeline hooks (pipeline.ts), and entity registration are retained intact
  • Docs stop presenting plan build / plan serve as the way to view plan content and point at the site approach (create-refrakt --type plan for new projects, the entityRoutes config for existing ones): site/content/plan/docs/plan-site.md, plan-cli.md, plan-integrate.md, site/content/runes/plan/{workflow,cli,index}.md, site/content/plan/index.md, site/content/docs/mcp/overview.md
  • CLAUDE.md's "Fall back to the CLI … (refrakt plan serve, refrakt plan build)" note is updated to the site approach
  • A changeset is added recording the removal as a breaking change for the plan plugin
  • npm run build and npm test pass with the render stack removed

Approach

The deprecation notices (serve.ts / build.ts) already point users at the replacement, so this is mechanical deletion plus doc/config cleanup. Delete the command modules and their private pipeline, unregister the commands from the plan CLI entry point, and drop any deps only they used. Keep everything the standard site pipeline consumes — the register/aggregate hooks feed entityRoutes/collection, which is what the plan site now renders through.

Grep for stragglers before finishing: plan serve, plan build, render-pipeline, planLayout, runPipeline (the plan-plugin one, distinct from @refrakt-md/content's), and pagefind across plugins/plan/, site/content/, and CLAUDE.md. This is a breaking change to @refrakt-md/plan, hence the changeset.

Blocked by

  • WORK-273

References

  • SPEC-120 — retire the bespoke plan render stack (the spec this work item realizes)
  • SPEC-071 — plan site scaffolding (shipped); § Deprecation of plan build / plan serve step 3 anticipated this removal
  • WORK-273 — the deprecation phase that deferred removal to a later release
  • SPEC-069 — entityRoutes / contributed routes, the replacement for per-entity render
  • SPEC-070 — collection rune, the replacement for the dashboards and per-status listings