ECC/docs/testing/ecc-2.2-release-readiness.tdd.md

ECC 2.2 release-readiness TDD evidence

Date: 2026-08-24

Scope

This pass covers the release blockers found in the delta from v2.1.0: cumulative selective-install ownership, native Antigravity packaging, canonical OpenCode installation and conservative legacy migration, provider-neutral OpenCode agents, skill-comply distribution, conservative legacy Codex uninstall, release-workflow safety, and guided-install filesystem boundaries.

RED

Commit 6e66dfba added release regressions before the repairs. All six focused commands exited nonzero on the origin/main baseline:

• A second selective install retained only the second module in install-state.
• OpenCode resolved to ~/.opencode instead of ~/.config/opencode.
• Managed preflight accepted a plan without an install-state path.
• skill-comply was absent from the npm archive.
• Release workflows lacked registry-error discrimination, an exact-main gate, reviewed notes, and npm-first publication ordering.
• The packed lifecycle did not exercise Antigravity or OpenCode.

Commit 528dbea0 added a security regression proving guided preflight accepted an identical copy source through a symbolic link. It failed before the no-follow snapshot repair.

Commit a504b194 added a release regression after review proved both workflows reused the literal 2.2.0 notes path for later valid versions. Both workflow cases failed before the version-derived notes repair.

Commit 55a2d482 added five OpenCode upgrade regressions. Discovery, uninstall, canonical reinstall, repair migration, and no-follow symlink preservation all failed before the legacy managed-root repair.

Commit 7d9f70c5 changed both workflow contracts to require the repository's established lowercase release-notes.md convention. Both cases failed against the uppercase 2.2-only path before the filename repair.

GREEN

• Focused installer, lifecycle, packaging, release-workflow, manifest, OpenCode, Antigravity, and uninstall tests passed.
• Full repository suite: 3,967 passed, 0 failed.
• npm audit --audit-level=low: 0 vulnerabilities.
• Supply-chain IOC scan: 207 files inspected, no findings.
• Both release workflow YAML files parsed successfully.
• Both release workflows derive reviewed notes from the validated tag and fail clearly when that version's notes are absent.
• Release-note selection follows the lowercase filename convention shared by prior release directories.
• Exact packed archive lifecycle passed on macOS with Node 24.9.0 using SHA-256 77e8867a50147f3ca23dabaf4a75f936c139aef27788d2b167c1702a4c81fdd4.
• The packed lifecycle covered npm installation, public CLI setup, cumulative Cursor install, drift detection, repair, uninstall, user-file preservation, Antigravity install/doctor/uninstall, and OpenCode install/doctor/uninstall.

Focused coverage

All three changed core modules exceeded the 80 percent line target:

Module	Lines	Functions	Branches
scripts/lib/multi-harness-setup.js	88.75%	82.75%	74.01%
scripts/lib/install/claude-skill-migration.js	95.20%	100%	88.78%
scripts/lib/install-targets/opencode-home.js	86.66%	100%	78.94%
scripts/lib/install/opencode-legacy-migration.js	82.24%	100%	68.29%

Coverage commands used c8 --check-coverage --lines 80 against the corresponding focused test files.

Release boundary

No merge, release tag, GitHub Release, or npm publication was performed during this pass.