Cache and Release Classification Grill Status

Branch Dashboard

Current Round

• Round: closed
• Current frontier: empty
• Shared-understanding confirmation: confirmed by the user on 2026-08-10

Locked Direction

• The release-impact classifier distinguishes none, baseline, npm, and mixed from semantic artifact comparison, not path filters alone.
• A baseline build inside npm package assembly is separate from publishing or promoting stable baseline authority.
• Every merge to main runs the classifier; only required release mutations execute.
• Production stable is the only release channel in scope.
• Same-repository PR CI and authenticated local development both read and write signed development-cache entries. Protected release authority remains separate.
• Verification and build work is cacheable by default. Portable tasks may cross local macOS and Ubuntu PR CI; host-dependent tasks use capability-keyed entries.
• Only the smallest tasks whose asserted behavior is current scheduling, timing, external lifecycle, or mutation remain fresh, with the reason declared.
• The rejected bilateral cross-platform acceptance suite is not required.
• The project remains on GitHub Free and does not require enforceable branch protection.
• Pull-request candidate checks cannot block a Free-plan merge, but exact successful candidate evidence is mandatory for publication.
• Direct, red, cancelled, or unattested main commits perform no production release mutation.
• Local verification uses a fast cache-backed staged-diff pre-commit gate and a complete cache-backed pre-push candidate gate.
• A failed same-minor consumer proof turns npm-only intent into mixed release intent.
• Mixed releases build and publish the baseline before npm; no candidate/promotion split is introduced.
• npm latest and next both identify production stable.
• Every explicitly reviewed product version publishes in order; pending versions do not coalesce.
• The next-minor baseline-first compatibility interval is accepted.
• Failed versions remain first in the release queue; retries reconcile completed steps before later versions run.

Still Open

• None. Requirements are ready for specification compilation.

Parked Branches

• Beta release channel. Owner: Stefan. Resume trigger: an explicit request to introduce a beta channel.
• Canary release channel. Owner: Stefan. Resume trigger: an explicit request to introduce a canary channel.
• npm staged publication with human approval. Owner: Stefan. Resume trigger: an explicit request to add staged publication or a human approval gate.

Specification Handoff

• Base: origin/main@caee8be43d38bfaaaff4cc3c90cb14c8b82c245a.
• Stack: none; use one feature/spec branch into main.
• Retained research authority: research/cache-release-diff-classification@7e196b2223d39e8767fb76356f7c56fb0630d966 and research/cache-release-green-main-gaps@eabdd5f7206f0aeeb3a3aaba4ff31de5dc30d1f8.
• Vercel dependency: Devpunks scope dev-punks, project harness-intelligence-api, project ID prj_Us1K3pmpyCJiAGLQfiPpAoOBhHGt, organization ID team_0QvyOroTH1I7k8hWMqSRCOqH.
• Prototype verdict: not applicable.

Glossary

Terms

• Release-impact classifier: Readonly authority that selects none, baseline, npm, or mixed from canonical product comparisons.
• Stable baseline: The immutable scaffold artifact currently promoted by the control plane as the production baseline.
• Portable deterministic test: A test task whose result is proven independent of operating system and architecture under its complete declared identity.
• Capability-keyed test: Host-dependent verification cached only when declared runtime, kernel, filesystem, tool, container, and other relevant capability evidence matches.
• Fresh witness: The smallest uncached test whose purpose is to observe current scheduling, timing, contention, external lifecycle, or mutation rather than deterministic output.
• Release intent: Reviewed repository state that declares the version, changelog, compatibility, and product release expected after merge.
• Release authority: Credentials and trust policy permitted to mutate npm, GitHub release, or stable baseline state.
• Compatible patch family: A baseline CLI range from one supported version up to, but excluding, the next minor version. Avoid: binary compatible family, unbounded minimum version.
• Portable cache writer: An authority allowed to upload a result under the platform-neutral development-cache identity.

Relationships

• One main commit has exactly one release-impact classification.
• One classification may require zero, one, or both product publications.
• An npm publication always assembles a bundled baseline but does not always promote a stable baseline.

Axioms

• Release mutations are never cacheable.
• Pull requests never publish production artifacts.
• Protected publication never consumes development-cache artifacts.
• A main merge always triggers classification; classification decides whether publication occurs.
• Classification may select an impact, but publication still requires exact successful pull-request candidate evidence for the current tree.
• Unknown release impact fails closed.
• A stable baseline never declares compatibility beyond its current minor family.
• npm latest and next resolve to the same production version.
• Authenticated local development and same-repository PR CI may both write portable cache entries.
• Test and build tasks are cacheable by default; an uncached task must state why replay cannot establish the asserted property.

Flagged Ambiguities

• "Publish after every merge" means the release workflow always runs, not that every merge creates a new product version.
• ">= currentVersion" is resolved as a bounded compatible patch family: >=current <next-minor.
• "Binary compatible" is avoided because compatibility covers behavior, schemas, and consumer evidence rather than a native ABI.
• "Cache everything" means cache every replay-safe result. It does not turn a prior concurrency schedule or external mutation into evidence that the current execution occurred.
• "Required PR gate" means required for production publication. GitHub Free cannot enforce it as a private-repository merge restriction.