# git-cas v6.5.6 Release Notes

v6.5.6 moves the interactive cockpit onto Bijou 7.2's hosted application
boundary and makes checked Git ref conflicts independent of diagnostic prose.
It changes no public package API or stored-data schema.

## Bijou 7 Hosted Cockpit

The interactive launcher now runs a `FramedApp`. Bijou owns terminal lifecycle,
outer chrome, help, command and asset-search palettes, settings, notifications,
performance telemetry, quit confirmation, and reference-counted cursor state.
The git-cas page continues to own vault authentication, storage state,
Explorer/Atlas/Operations navigation, filtering, and the Store Wizard.

Store and restore progress use Bijou's shared cursor guard and render the
initial `0/N` state without incrementing the processed count. Frame and page
tests preserve ordinary modal input, page-first key ownership, structured
stdout, and the static noninteractive fallback.

Design Book selected the high-contrast foregrounds for the dark cockpit
surfaces. Bijou's theme doctor and explicit text-tone tests enforce a minimum
4.5:1 contrast ratio.

## Deterministic Checked-Ref Conflicts

Failed checked updates, atomic anchors, and checked deletes no longer inspect
Git's human-readable diagnostics. The Git adapter reads structured post-failure
posture—direct OID, symbolic target, or absence—and normalizes only when that
posture disproves the attempted compare-and-swap precondition.

The existing contracts remain:

- checked updates and deletes reject with `GIT_REF_CONFLICT` plus structured
  expected and observed posture;
- atomic anchors return `false` when their source changed or target appeared;
- operational failures remain the original error when the attempted ref
  precondition still holds.

Diagnostic-free unit and real-Git tests cover changed, absent, and symbolic
posture across all three mutation paths.

## Verification

The release candidate passed the repository's complete 14-step verifier with
6,898 observed tests across Node, Bun, and Deno. The matrix includes public
type compatibility, executable examples, 199 real-Git integration tests on
each runtime, build stamping, and npm and JSR dry-runs.

## Compatibility

This release requires no application or stored-data migration. Existing refs,
objects, handles, cockpit lower modes, machine-readable output, and package
exports remain valid. Interactive operators receive the hosted Bijou shell
automatically; callers receive more reliable existing conflict semantics
without changing method signatures.