Preview This is the v1.0 preview line. It documents a rebuild that is still in alpha — schemas, tool names, and package contents change without notice, and nothing here is covered by a stability guarantee. For the released line, see the v0.x documentation.

v0 Reconciliation

Controlled carry-over from the supported v0 line into v1.

Alpha.4 documentation review: This page records design or historical planning. For shipped behavior and current gaps, use the issue #135 implementation review .

Baseline

The v1 line forked from v0.27.1. Reconciliation therefore compares the current v1 work against the latest supported v0 release, currently v0.28.3, rather than copying the v0 tree wholesale.

The rule is:

  • carry fixes that remain valid under the v1 ontology
  • adapt lifecycle and storage behavior to generated v1 contracts
  • regenerate catalogs, schemas, and manifests from v1 sources
  • defer unrelated v0 features with an explicit disposition
  • never overwrite v1 schema sources with flat v0 schemas

Current Matrix

v0 surfacev1 dispositionAlpha status
Refreshable GitHub token-file authenticationCarry unchanged security semanticsImplemented and tested
Migration draftingAdapt to v1 Migration schema and automatic apply modeImplemented and tested
Historical migration filename repairCarry with append-only audit bridgeImplemented and tested
Scope lifecycleAdapt storage to Container(kind=scope)Implemented and tested
TeamMember role assignmentAdapt through the Actor interfaceImplemented and tested
Immutable release-manifest preflightCarry --check; builds must not mutate tagsImplemented
git-branching skillCarry after v1 metadata reviewDeferred after alpha
project-reconciliation skillCarry after v1 entity-name reviewDeferred after alpha
repository-portfolio-review skillCarry after v1 entity-name reviewDeferred after alpha
v0 doctor fixesRe-evaluate per finding against v1 storageOngoing
v0 flat schemas and generated catalogsNever copy; regenerate from v1 sourcesEnforced

Verification

The server smoke suite exercises the v1-native replacements. The package smoke suite then extracts only the release tree and repeats the workflow so repository imports cannot conceal a missing carry-over.

Before each prerelease:

  1. compare the selected v0 release with v1.x-dev
  2. update this matrix
  3. run schema, server, package, docs, doctor, and release-audit checks
  4. record any intentional deferral with an owner or milestone