Remove files that are internal working notes, not user documentation:
- CODEWHALE_0_8_68_TRACKER.md — spent release tracker
- HANDOFF_v0.8.68_completion.md — internal agent handoff
- docs/DOGFOOD_v0.8.67_COMPUTER_USE.md, docs/DOGFOOD_v0.8.67_CURSOR_RESULTS.md — dated dogfood logs
- docs/DOGFOOD_AUTOMATIC_WORKFLOWS.md — dated dogfood log (the checked-in
example workflows under docs/examples/dogfood-automatic/ stay)
- docs/TUI_DOGFOOD_INTEGRATION_CHECK_2026-07-12.md — dated check
- docs/evidence/xiaomi-mimo-2026-06-23/** — competitor pricing capture dumps
- assets/screenshot.legacy.png — dead asset
- benchmark_results/deepseek-anthropic-comparison-2026-06-24.md — product noise
Fix the three cross-references: docs/AUTOMATIC_WORKFLOWS.md now points at
the example fixtures directly, docs/PROVIDERS.md drops the evidence link,
and the wf_a2 example prompt references docs/examples/dogfood-automatic/.
docs/examples/** and scripts/release/install-dogfood.sh are kept on purpose.
Prepared with agent assistance for the 0.9.1 public-surface pass.
Signed-off-by: Hunter B <hmbown@gmail.com>
Add a reproducible dogfood runbook and checked-in workflow fixtures for the
four automatic Workflow scenarios (read-only audit, staged worktree fix,
partial failure + synthesis, mid-run cancel), plus WorkflowPanel projection
tests so another engineer can re-run the same checks without guesswork.
Add Fleet launch-shape validation for WhaleFlow IR with a 100-agent default population cap, five recursive rings, and bounded loop/expand requirements. Update the Fleet setup surface and docs to frame Fleet as the durable sub-agent config layer while WhaleFlow owns agent-authored orchestration.
Adds a verifiable dogfood smoke that drives several concurrent exec-style
workers (three healthy + one injected-failure that emits an error event and
exits non-zero) through the real host adapter, asserting distinct terminal
pass/fail outcomes — no external services, no model calls, no codewhale binary.
Documents the automated CI smoke vs the manual `codewhale fleet run` path in
the dogfood spec, and is honest that the manager run-loop cutover to drive real
FleetExecutor workers is still in progress.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Hunter B