You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
v0.9.1 completion board and exact final dogfood gate
Purpose
This is the non-publishing fan-in board. It owns final integration evidence, one exact rebuilt/installed local dogfood, and the stop line. It does not own feature implementation and is intentionally not agent-ready.
Do not start the final freeze until every canonical blocker below is merged, independently reviewed, or explicitly deferred by Hunter.
Every agent-ready implementation issue is self-contained for a fresh clone of Hmbown/CodeWhale: it must name repo-relative entry points, provider-free acceptance, exact validation, dependencies, and the PR handoff. No cloud worker needs /Volumes/VIXinSSD/CW, workspace backups, a maintainer worktree, or a private handoff. Individual cloud workers stop at a tested PR; this board alone owns integration and the local-device dogfood.
Use one fresh clone/branch and one focused PR per issue. Apply agent-in-progress while a worker owns an issue; do not double-assign it or let workers edit this board.
A worker may open a draft early, but it must rebase onto current main and the listed dependencies before review. Closes #N means every checkbox is proven; otherwise use Refs #N (partial).
Consolidated intake
No scope was dropped. Redundant implementation leaves were closed as redirects:
Community evidence stays visible: #4032, #4603, and #4605 remain open under their reporter authors; restored #2889 retains @aboimpinto's design direction and explicit credit.
Native ACP already exists through codewhale serve --acp; verify it provider-free rather than reimplementing it.
Explicit live-account holdouts
Restore xAI device-code OAuth login and surface endpoint errors #4410 remains open for one real xAI tool-bearing turn on the corrected build. Its provider-free implementation and receipts are required; the live account step is neither inferred nor run without Hunter's approval.
Real Kimi K3 entitlement remains a human account check. Provider-free K3/MFJS captures are required; entitlement is not inferred from them.
Final exact-candidate gate
Refresh origin/main, freeze one exact SHA, and record it before building.
Every canonical blocker is merged or explicitly deferred; signed/additive history, DCO, source branches, contributor authorship/trailers, hosted CI, independent audit, and zero unresolved review threads are verified.
Focused tests, all locked TUI tests, formatting/diff checks, strict workspace clippy, and exact hosted CI are green on the frozen tree.
Run codewhale-local-build, codewhale-runtime-smoke, codewhale-tui-acceptance, and codewhale-release-readiness against that exact tree.
Install only through scripts/release/install-dogfood.sh; CLI, compatibility CLI, and TUI all report the frozen SHA.
Provider-free and visual acceptance cover the canonical issues above, native ACP, restart/replay, narrow terminal sizes, and honest route/context/billing/verification receipts.
README screenshot/receipts, changelog, contributor list, completion ledger, and pre-publication packet identify the same candidate.
Leave safe Kimi K3 test commands for Hunter. Do not run live K3 or xAI entitlement/tool-bearing tests without separate approval.
The final install-dogfood.sh run and installed-binary/visual receipt happen on Hunter's selected device. That local step is intentionally not delegated to a generic cloud worker and does not make any implementation issue machine-dependent.
Stop line
Completion means one exact rebuilt and installed local dogfood candidate plus truthful receipts. It does not authorize a tag, GitHub Release, crates/npm publication, public artifact upload, deployment, customer communication, paid resource, or live provider credential. Nothing is published.
v0.9.1 completion board and exact final dogfood gate
Purpose
This is the non-publishing fan-in board. It owns final integration evidence, one exact rebuilt/installed local dogfood, and the stop line. It does not own feature implementation and is intentionally not
agent-ready.Do not start the final freeze until every canonical blocker below is merged, independently reviewed, or explicitly deferred by Hunter.
Every
agent-readyimplementation issue is self-contained for a fresh clone ofHmbown/CodeWhale: it must name repo-relative entry points, provider-free acceptance, exact validation, dependencies, and the PR handoff. No cloud worker needs/Volumes/VIXinSSD/CW, workspace backups, a maintainer worktree, or a private handoff. Individual cloud workers stop at a tested PR; this board alone owns integration and the local-device dogfood.Canonical implementation board
Children, Fleet, and coordination
Evidence, execution, and authority
Durable state, privacy, and terminal UX
Providers, usage, and verification
Skills
/skillsmanager for inventory, audit, install, update, remove, and trustCredit and release records
Cloud execution waves
Use one fresh clone/branch and one focused PR per issue. Apply
agent-in-progresswhile a worker owns an issue; do not double-assign it or let workers edit this board.A worker may open a draft early, but it must rebase onto current
mainand the listed dependencies before review.Closes #Nmeans every checkbox is proven; otherwise useRefs #N (partial).Consolidated intake
No scope was dropped. Redundant implementation leaves were closed as redirects:
Community evidence stays visible: #4032, #4603, and #4605 remain open under their reporter authors; restored #2889 retains @aboimpinto's design direction and explicit credit.
Merged foundation to reverify on the frozen SHA
Native ACP already exists through
codewhale serve --acp; verify it provider-free rather than reimplementing it.Explicit live-account holdouts
Final exact-candidate gate
origin/main, freeze one exact SHA, and record it before building.codewhale-local-build,codewhale-runtime-smoke,codewhale-tui-acceptance, andcodewhale-release-readinessagainst that exact tree.scripts/release/install-dogfood.sh; CLI, compatibility CLI, and TUI all report the frozen SHA.The final
install-dogfood.shrun and installed-binary/visual receipt happen on Hunter's selected device. That local step is intentionally not delegated to a generic cloud worker and does not make any implementation issue machine-dependent.Stop line
Completion means one exact rebuilt and installed local dogfood candidate plus truthful receipts. It does not authorize a tag, GitHub Release, crates/npm publication, public artifact upload, deployment, customer communication, paid resource, or live provider credential. Nothing is published.