@indexnetwork/protocol 14.3.0-rc.475.1 → 14.3.2-rc.477.1

package/CHANGELOG.md

@@ -20,6 +20,74 @@ went 6.7.1 → 8.0.2 with no 7.x in between because the whole 7.x line shipped a
 prereleases between the two promotions. To track every change, read `rc`; to
 pin a supported release, use `latest`.
 
+## 14.3.2 - 2026-08-16
+
+No source change. The public contract in `src/index.ts` is untouched; only
+non-shipped tooling was removed.
+
+### Removed
+
+- `architecture/exports.snapshot.json`, the `architecture:exports` and
+  `check:exports` scripts, and `scripts/architecture/export-inventory.ts`.
+  `check:exports` is gone from `architecture:check` and from the CI lint job.
+
+  The inventory was fully derived from `src/index.ts` as of 14.3.1, so
+  `check:exports` could not catch a genuine defect — only a missed regenerate.
+  Its remaining value was making stable-export removals visible in a PR diff,
+  and that is now a review responsibility: consult [STABILITY.md](./STABILITY.md)
+  when changing the barrel, because nothing mechanical will flag a major bump.
+
+  The snapshot was never published (`files` covers `dist`, `IMPLEMENTATION.md`,
+  `STABILITY.md`, `CHANGELOG.md`), so no consumer is affected.
+
+- `scripts/architecture/module-graph.ts` and its spec. Its only non-test caller
+  was the deleted protocol atlas generator. `capability-model.ts` is unaffected —
+  `capability-boundaries.ts` and the `src/architecture` specs still use it.
+
+## 14.3.1 - 2026-08-16
+
+No source change. Tooling and release record only.
+
+### Added
+
+- `bun run architecture:exports` generates `architecture/exports.snapshot.json`
+  from `src/index.ts`, and `bun run check:exports` reports drift and exits
+  non-zero. `check:exports` is now part of `architecture:check`, which CI runs.
+
+  The inventory is read by `scripts/build-protocol-atlas.ts` as the export
+  inventory, but that only validates the subset in `ROOT_EXPORT_COMPONENTS` —
+  the other ~380 entries were hand-maintained, which is how 300 of them came to
+  point at directories renamed in 14.2.1. The generator derives `name`, `kind`,
+  and `source` from the entry point, so that class of drift cannot recur.
+
+  `stability` is the one field that is not mechanical: `src/index.ts` groups its
+  re-exports under banner comments, and a section carrying a standalone
+  `@experimental` line is experimental until the next banner. Two traps that
+  cost a wrong first implementation each are covered by tests — the file header
+  explains the tiering in prose ("Sections marked `@experimental` below"), which
+  must not match, and the marker scopes to its own section rather than to the
+  rest of the file.
+
+  Anything the inventory cannot describe — a bare `export *`, a locally
+  declared export, a re-export with no module specifier — raises rather than
+  being skipped. Silently dropping one means `check:exports` reports "matches"
+  while the public surface has grown unrecorded, which is the failure the
+  inventory exists to prevent. `export * as ns from` is representable and is
+  recorded as the single name it introduces.
+
+  Drift is compared positionally, not by set membership: the inventory mirrors
+  declaration order, so reordering or duplicating an entry is real drift that a
+  set comparison reports as an empty diff above a "stale" error.
+
+  Verified by reproducing the committed inventory byte-for-byte, all 443
+  entries.
+
+### Fixed
+
+- Backfilled the missing `14.0.0` CHANGELOG section. That release shipped in
+  #1402 and bumped `package.json` without a changelog entry, so the record
+  jumped 13.2.1 → 14.1.0 with a breaking change unrecorded in between.
+
 ## 14.3.0 - 2026-08-16
 
 No public API change: all 443 exported symbols are byte-identical to 14.2.2.
@@ -220,6 +288,24 @@ This is internal structure only.
   touching `QUESTIONER_ENABLED` — so the accessor deliberately does not reuse
   `positiveIntEnv`. Configured by `QUESTIONER_INTENT_DAILY_CAP`.
 
+## 14.0.0 - 2026-08-15
+
+Backfilled. This release shipped in #1402 and bumped `package.json` without a
+CHANGELOG section, so the record jumped 13.2.1 → 14.1.0. Reconstructed from the
+commit (`225425371d`) rather than from memory.
+
+### Removed
+
+- **BREAKING**: retired the pre-personafication `orchestrator` chat persona.
+  `ORCHESTRATOR_PERSONA_ID` and `ORCHESTRATOR_PERSONA` are gone from the package
+  surface, and `ChatGraphFactory` and `ChatAgent.create()` now require a persona
+  — there is no default to fall back on, and unknown values fail closed.
+
+  Production evidence at the time: the orchestrator had written no new session
+  since 2026-08-04, and the presence of `onboarding`-persona rows showed the
+  Signal cutover flag was already on. The 9,464 historical orchestrator
+  conversations remain readable.
+
 ## 13.2.1 - 2026-08-16
 
 No public API change: all 441 exported symbols are byte-identical to 13.2.0, and

package/STABILITY.md

@@ -13,7 +13,9 @@ change. It is the reference behind the tier annotations in `src/index.ts`.
   of the contract and may change or disappear in any release — do not rely on them.
 - The contract is exactly the set of symbols re-exported from `src/index.ts`.
   Exports are listed explicitly (no `export *` wildcards), so the surface is
-  reviewable and additions are always intentional.
+  reviewable and additions are always intentional. Nothing checks this
+  mechanically — a removed or renamed stable export is caught in review of the
+  `src/index.ts` diff, and that is what triggers the major bump below.
 - Root exports are assembled through named capability facades. Those facades are
   implementation seams, not package subpath entry points: consumers must still
   import only from `@indexnetwork/protocol`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@indexnetwork/protocol",
-  "version": "14.3.0-rc.475.1",
+  "version": "14.3.2-rc.477.1",
   "type": "module",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",