chore(specs): gardener checkbox sync#870
Conversation
Deploying mcpproxy-docs with
|
| Latest commit: |
6e2030a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://bef6578f.mcpproxy-docs.pages.dev |
| Branch Preview URL: | https://claude-spec-gardener.mcpproxy-docs.pages.dev |
|
The failing This looks like a version-skew regression introduced by #863 ( Generated by Claude Code |
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
📦 Build ArtifactsWorkflow Run: View Run Available Artifacts
How to DownloadOption 1: GitHub Web UI (easiest)
Option 2: GitHub CLI gh run download 29719229804 --repo smart-mcp-proxy/mcpproxy-go
|
Spec-gardener run: 2026-07-20. Applied 15 checkbox ticks, proposing 1 un-tick candidate (NOT applied), across 34 specs with tick/un-tick candidates surfaced by
scripts/check-spec-evidence.py.Applied ticks
All 15 were independently re-verified by the gardener session (reading the cited files directly) in addition to the sub-agent that originally proposed each.
Proposed un-ticks (NOT applied)
All other 85 UNRESOLVED/REMOVED/RELOCATED findings from the checker were investigated and found to be RELOCATED-NOT-ABSENT — the cited evidence path was stale (file renamed/consolidated/moved), but the actual behavior exists elsewhere in the current codebase (e.g.
internal/contracts/config.go→ consolidated intointernal/contracts/types.go;cmd/mcpproxy/teams_register.go→ renamed toserveredition_register.goas part of a deliberate Teams→Server-Edition rename). These are correctly left ticked and are not proposed as un-ticks.Dropped by verification
130
possibly_builtcandidates (unchecked tasks where every cited file happens to exist) were investigated and dropped — the file existed but the specific promised behavior was absent, differently implemented without meeting the task's bar, an unwired component, a stub, or an untested claim. Grouped by spec:001-code-execution— 12 dropped001-oas-endpoint-documentation— 6 dropped001-update-version-display— 6 dropped003-tool-annotations-webui— 3 dropped004-management-health-refactor— 9 dropped006-oauth-extra-params— 8 dropped007-oauth-e2e-testing— 5 dropped008-oauth-token-refresh— 6 dropped009-proactive-oauth-refresh— 19 dropped010-release-notes-generator— 1 dropped011-resource-auto-detect— 1 dropped014-cli-output-formatting— 1 dropped016-activity-log-backend— 1 dropped017-activity-cli-commands— 9 dropped019-activity-webui— 1 dropped021-request-id-logging— 1 dropped026-pii-detection— 3 dropped028-agent-tokens— 1 dropped029-mcpproxy-teams— 1 dropped040-server-ux— 4 dropped042-telemetry-tier2— 12 dropped044-diagnostics-taxonomy— 10 dropped044-retention-telemetry-v3— 3 dropped056-output-schema-validation— 1 dropped057-in-proxy-profiles— 1 dropped073-activity-size-retention— 1 dropped076-deterministic-tool-scanner— 1 dropped077-scanner-simplification— 2 dropped083-discovery-profiler— 1 droppedMethodology note
Given the volume (147
possibly_builtcandidates + 88 UNRESOLVED/REMOVED/RELOCATED findings across 34 specs), verification was fanned out across 8 parallel research sub-agents (one per group of specs), each applying the tick test from this repo's spec-gardener instructions: state the promised behavior, cite file:line, confirm it's real (not a stub/comment/unwired component/skipped test), and default to not-ticking when uncertain. The gardener session then independently re-verified every candidate the sub-agents recommended ticking by reading the cited source directly before applying any checkbox change, and dropped two of a sub-agent's proposed ticks where the task named a specific artifact (a named computed property) that did not actually exist in the code even though the surrounding behavior worked via a different mechanism (009-proactive-oauth-refresh T054, T060 — dropped despite sibling tasks T055/T056/T061/T063 for the same feature area being ticked, since those name outcomes rather than specific artifacts).ROADMAP.mdwas regenerated viascripts/gen-roadmap.pyin a separate commit after the checkbox sync, per the pre-commit hook's staleness check.