id: "GW20-026"
title: "Remove duplicate schema-library majors from the install graph"
type: "feature"
status: "planned"
milestone: "v20.1.0"
category: "required"
workstream: "tooling"
issue: "#982"
baseline_commit: "ceb58e656ec5bc85f0ae5991bf2a55599693bbb3"
feedback_sections: [18]
prerequisites: []

Feature

LLM prompt

Complete GW20-026: Remove duplicate schema-library majors from the install graph.
Read this entire task and its current GitHub issue before implementation.
Verify the current mainline and all prerequisite integrations.
Read AGENTS.md and the three TypeScript policy documents.
Use runtime-backed domain values and injected ports.
Keep parsing and codecs at the adapter boundary.
Preserve v20 APIs, stored identities, CRDT semantics, and failure meanings.
Use one coherent issue, PR, and mainline integration. Do not leave a broken intermediate state.
Problem to resolve:
The report records three zod copies. git-warp uses zod 3, while trailer-codec and vault bring zod 4.
Acceptance checks:
Record a clean library-only install inventory and identify each zod owner.
Align compatible released schema dependencies so the supported install has one zod major and no unnecessary duplicate copies.
Do not use an override that violates an upstream package contract.
Runtime validation, trailer codecs, vault consumers, and packed declarations pass after the dependency change.
Record before/after installed bytes and resolved package versions from the same clean Docker fixture.
External gate: compatible published schema dependencies from git-cas, trailer-codec, and vault. git-cas 6.5.11 itself uses zod 3.
Record exact ready package versions before activation. Do not invent a minimum upstream version or narrow the target to direct dependencies only.
Read these source paths:
package.json
package-lock.json
src/infrastructure/adapters/TrailerCommitMessageCodecAdapter.ts
Prerequisites: None established. Recheck external readiness.
Scope exclusions: Rewrite upstream source in node_modules or use a mismatched forced override.
Run all tests and benchmarks in COPY-based Docker without host repository mounts.
Use the project guarded runner and the shared git-locks authority.
Lock host/heavy-work and the exact worker key together for expensive work.
Limit build caches to 20 GiB, test data to 4 GiB, and logs to 128 MiB.
Require 50 GiB free on host and Docker backing storage before heavy work.
Enforce disk accounting, CPU, memory, timeout, and child-process shutdown.
Do not start an unguarded workload. Do not bypass a resource refusal.
Require full touched-code coverage for refactors and an all-green manual SSJS scorecard.
Record source, image, command, fixtures, results, limits, and the regression witness.
Commit only your own files. Do not amend, rebase, force, push, or publish without authorization.
Report incomplete or blocked checks. Do not claim completion from a narrow green test.
Link the issue, coherent PR, and actual mainline integration when those actions are authorized.

1. Background Context

Source: FEEDBACK-git-warp.md, sections 18.
The report SHA-256 is 9b15209d51cd705059a9e6bfebf0f6681ff832924c1462b99ff3cfebde6bacae.
The report uses npm git-warp 20.0.0 and git-cas 6.5.11.
Its runtime results come from macOS host experiments. This planning task did not rerun them.
Source review baseline: ceb58e65.

Tracker: #982.

Read these source and test surfaces before work:

• package.json
• package-lock.json
• src/infrastructure/adapters/TrailerCommitMessageCodecAdapter.ts

2. Problem Description

The report records three zod copies. git-warp uses zod 3, while trailer-codec and vault bring zod 4.

2b. Proposed Solution

Consume compatible published dependency updates. If upstream work is required, record its release gate and preserve the installed contract.

2c. Alternatives considered and rejected

Reject a private-import workaround. It does not provide a supported application contract.
Reject a documentation-only substitute when this task requires runtime behavior.
Keep larger storage and package redesigns under their existing issues.

2d. Acceptance Criteria

• Record a clean library-only install inventory and identify each zod owner.
• Align compatible released schema dependencies so the supported install has one zod major and no unnecessary duplicate copies.
• Do not use an override that violates an upstream package contract.
• Runtime validation, trailer codecs, vault consumers, and packed declarations pass after the dependency change.
• Record before/after installed bytes and resolved package versions from the same clean Docker fixture.
• External gate: compatible published schema dependencies from git-cas, trailer-codec, and vault. git-cas 6.5.11 itself uses zod 3.
• Record exact ready package versions before activation. Do not invent a minimum upstream version or narrow the target to direct dependencies only.

2e. Test Plan

Golden: Install the packed library into an empty Docker consumer. Record npm ls zod and installed bytes. Execute schema and codec compatibility witnesses.

Edges: npm lock replay; JSR consumption; optional CLI dependencies; incompatible upstream majors.

Known failure modes: preserve typed refusal, atomic publication, and complete evidence. Do not conceal unavailable support.

Fuzz and stress: use fixed fixture sizes and seeds. Apply the roadmap resource guards. Do not start an unbounded campaign.

3. Prerequisites

External gate: compatible published schema dependencies from git-cas, trailer-codec, and vault. Record exact package versions and install proof.

None established as an internal issue dependency. Verify the current boundary and external readiness before activation.

4. Scope

In: The report records three zod copies. git-warp uses zod 3, while trailer-codec and vault bring zod 4.

Out: Rewrite upstream source in node_modules or use a mismatched forced override.

Safe intermediate state: one independently mergeable PR passes its relevant checks after its prerequisites.
Existing supported applications remain usable. Historical data remains intact.

5. Why now

This flaw blocks a supported Synapse store workflow or gives its operator incorrect guidance.
Resolve it within v20.1.0 without reducing the existing causal-history commitment.

6. Risks

Source inspection does not establish runtime or performance results.
Preserve historical identities, validation, and evidence. Do not weaken refusal to obtain a green result.
If the fix requires a breaking contract, record the conflict before activation. Do not hide it within a minor release.

7. Definition of Done

All acceptance checks have evidence from the exact candidate.
Relevant lint, typecheck, compatibility, and Docker checks pass.
The manual SSJS scorecard is green. Refactor coverage reaches 100% on touched code.
Record the issue, PR, and mainline integration commit. Record any external release gate.
A required check with missing evidence remains incomplete.

8. Stakeholders

James Ross: git-warp maintainer and acceptance owner.
Synapse store authors: applications need correct writes, reads, history, and operational guidance.
Library and CLI consumers: existing v20 contracts must remain usable.

9. Related Issues

• #519