v0.90.0

Scramjet 0.90.0 moves structural-mapping ownership to the Mach 12 development methodology while preserving cross-command-set planning use.

Highlights

• Mach 12 ownership: Rename the canonical mapper from scramjet:structural-mapper to mach12:structural-mapper and package it with Mach 12’s planning specialists.
• Cross-set availability: Keep registered agents callable across command-set boundaries, including ordinary file-level planning outside an active Mach 12 command.
• Coherent optional activation: Dispatch the mapper from ordinary planning only when Mach 12 has registered it, without adding a substitute procedure or runtime discovery machinery.
• Preserved evidence contract: Retain the mapper’s read-only tools, bounded Current-State Structural Evidence Packet, and mapper-first Mach 12 planning handoff.
• Aligned distribution and guidance: Update command wiring, command-set metadata, documentation, installer coverage, and structural contract tests for the new ownership boundary.

Breaking change

• External prompts or custom commands that call scramjet:structural-mapper by name must migrate to mach12:structural-mapper; no compatibility alias is retained.

Known limitations

• Structural mapping outside Mach 12 depends on the Mach 12 command set being installed and its mapper being registered.
• Deterministic tests establish naming, discovery, wiring, and installation behavior; they do not by themselves prove planning usefulness.

Closes #518 by aligning the mapper’s ownership with its planning scope while preserving intentional cross-set use.

Reviewed by GPT-5.6 Sol

v0.89.1

Scramjet 0.89.1 hardens forward-only releases against stale package versions and ambiguous partial publication.

Highlights

• Commit-bound release preflight: Validate the exact merged commit, clean release metadata, all five package manifests, fixed internal dependencies, workspace links, lockfile closure, and registry freshness before mutation.
• Five-fresh publication unit: Require unpublished forward versions for every package and publish each exactly once in dependency order, with bounded read-only propagation checks and no same-tag continuation.
• Independent release proofs: Verify npm attestation metadata, native signatures, isolated postinstall-enabled installation, exact five-package runtime closure, and the installed CLI as separate outcomes.
• Forward-only recovery: Treat partial or ambiguous publication as permanent for that tag, prohibit retries, and direct recovery through another release with five fresh versions.
• Exact merge targeting: Bind release creation to the confirmed merge SHA and preserve separate reporting for GitHub release creation, package publication, provenance, and clean installation.
• Portable release tests: Make Git and polling fixtures deterministic across shallow Linux and macOS CI checkouts.

Known limitations

• Publication is intentionally nontransactional: an external registry or transport failure can leave a partial package set that requires a new forward release.
• Final success depends on npm metadata propagation, provenance, native signature audit, and clean-install verification in the tag workflow; creating the GitHub release does not itself prove those outcomes.

Closes #514 by preventing stale package versions from reaching immutable release tags and enforcing five-fresh, forward-only recovery.

Reviewed by GPT-5.6 Sol

v0.89.0

Scramjet 0.89.0 adds robust, semantically reviewed branch integration before authorized publication.

Highlights

• Dedicated branch integration owner: Add /mach12:integrate-branch for safely integrating a freshly fetched same-repository branch into the current feature branch.
• Semantic review beyond conflict markers: Require inspection of both branch deltas and the combined tree for stale references, incompatible assumptions, and broken cross-file contracts—even when Git reports a clean merge.
• Safe publication boundaries: Validate canonical repository, branch, upstream, commit, and worktree identities; preserve unrelated work; require informed authorization for direct pushes; and verify local, upstream, forge, and PR convergence.
• Pre-Merge delegation: Replace /mach12:pr-pre-merge’s duplicate inline merge implementation with an informed Merge/Cancel gate and delegation to the new integration owner, while preserving separate checklist and CI-fix publication responsibilities.
• Focused command contracts: Expand deterministic coverage for discovery, trust boundaries, clean and conflicted merges, publication authorization, resumed results, verified handoffs, and command inventories.

Known limitations

• Operational effectiveness still needs observation across real already-integrated, clean semantic-correction, genuine-conflict, declined/resumed push, non-default-branch, and delegated Pre-Merge scenarios.
• Static tests pin the model-interpreted direct/delegated lifecycle contract but cannot prove reliable interpretation in every execution.
• Managed installations preserve user-edited seeded commands, so customized installations may retain older local variants.

Closes #513 by adding a reusable, semantically reviewed branch-integration workflow and transferring Pre-Merge integration ownership to it.

Reviewed by GPT-5.6 Sol

v0.88.0

Scramjet 0.88.0 adds proportional, source-grounded structural mapping before non-trivial implementation planning.

Highlights

• Dedicated structural mapper: Add a seventh read-only Scramjet agent that maps task-relevant responsibilities, dependencies, contracts, consumers, public exposure, and evidence limits without designing or mutating.
• Structural evidence before architecture: Require non-trivial Mach 12 issue plans to consume a cited current-state evidence packet before selecting architecture or drafting file-level changes.
• Bounded planning budget: Rebalance the existing eight-call ceiling to seven initial advisory calls plus one optional narrow mapper refresh, without automatic architect redispatch.
• Proportional ordinary planning: Apply the same mapper-first discipline to ordinary file-level plans while allowing clearly mechanical, unambiguous work to skip the extra ceremony.
• Contract-impact discipline: Require architects to assess ownership fit, interface compatibility, known-consumer migrations, and unknown external exposure before claiming a complete blueprint.

Known limitations

• Actual-model evaluation covered representative cross-package, public-interface, ordinary-planning, and mechanical-skip scenarios; these observations do not prove general model behavior.
• A full production-path /mach12:issue-plan trial remains deferred to the next separately authorized planning opportunity.
• Repository searches cannot establish complete external-consumer coverage; plans must preserve and report that evidence boundary.

