Skip to content

build(repo): streamline active protocol surface#823

Merged
jithinraj merged 2 commits into
mainfrom
chore/remove-archive-tree
Jun 2, 2026
Merged

build(repo): streamline active protocol surface#823
jithinraj merged 2 commits into
mainfrom
chore/remove-archive-tree

Conversation

@jithinraj

@jithinraj jithinraj commented Jun 2, 2026

Copy link
Copy Markdown
Member

Summary

Streamlines the repository to its active protocol surface by removing the retired pre-0.10 archive/ tree (220 files) from HEAD. Historical content remains recoverable from git history and v0.9.x / archive/* tags. No protocol surface change.

Scope

Repository hygiene only. Explicitly NOT changed: wire format, schemas, signing, public API, CLI behavior, package publication, or normative protocol behavior.

Changes

  • Replace the archive-path-coupled package-surface guard with directory-independent retired-name invariants: retired package names stay out of scripts/publish-manifest.json, the workspace package map, and the resolve-package-path resolver map, and pnpm-workspace.yaml declares no root archive/ glob.
  • De-stale REPO_SURFACE_STATUS.json (drop archived entries that pointed at removed paths) and regenerate docs/PACKAGE_STATUS.md and docs/SURFACE_STATUS.md.
  • Update current operational docs (DEPRECATION_POLICY, MIGRATION_CURRENT, STABILITY-CONTRACT, README_LONG) and add a retired-package-name reference table.
  • Leave historical changelog, release notes, and baselines intact.

Validation

  • pnpm lint, pnpm typecheck:core, pnpm build, and pnpm test (452 files / 11437 tests) pass.
  • scripts/guard.sh, pnpm verify:surface-status, node scripts/verify-spec-drift.mjs, and node scripts/audit-gate.mjs pass.
  • The retired-name guard was verified to fail when a retired name, an archive/ workspace glob, or a retired resolver mapping is reintroduced, then reverted.

Recovery

Removes the retired archive tree from HEAD while preserving recovery through git history, v0.9.x tags, and archive tags. No wire, schema, signing, package publication, public API, CLI, or normative protocol behavior change.

jithinraj added 2 commits June 2, 2026 11:19
Remove the pre-0.10 archive/ tree (220 files) from HEAD. Historical content
remains recoverable from git history and v0.9.x / archive tags.

- Replace the archive-path-coupled package-surface guard with directory-
  independent retired-name invariants: retired package names stay out of the
  publish manifest and the workspace package map, and pnpm-workspace.yaml
  declares no archive/ glob.
- De-stale REPO_SURFACE_STATUS.json (drop archived entries that pointed at
  removed paths) and regenerate docs/PACKAGE_STATUS.md and docs/SURFACE_STATUS.md.
- Update current operational docs (DEPRECATION_POLICY, MIGRATION_CURRENT,
  STABILITY-CONTRACT, README_LONG) and add a retired-package-name reference
  table. Historical changelog, release notes, and baselines are left intact.

No wire, schema, signing, public API, CLI, package publication, or normative
protocol behavior change.
- resolve-package-path.ts: drop the stale `disc -> packages/discovery`
  mapping (the package is retired and the path is gone from HEAD).
- package-surface-audit.test.ts: also guard that retired short names are
  absent from the resolve-package-path map (not only the workspace map), and
  narrow the workspace-glob assertion to the root `archive/` path so it no
  longer over-rejects unrelated names that merely contain the substring
  "archive".
- STABILITY-CONTRACT.md: align the @peac/sdk row with the removed-from-HEAD
  wording and replace the dangling apps/bridge link with plain text.

No wire, schema, signing, public API, CLI, package publication, or normative
protocol behavior change.
@jithinraj jithinraj changed the title build(repo): remove pre-0.10 archive tree from HEAD build(repo): streamline active protocol surface Jun 2, 2026
@jithinraj
jithinraj merged commit 2b7e77a into main Jun 2, 2026
28 checks passed
@jithinraj
jithinraj deleted the chore/remove-archive-tree branch June 2, 2026 06:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant