v0.5.0-rc.0 is the release candidate before the 0.5.0 stable release. This build focuses on release stabilization: non-interactive init recovery, workflow breadcrumbs reading from workflow.md, automatic workflow.md breadcrumb updates, and bundled trellis-meta reference updates.
Enhancements
Workflow breadcrumbs
Per-turn workflow breadcrumbs, the short prompts that tell the AI which workflow step it is in, now read from.trellis/workflow.md [workflow-state:STATUS] blocks.
The parser and stripper both require matched tag pairs:
Automatic workflow.md breadcrumb updates
trellis update now refreshes the [workflow-state:*] blocks in .trellis/workflow.md. Hooks read those blocks to tell the AI what to do next; normal prose outside the blocks is still left alone.
The implementation lives in
buildWorkflowMdTemplate (packages/cli/src/commands/update.ts).
Session active task after task.py create
task.py create now best-effort sets the session active-task pointer. The planning breadcrumb becomes reachable immediately after creating a task, so the AI sees Phase 1.1 through Phase 1.4 guidance instead of falling back to the no-task path.
trellis continue also routes by task.json.status plus required artifacts, including the Phase 1.4 activation branch after prd.md and jsonl context are ready.
Bundled trellis-meta references
The bundled trellis-meta skill now describes how workflow-state reads workflow.md consistently across its reference pages:
Bug Fixes
Non-interactive trellis init --yes
trellis init --yes now stays non-interactive when files already exist.
--force still overwrites existing files. --yes preserves them by default.
Aborted first-init recovery
If an earlier init wrote.trellis/ but aborted before creating any task, rerunning init now creates the bootstrap task instead of routing to joiner onboarding.
The empty-
tasks/ early check bypasses handleReinit, then the main dispatch’s bootstrap fallback runs.
Testing
Init recovery coverage
The init suite now covers:Workflow-state coverage
Regression coverage now guards:Upgrade
Install the RC:0.5.0-rc.0 adds no new migration entries, but 0.4.x projects still need the 0.5 migration chain that starts at 0.5.0-beta.0.