Repository navigation
Tags
Tags
2.2.0 — Archflow Studio Adds /archflow:studio, a local web workspace over the same .archflow/ files. The roadmap becomes a board, the release becomes a pipeline, and the agents run in a panel instead of a scrollback. Studio onboards a project and migrates a v1.0 one from the UI, so after the plugin install the terminal is optional. Beta. Ships inside this plugin rather than as a second one: ~5.6 MB on every install (2.3 MB server bundle + 3.7 MB SPA), in exchange for one namespace and one install. Also in this release: - A second SessionStart hook, so Studio's chat can fork the session you launched it from rather than opening an unrelated one. - Landing page cut from 15 sections to 12 without deleting any argument, with a Studio section, tabs for the three start paths, and an objections accordion. - New /guides/studio/, and every guide now renders an <h1> (none did). - Em dashes replaced site-wide and in the README. - The announcement bar is opaque; it was a 10% tint over nothing and the page showed through it while scrolling.
feat: add /archflow:autopilot — unattended story runs on a pre-author… …ized envelope (#24) Formalizes a ritual that was being re-typed as a prose prompt every time: review the release's stories, ask about blockers, then build unattended on a branch while the user is asleep or working elsewhere. Two things prose could not guarantee, and the reason this is a command: - Blockers discovered MID-RUN. The pre-flight only catches what is visible in the story text; the ones that bite at 3am surface during implementation. Autopilot never guesses and never stalls: the story is parked with the open question and candidate answers, its WIP committed but unmerged, and the run continues. - Context compaction. A multi-hour run compacts, possibly repeatedly, taking the interview answers with it. The run ledger is durable state, re-read at the top of every story, and makes `resume` possible after a crash. The interview is AskUserQuestion-first: batched (never dripped), every question carrying 2-4 concrete options, and nothing asked that the API contract, design artifacts, or codebase already answer. Authority envelope, fixed and not negotiable at runtime: may branch, commit, run QA and acceptance, and merge into the run branch; may NOT merge or push to main, open a PR, deploy, spend money, or resolve a decision the user did not answer. New: plugin/commands/autopilot.md {plugin/skills/archflow,.archflow}/schemas/autopilot-schema.yaml run ledger Changed: release-schema.yaml `parked` story status + `parked` block (blocks_release, defaulting true, clearable only by the human) phase-5-launch.md ship ritual HALTs on a parked story that blocks release instructions.md command list, ledger, parked in the readiness pipeline, and autopilot named as the ONE approval-gate exception release.md / status.md / SKILL.md / CLAUDE.md / README.md / docs/index.html plugin.json + marketplace.json 2.0.2 -> 2.1.0 Claude-Session: https://claude.ai/code/session_01Ts7WPM32uC4b99tSoviL12 Co-authored-by: azidan <abdallah.zidan@mobilestudioeg.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
PreviousNext