v0.8.7 — GitHub Projects integration + documenter end-to-end dogfood

v0.8.7 — 2026-04-21 — GitHub Projects integration (the Issues-lifecycle's deferred-work half) + documenter end-to-end dogfood

Closes the symmetric gap opened by v0.8.2: where /bugfix maintains a public GitHub Issue as bug posterity, now /plan, /work, /review, and /release each offer to file deferred-work items to a user- or org-owned ProjectsV2 board linked to the repo. Opt-in at /setup, preview-and-ask at every gh call, graceful-skip when the project isn't configured. Parallel track: the first end-to-end exercise of the documenter sub-agent's /release contract, flipping two feature flags and adding three new wiki pages + an ADR.

Added

• gh project item-create offer wired into every phase. /plan proposes from the plan's ## Out of scope section; /work from out-of-task-scope findings noticed while implementing; /review from deferred-rather-than-blocked findings; /release from cross-session themes. Each phase batches its proposals into a single preview, preview-and-ask on every invocation, graceful-skip when .harness/project.json is absent or gh is unavailable. Canonical blocks in harness/phases/{02-plan,03-work,04-review,05-release}.md with adapter-parity across all four adapters (claude-code, antigravity, codex, gemini — 20 adapter files touched). See the new wiki/design/features/GitHub-Projects-Integration.md for the feature page and ADR 0003 for the ownership-and-linking decision.

Fixed

• ProjectsV2 /setup flow now links the project to the repo. The initial implementation created a user-scoped project that didn't appear under github.com/<owner>/<repo>/projects. ProjectsV2 has no repo-owned form — the fix is a two-step gh project create + gh project link --repo <owner>/<repo> flow at /setup step 8. .harness/project.json schema gains a repo field recording the linkage. Includes the @me-vs-literal-owner gh-CLI quirk as an inline code comment (passing @me to gh project link --owner sometimes fails with "'' has different owner from '@me'" even when they match). Rationale and consequences are in ADR 0003.
• Dropped the "at most 1 per session" cap on Project-item proposals. Early drafts capped at one item; in practice a single /work or /review session can legitimately surface multiple deferred findings, and silent misses are worse than a user seeing a three-item batched preview. Replaced with a quality-bar-plus-batching rule: propose one item per distinct finding, batch into a single preview at phase end, per-phase soft caps as reminders rather than hard limits. Applied uniformly across all 20 canonical + adapter files.

Internal

• First end-to-end exercise of the documenter sub-agent. Invoked per its /release contract (harness/agents/documenter.md §/release) with plan-to-HEAD diff + the current wiki/ tree. Returned the canonical structured report (FILES CREATED / EDITED / OPEN QUESTIONS / NO-OP CATEGORIES). Outputs: new Feature page for GitHub-Projects-Integration (Template 2, Status: implemented), new ADR 0003 (Template 3, Status: accepted), new wiki/development/Completed-Features.md (Template 1 with overview table), Home.md + _Sidebar.md updated for the new pages. All three OPEN QUESTIONS resolved without further docsub edits. Flipped feat-documenter-subagent.passes and feat-gh-projects-integration.passes to true in features.json.
• README refreshed against v0.8.2 drift. Stale "v0.1" Status block replaced with a CHANGELOG pointer; Skills table gained ship-release (which shipped in v0.8.0 but was never cross-linked); /bugfix Phases row expanded with the Issue-posterity lifecycle; documenter sub-agent named in the intro + Install "drops in" list; new bullet for the wiki/ + .github/workflows/wiki-sync.yml pair. Install / Contributing / License untouched.
• ADR 0002 updated with the runtime installer-boundary guard shipped in v0.8.2. Section 4 split into Runtime-guard vs. Test-time-assertions subsections, Consequences bullet rewritten for copy-time enforcement. Matches the ensure_boundary_src / Ensure-BoundarySrc implementation in install.sh / install.ps1.
• Windows boundary-guard test coverage. Added scripts/test-install.ps1 (PowerShell twin of scripts/test-install.sh with all 5 checks a–e). Wired into .github/workflows/tests-windows.yml install-smoke job. Ensures the installer-boundary regression class caught by Defect 2 of #1 is guarded on both OSes.