Skip to content

Adopt git-cas v6.2 as the sole storage composition root #735

Description

@flyingrobots

Parent: #734

Prerequisite complete: git-stunts/git-cas#60 shipped in @git-stunts/git-cas@6.2.0 and is visible on npm.

Outcome

Applications open one opaque repository-scoped GitStorage handle. Internally, the composition root owns sibling Git-history and git-cas adapters; neither the public API nor the domain layer receives plumbing, concrete adapters, or raw CAS construction capabilities.

Scope

  • Add GitStorage.open({ cwd }) and MemoryStorage.create() as the supported storage constructors.
  • Replace the public Git-shaped StorageAdapter contract with an opaque WarpStorage handle.
  • Compose GitTimelineHistoryAdapter and GitCasRepositoryAdapter as siblings under GitStorage.
  • Open and inject exactly one repository-scoped git-cas facade.
  • Remove dynamic CAS construction and reflected runtime adapter construction.
  • Keep Git history semantics separate from git-cas asset/cache/retention semantics.
  • Remove duplicate lazy CAS initializers and WARP-owned encryption validation already enforced by git-cas.
  • Expose domain capabilities as semantic WARP storage services, not raw object ports.

Proof

Receipt, Tick, and Evidence substrate vocabulary is tracked separately by #743.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:storagePrimary work area: storage.priority:asapImmediate release pressure.status:activeSomeone is actively working this issue.type:featureNew capability or product behavior.

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions