build(repo): streamline active protocol surface#823
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 andv0.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
scripts/publish-manifest.json, the workspace package map, and theresolve-package-pathresolver map, andpnpm-workspace.yamldeclares no rootarchive/glob.REPO_SURFACE_STATUS.json(drop archived entries that pointed at removed paths) and regeneratedocs/PACKAGE_STATUS.mdanddocs/SURFACE_STATUS.md.DEPRECATION_POLICY,MIGRATION_CURRENT,STABILITY-CONTRACT,README_LONG) and add a retired-package-name reference table.Validation
pnpm lint,pnpm typecheck:core,pnpm build, andpnpm test(452 files / 11437 tests) pass.scripts/guard.sh,pnpm verify:surface-status,node scripts/verify-spec-drift.mjs, andnode scripts/audit-gate.mjspass.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.xtags, and archive tags. No wire, schema, signing, package publication, public API, CLI, or normative protocol behavior change.