Package Publish And Versioning

[flyingrobots]

Migrated from Method backlog

This issue was created from a legacy filesystem backlog card. GitHub Issues are now the live work tracker; repository docs remain Method evidence.

Source backlog: docs/method/backlog/v0.1.0/RELEASE_package-publish-and-versioning.md
Original lane: v0.1.0
Original legend: RELEASE

Original backlog card

Package Publish And Versioning

Status: v0.1.0 release blocker.

Depends on:

• Versioned contract and API compatibility
• JS/WASM/Browser client release surface
• Release-grade quickstart

Why now

Real applications need to know whether a generated contract package, runtime
ABI, WASM ABI, and client helper set fit together. The jedit release gate should
not depend on local path accidents or unversioned generated artifacts.

Required behavior

Echo release artifacts must state compatibility for:

• Echo crate/package version;
• Echo ABI version;
• WASM ABI version, if shipped;
• Wesley generator version range;
• contract package version;
• schema hash;
• artifact hash;
• codec id;
• generated helper compatibility;
• installed package metadata.

Acceptance criteria

• Echo documents release artifact names and publish targets.
• Echo defines compatibility checks for generated contract packages.
• Publish dry-run or equivalent release command is documented.
• jedit can consume Echo through documented versioned artifacts or an
  explicitly documented local-development override.
• The release candidate checklist includes package metadata verification.
• CHANGELOG and release docs name package/API compatibility expectations.

Test plan

• Add package metadata fixture with compatible and incompatible generated
  package versions.
• Add release dry-run check where the repository supports one.
• Add quickstart validation that does not depend on an undocumented local path.

Non-goals

• Do not publish until the release candidate gate is green.
• Do not force all neighboring repos to release in one commit.
• Do not treat local sibling path overrides as release-grade compatibility.

[coderabbitai]

🔗 Related PRs

#326 - Echo contract hosting roadmap [merged]
#329 - Stack Witness 0001 fixture-backed jedit walking skeleton [merged]
#330 - test(wasm): own package export smoke boundary [merged]
#369 - docs: add Echo v0.1.0 release plan [merged]
#380 - feat(core): expose retained evidence posture on readings [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!