v0.6.3 — Cross-project agent onboarding

vibe-council v0.6.3 — Cross-project agent onboarding

Ready for the v0.6.3 tag — not yet tagged. The version bump (backend/__init__.py,
pyproject.toml, uv.lock) and the dated CHANGELOG.md section are done
(chore: prepare v0.6.3 release); the repo now reports 0.6.3. The git tag and the GitHub
Release are still a separate, manual step — see §"Final release checklist" below and
docs/release-checklist.md.

The cross-project agent onboarding release. On top of the v0.6.0 agent-to-Workbench proposal
bridge, this bundles the v0.6.1–v0.6.3 onboarding arc: a role-aware vibe guide layer, a local-first
Markdown project vault, a read-only vibe project doctor, and a read-only vibe context export --for <agent> handoff. Everything here is read-only and local: no model/provider/network call, no
Workbench trust-boundary change, no /council command (vibe is the real CLI), no new dependency.
Based on and crediting karpathy/llm-council.

No commercial-clearance claim. License/provenance remains an unresolved "Question 0"
commercial gate; no LICENSE is added.

What this release adds

Role-aware guide layer (v0.6.1)

• vibe guide claude --role <role> — a read-only stdout generator printing a role-tailored
  instruction block. Roles: task-shaper, planner, coder, reviewer, release-manager. Each
  pairs a role-specific workflow with the common rules (this project's CLI is vibe not /council;
  council is a reviewer/context/memory layer, not an implementer; the cheap/balanced/full preset
  policy; before/after-coding workflow; the Workbench proposal-bridge basics; the never-stage list).
• Opt-in --write — vibe guide claude --role <role> --write [FILE] appends the role's
  section to a CLAUDE.md-style file (default CLAUDE.md) and reports the path. Append-only with a
  per-role marker: never overwrites/truncates, re-runs are skipped, and roles coexist in one file.
• Claude / Codex / Fable topics — vibe guide {claude|codex|fable} [--role <role>] [--write [FILE]], reusing the same machinery. Default --write targets: CLAUDE.md, AGENTS.md,
  FABLE.md. Codex emphasizes using vibe as a reviewer/guardrail and proposing (not bypassing)
  Workbench actions; Fable documents its cost/technical-lead policy — plan-first, curated
  docs/context//docs/fable/ packs (not broad scans), Opus/Sonnet implement routine PRs, and Fable
  reserved for major phase planning / critical architecture-security blockers / high-leverage reviews.

Project vault (v0.6.2)

• A local-first, Markdown, human- and agent-readable project-memory vault under
  docs/context/project/: README.md, STATUS.md, ROADMAP.md, DECISIONS.md (an index/pointer
  into docs/decisions/, never a competing canonical store), PROGRESS.md, RISKS.md,
  WORKFLOWS.md, NOTES.md. Each file states what belongs there and what must never go there
  (secrets, API keys, private paths, runtime payloads, raw outputs, private plans).
• The context builder is unchanged — the pack stays a budgeted projection (STATUS.md + decision
  index; context check 21/21 preserved). The vault is read directly and discovered via pointers,
  not injected into the budgeted pack.

Project doctor (v0.6.2)

• vibe project doctor — a read-only onboarding-readiness diagnostic (new project subcommand,
  distinct from the provider vibe doctor). Checks the vault + core onboarding docs are present; that
  no dangerous file is staged (.env / .council/ / .council/runtime/ / private plans → fail;
  a staged uv.lock → advisory warning); a context-health summary (in-memory
  build_pack/check_pack); and lists the vibe guide commands. Exit 0 when ready; non-zero with
  next steps otherwise; git-unavailable degrades to a warning. Read-only: writes no files, creates
  no .council/, makes no model/provider/network call.

Agent context export (v0.6.3)

• vibe context export --for {claude|codex|fable} [--role <role>] [--output FILE] — a read-only
  onboarding context handoff. Prints Markdown to stdout by default; --output FILE writes it and
  never overwrites an existing file. It bundles a header (vibe real / /council future), a
  vibe project doctor recommendation, project-vault pointers (not a full vault dump), a
  context-health summary built in-memory (no .council/ written), the Workbench proposal flow
  (propose → human approves → guarded execute; no auto-execution; raw payload never rendered), and the
  operating rules + agent guidance + never-stage list. The existing vibe context export claude-code
  behavior is unchanged.

Safety posture — unchanged from v0.6.0

Nothing in this release changes the security model; everything added is read-only/local:

• No model/provider/API/network call from any of the new onboarding commands.
• No Workbench trust-boundary change — approval stays separate from execution, the deterministic
  trust boundary remains authoritative, the auditor stays advisory, and there is no
  auto-execution. The Workbench/importer/panel/executor are untouched.
• /council is not a real command — it stays a documented future host-command idea; vibe
  remains the real CLI (the onboarding docs say so explicitly).
• No command-allowlist change, no new dependency, no new network surface.
• Redaction lint remains 0 critical; context check and MCP health remain 21/21.

Explicit non-goals (deferred, not started in this release)

No project init · no interactive launcher / vibe council start · no Obsidian plugin · no vector DB ·
no hosted / SaaS stack · no Next.js / Postgres / Redis / Docker / LangGraph adoption · no
personalization implementation (v0.7) · no mobile/LAN/voice (v0.8) · no hosted/team (v0.9+). The
onboarding surface is a set of read-only generators/diagnostics, not a runtime.

Release checklist (must be clean before tagging)

• python -m unittest discover -s tests -t . is green (749 tests).
• uv run python -m backend.cli --version prints vibe-council 0.6.3.
• vibe lint --redaction reports 0 critical findings.
• vibe decisions lint passes.
• vibe context check scores 21/21.
• vibe mcp inspect --context --health scores 21/21.
• uv sync produces no uv.lock diff beyond the intentional self-version sync in this PR.
• No .council/ artifact (including .council/runtime/payloads/) staged/committed.
• No private/local plan file staged/committed.

Final release checklist (manual steps, after this PR merges)

These are not automated by this PR — a maintainer performs them once the checklist above is clean
on master:

• Merge this PR (chore: prepare v0.6.3 release) into master.
• On the merged master, re-confirm: tests green, redaction lint 0 critical, decisions lint
  passes, context check 21/21, MCP health 21/21.
• Verify git status --short and the merged diff carry no private/local artifacts
  (.council/, the two untracked private plan files, .env/.venv//data/, secrets,
  generated packs/exports).
• vibe --version on master prints vibe-council 0.6.3.
• Create an annotated git tag: git tag -a v0.6.3 -m "vibe-council v0.6.3" on the merge
  commit, then git push origin v0.6.3.
• Create the GitHub Release for v0.6.3 manually, using this document
  (docs/releases/v0.6.3.md) as the release-notes body.

Known limitations

• Onboarding is read-only generators/diagnostics — vibe guide/project doctor/context export
  print (or, for guide --write/export --output, append/write a user-chosen file); none are
  interactive launchers and none run a model.
• The project vault is curated, committed Markdown — not a database, not an Obsidian dependency.
• Intentionally local-only — the Workbench binds 127.0.0.1; agent intake is file/CLI only.
• No hosted/team/mobile/voice yet — deferred to later phases.

Next after v0.6.3

Cut the v0.6.3 tag/GitHub Release, then scope the next phase per
docs/fable/04-roadmap.md: personalization (v0.7) is the next candidate,
with mobile/LAN/voice (v0.8) and hosted/team (v0.9+) deferred behind the local core.