Closes #511 by adding proportional structural due diligence to implementation planning.

Reviewed by GPT-5.6 Sol

v0.87.0

Scramjet 0.87.0 adds focused command-authoring support built around commands as lightweight generalized plans executed by capable agents.

Highlights

• Six read-only command specialists: Add focused agents for command-set exploration, architecture, instruction semantics, concrete failure analysis, holistic review, and independent finding assessment.
• Shared command-writing guidance: Package the progressively loaded writing-scramjet-commands skill covering outcomes, authority, handoffs, informed user alignment, approval-only coaching exceptions, context economy, and evidence from actual use.
• Deterministic command linting: Add scramjet-command-lint for runtime-derived recognition and collision diagnostics plus structural Goals and context-framing checks. It does not establish semantic quality or operational effectiveness.
• Mach 12 command-work routing: Use Scramjet specialists for command work, retain code specialists for runtime work, partition mixed briefs, and keep mutation, project-tool execution, interaction, and publication with the parent agent.
• Project-native checks and contextual continuation: Teach Mach 12 to discover repository-authorized development tools and recommend next steps from completed-work context rather than fixed array positions.
• Informed alignment: Require consequential user asks to include relevant evidence, alternatives, consequences, uncertainty, and a recommendation without ceremonial confirmation.

Known limitations

• Real-world effectiveness of the final six-agent architecture remains unproven; structural and synthetic checks do not establish product value.
• Project-native tool discovery and transport were not exercised through a final production Mach 12 command path.
• A live command-only planning run showed that the one-architect policy can collapse materially different alternatives too early; that limitation remained unresolved at release.

Closes #474 through the six-agent redesign.

Reviewed by GPT-5.6 Sol

v0.86.0

Scramjet 0.86.0 makes pre-merge version propagation an atomic, repository-guided operation.

Highlights

• Follow repository release authority: Discover applicable contribution and release instructions, including directly referenced material, before fallback investigation.
• Propagate versions completely: Run required synchronization or generation steps before committing canonical versions, mirrors, and tracked generated metadata together.
• Fail safely on ambiguity: Investigate incomplete guidance and ask rather than guessing about package managers, commands, or generated files.
• Verify the command contract: Add focused coverage for authority precedence, propagation ordering, bounded commit scope, consistency checks, and ambiguity handling.

Fixes #508.

Reviewed by GPT-5.6 Sol

v0.85.0

Scramjet 0.85.0 improves PR review fixes by separating requirements clarification from proportional architecture analysis.

Highlights

• Clarify requirements first: Separate required behavior and bounded-scope questions from later implementation architecture decisions.
• Scale architecture analysis proportionally: Dispatch mach12:code-architect only for unresolved non-trivial decision boundaries, while bypassing ceremonial analysis for trivial or settled fixes.
• Preserve parent authority: Keep selected findings, validation-proof constraints, final design selection, and repository mutation under the parent command.
• Pin the command contract: Add focused coverage for decision classification, architect context, authority boundaries, and clarification ordering.

Fixes #506.

Reviewed by GPT-5.6 Sol

v0.84.1

Scramjet 0.84.1 makes trusted-OIDC releases tolerate normal multi-minute npm registry and provenance propagation, enabling corrected forward recovery from the partial v0.84.0 publication.

Recovery release: v0.84.0 remains immutable and will not be rerun. This release preserves fail-closed artifact verification while completing recovery through the normal OIDC path.

Highlights

• Allow npm propagation time: Poll registry visibility, latest tags, and provenance for up to 31 attempts at ten-second intervals without republishing.
• Keep recovery fail-closed: Continue verifying package identity, exact artifacts, provenance, dependency order, and dist-tags before advancing.
• Clarify forward recovery: Document the partial v0.84.0 outcome and require a corrected forward release rather than rerunning its immutable tag.
• Exercise delayed visibility: Add multi-minute registry, tag, provenance, and polling-exhaustion coverage.

Fixes #503.

Reviewed by GPT-5.6 Sol

v0.84.0

Scramjet 0.84.0 replaces stored npm publishing credentials with a tag-driven GitHub Actions OIDC release path and adds explicit release-safety checks.

Publication status: npm package publication for this tag did not complete. A follow-up correction is in progress.

Highlights

• Move toward trusted publishing: Replace NPM_TOKEN-based publication with GitHub Actions OIDC and pin the release toolchain.
• Add fail-closed release checks: Validate event and package identity, preflight registry state, publish in dependency order, and reject ambiguous failures.
• Protect package metadata: Preserve non-latest dist-tags, add canonical repository metadata, and reconcile provenance attestations.
• Document release operations: Add a maintainer runbook covering trusted-publisher setup, verification, and partial-publication recovery.
• Exercise the release contract: Add focused helper and workflow tests for validation, publication ordering, provenance, and recovery behavior.

Fixes #162.

v0.83.1

Scramjet 0.83.1 clarifies that the Agent Skills 1024-character description limit is advisory while preserving complete descriptions in the model-visible prompt.

Highlights

• Clarify long-description warnings: Diagnostics now state that 1024 characters is the Agent Skills specification limit, the warning is advisory, and the full description remains available.
• Protect complete description retention: A filesystem-backed regression test verifies exact loading and generated-prompt content beyond the specification limit.
• Handle Unicode lengths accurately: Warning diagnostics report Unicode character counts rather than UTF-16 code units.
• Document runtime behavior: Skills documentation and the upstream-divergence inventory now record the distinction between specification validation and Scramjet behavior.

Fixes #500.