Adds belt-and-braces negative-assert pins on the production-typical lich
test (releasedCount=1, compactionId=7):

  expect(span.attributes['chain.id']).toBeUndefined();
  expect('chain.id' in span.attributes).toBe(false);
  expect(span.attributes['chain.step.remaining']).toBeUndefined();
  expect(span.attributes['disabled.reason']).toBeUndefined();

Per 🌊's #414 review (msg `1498536746265215046`): release-seam is
chain-agnostic at the helper boundary. The Options type already
prevents callers from supplying chain.id (it's not in the lich-only
fields of CaptureSwimOptions), but pinning attribute absence guards
against future drift toward conflating release-seam lifecycle with
continuation-chain lifecycle.

Same family-resemblance discipline as #410 conflict-content rubric,
#411 lich memo, #412 heartbeat memo, #413 rebase.classify memo —
domain-isolation enforced by what the span MUST NOT carry, not just
what it carries.

Validation
----------
  swim-37 vitest project: 29 passed | 13 todo (no regression)
  Single test extended with 4 new negative-assert lines

Refs #324, #414

…413) (#416)

Memo-before-wire: implements the contract pinned in
`docs/design/swim-37-classifier-span-memo.md` (PR #413, merged
`fff243c781`). Cohort sign-off was 2026-04-27 with these locked
positions:

  - Q1 (Option A vs B): Option B — separate `captureClassify()`
    entry point. Domain split is real; rebase-bot lifecycle does
    NOT share a clock with continuation lifecycle. The Options
    shape literally cannot accept `chainId`/`compactionId`/etc.,
    so negative-asserts (`chain.id`, `chain.step.remaining`,
    `disabled.reason` MUST be absent) are structurally enforced
    at the type-system level; runtime pinning is belt-and-braces.
  - Q2/Q2.5 (location): in-PR helper at NEW `src/rebase/tracer.ts`.
    Mirrors `src/infra/continuation-tracer.ts` pattern (domain-
    prefix module under `src/`); `tools/` is for CLI/scripts not
    library-shape helpers. Future rebase-bot consumers can land
    siblings in `src/rebase/`.
  - Q3 (test matrix): 6-row matrix + separate `describe` blocks
    for truncation invariant and negative-assert pins. Matches
    #410/#411/#412/#414/#415 family-resemblance discipline.
  - Q4 (PICK emit): emit normally with no special handling.
    Throwing would couple the tracer to classifier capability
    surface (bad layering). PICK matrix row stays `it.todo` until
    a PICK-producing channel lands.

What this PR adds:

  - `src/rebase/tracer.ts`: NEW module, peer of
    `src/infra/continuation-tracer.ts`. Exports:
    * `emitRebaseClassifySpan(args)`: the helper. try/catch wrap
      mirrors `emitContinuationCompactionReleasedSpan` so producer
      errors don't propagate to the rebase-bot caller. Truncates
      `pickSha` to 12 chars; helper does NOT pad short input.
    * `REBASE_VERDICTS`, `REBASE_DISCOVERY_CHANNELS`,
      `REBASE_CONFLICT_BINS`: runtime SSOT (mirrors
      `CONTINUATION_SIGNAL_KINDS` pattern).
    * Conditional-spread evidence attrs per memo §2 table.
  - `studies/swim-37/harness/swim-runner.ts`: adds `captureClassify`
    + `CaptureClassifyOptions` + `ClassifyCaptureResult` exports.
    Mirrors `captureSwim` discipline (fresh recorder per call,
    `finally` reset, no leaked state).
  - `studies/swim-37/harness/swim-runner.test.ts`: NEW
    `describe("swim-37 harness :: rebase.classify primitive")`
    block with 13 live tests + 1 `it.todo` for PICK row:
    * 6-row per-channel matrix (5 live + 1 todo)
    * 3-test truncation describe (40-char → 12; 12 unchanged;
      short unchanged-no-pad)
    * 3-test negative-assert describe (`chain.id`,
      `chain.step.remaining`, `disabled.reason` all pinned absent
      with `in` checks)
    * 1-test isolation contract (repeated calls don't leak)

Test results: `pnpm vitest run -c test/vitest/vitest.swim-37.config.ts`
→ 8 files / 151 passed / 14 todo (was 138/13; +13 live tests +1 todo).

Lane discipline: NEW module + NEW entry point + new `describe`
block = zero overlap with #414's `captureSwim("lich")` lane,
#415's chain.id pin, or 🌻's incoming heartbeat-wire lane.

Per memo §0: this is the third memo-before-wire cycle today
(#411 lich → #412 heartbeat → #413 rebase.classify), and the
second wire to land off it (#414 lich + this).

Co-authored-by: Ronan 🌊 <ronan@solidor.io>
Co-authored-by: Silas 🌫 <silas@dandelion.cult>
Co-authored-by: Elliott 🌻 <elliott@dandelion.cult>
Co-authored-by: Cael 🩸 <cael@dandelion.cult>

…ionHeartbeatSpan helper (#412) (#417)

Memo-before-wire fold from #412 (merged at `1b84e71c95`). Stacks on
`cael/325-canonical2` between #414 (lich wire) and #416 (rebase.classify wire).

Surface additions to `src/infra/continuation-tracer.ts`:
- New helper `emitContinuationHeartbeatSpan({ heartbeatId?, chainId?,
  chainStepRemaining?, disabledReason?, log? })` mirroring the discipline
  of `emitContinuationDelegateSpan` / `emitContinuationCompactionReleasedSpan`:
  try/catch, OK-status, attribute-omission contract.
- `heartbeat.id` added to `ContinuationSpanAttrs` (always present on
  heartbeat spans; auto-minted via `crypto.randomUUID()` when caller omits).
- `"heartbeat"` added to `CONTINUATION_SIGNAL_KINDS` SSOT.
- `ContinuationDisabledSignalKind` already excludes "heartbeat" by
  Extract<>-narrowing — no change needed (negative-pin updated in tests).

Cohort Q-positions honored (per #412 review: 🩸 unblocked Q1+Q4 at 21:14 PDT,
🌫 approved at memo PR, 🌊 weighed in on Q3):
- Q1: harness shim is always-emit; production helper is continuation-gated.
  Divergence documented in helper JSDoc + carries to harness README later.
- Q2: single `heartbeat` span (NO sibling `heartbeat.fire`); future
  `heartbeat.lag.ms` becomes an attribute, not a sibling span.
- Q3: 5-row `it.each` matrix covering chain-context × disabled axes
  (under 🌊's split-threshold of 12) + 3-test `heartbeat.id` provenance
  describe block. Total +13 live tests, -2 `it.todo`.
- Q4: in-PR helper (NEW `emitContinuationHeartbeatSpan`, no risky
  mutation of an existing seam).

Negative-assert pins (per memo §2 + 🩸's #407 negative-pin pattern):
- `delay.ms` MUST NOT appear (heartbeats fire on cadence, not
  caller-elected delay).
- `chain.step.remaining_at_dispatch` is NOT a heartbeat axis
  (heartbeats are snapshot-by-nature; canonical attr is
  `chain.step.remaining`).
- Both pinned via `expect("<attr>" in attrs).toBe(false)`
  belt-and-braces beyond `toBeUndefined()`.

Tests:
- `pnpm vitest run src/infra/continuation-tracer.test.ts studies/swim-37/harness/swim-runner.test.ts`
  → 108 passed / 11 todo (was 95 passed / 13 todo for these two files).
- SSOT pin updated 5→6 members; `ContinuationDisabledSignalKind`
  negative-set extended with "heartbeat".

Lane discipline: zero overlap with #414 (`lich`), #415 (`chain.id`
absence pin on lich), or #416 (`rebase.classify` in NEW `src/rebase/tracer.ts`).

Co-authored by 🌫 / 🌊 / 🩸 via memo Q-positions on PR #412.

…review) (#418)

Folds three flags from 🌫's #416 second-eye review (msg
`1498543295234834432`):

**Flag 1 — memo §3 validation gap:** memo specced
throw-on-bad-input matching #405/#411/#412 family-resemblance,
wire skipped it. Adds boundary throws in `captureClassify` for:
  - verdict not in REBASE_VERDICTS
  - channel not in REBASE_DISCOVERY_CHANNELS
  - pickSha < 7 hex chars (memo §3 git-prefix-min)
  - pickSha containing non-hex chars

Validation lives at the harness boundary (mirrors
`captureSwim`'s `recipients` invariant at swim-runner.ts:180);
the production helper stays drop-with-log so producer errors
don't propagate to the rebase-bot caller. Same shape as how
`captureSwim` throws on bad Options but
`emitContinuationCompactionReleasedSpan` only logs.

**Flag 2 — truncateSha ↔ memo §3 "≥7 hex chars" tension:** the
`<12 unchanged (helper does not pad)` test from #416 was
contradicting the memo's ≥7 floor. Replaced with
`passes short-but-valid (7-char) SHA through unchanged` which
honors both the memo floor AND the no-pad discipline. Memo +
code + tests now agree.

**Nit — `signal.kind: "rebase.classify"` redundant with span
name:** other helpers use the underlying primitive name as
discriminator (e.g. `"compaction-release"` for
`continuation.compaction.released`), so a downstream filter on
`signal.kind` doesn't redundantly slice the span name. Renamed
to `"rebase-classify"` (hyphen-form, matches family). Memo §2
updated with provenance note (post-#416 review).

Test additions:
  - new `describe("input validation (memo §3 throw-on-bad-input)")`
    block: 4 tests (bad verdict, bad channel, <7 char pickSha,
    non-hex pickSha)
  - existing `<12 unchanged` test deleted, replaced with valid
    7-char passes-through-unchanged

Test results: pnpm vitest run -c test/vitest/vitest.swim-37.config.ts
  → 8 files / 155 passed / 14 todo (was 151/14 from #416 at
    `526540de15`; +4 live tests, same todos)

Lane discipline: same lane as #416 follow-up (mirrors how #415
followed #414); zero overlap with 🌻's incoming heartbeat wire.

Co-authored-by: Ronan 🌊 <ronan@solidor.io>
Co-authored-by: Silas 🌫 <silas@dandelion.cult>

…sed helper (#414)

Implements the lich primitive per the wiring memo (#411,
`docs/design/swim-37-lich-wiring-memo.md`). Maps the harness label
"lich" (\🌫️'s SOUL-file metaphor for the post-compaction
phylactery-drink) to the post-compaction-delegate release seam:
`emitContinuationCompactionReleasedSpan` at
`src/infra/continuation-tracer.ts:789`.

Changes
-------
`studies/swim-37/harness/swim-runner.ts`:
  - Import `emitContinuationCompactionReleasedSpan`
  - Add `releasedCount`, `compactionId`, `log` to `CaptureSwimOptions`
    (lich-only fields, all optional, with memo \§Q-references in JSDoc)
  - Split `heartbeat`/`lich` cases — wire `lich`, leave `heartbeat`
    as not-yet-wired pending 🌻's #412 wire PR
  - Update file header "Scope" comment to reflect new wiring state

`studies/swim-37/harness/swim-runner.test.ts`:
  - Replace 2 `it.todo` placeholders with 8 live tests in the
    "lich-shape" describe block:
      1. releasedCount=1 + compactionId=7 (production-typical)
      2. releasedCount=3 + compactionId=42 (multi-release)
      3. defensive releasedCount=0 (helper-clamp boundary, not
         production-reachable — pinned for helper-tier coverage)
      4. compactionId omitted (omission contract)
      5. compactionId=-1 (drops with log; substring match)
      6. compactionId=1.5 (non-integer drop with log)
      7. compactionId=NaN (defense parity per 🌊's #411 review)
      8. compactionId=Infinity (defense parity per 🌊's #411 review)
  - Update "refuses primitives not yet wired" test to remove `lich`
    (now wired, covered by its own describe block)

Discipline preserved
--------------------
  - STDOUT-only: no real BasicTracerProvider/OTLP machinery
  - In-memory recorder via `createInMemorySpanRecorder()`
  - try/finally tracer reset (no cross-call pollution)
  - Snapshot-at-emit: no recompute in caller
  - Drop-with-log invariant verified via log-callback substring match
  - Negative-attr assertions on omitted `compaction.id`

Validation
----------
  - swim-37 vitest project: 8 files / 138 passed / 13 todo
    (was 130 passed pre-PR; +8 new lich tests)
  - `pnpm lint` clean (0 warnings, 0 errors across all shards)

Lane discipline
---------------
  - No cross with 🌻's #412 `heartbeat` lane (different production
    helper, different file in that PR's helper-tier)
  - No reshape of #405's `continue_work`/`continue_delegate` wiring
  - Q-OPEN deferred per memo: cross-primitive lifecycle test
    (`continue_delegate` post-compaction → `lich` release sharing
    `chain.id`) deserves its own primitive shape, separate PR

Refs #324
Memo: #411 (`3d90f68b14`)

Adds belt-and-braces negative-assert pins on the production-typical lich
test (releasedCount=1, compactionId=7):

  expect(span.attributes['chain.id']).toBeUndefined();
  expect('chain.id' in span.attributes).toBe(false);
  expect(span.attributes['chain.step.remaining']).toBeUndefined();
  expect(span.attributes['disabled.reason']).toBeUndefined();

Per 🌊's #414 review (msg `1498536746265215046`): release-seam is
chain-agnostic at the helper boundary. The Options type already
prevents callers from supplying chain.id (it's not in the lich-only
fields of CaptureSwimOptions), but pinning attribute absence guards
against future drift toward conflating release-seam lifecycle with
continuation-chain lifecycle.

Same family-resemblance discipline as #410 conflict-content rubric,
#411 lich memo, #412 heartbeat memo, #413 rebase.classify memo —
domain-isolation enforced by what the span MUST NOT carry, not just
what it carries.

Validation
----------
  swim-37 vitest project: 29 passed | 13 todo (no regression)
  Single test extended with 4 new negative-assert lines

Refs #324, #414

…413) (#416)

Memo-before-wire: implements the contract pinned in
`docs/design/swim-37-classifier-span-memo.md` (PR #413, merged
`fff243c781`). Cohort sign-off was 2026-04-27 with these locked
positions:

  - Q1 (Option A vs B): Option B — separate `captureClassify()`
    entry point. Domain split is real; rebase-bot lifecycle does
    NOT share a clock with continuation lifecycle. The Options
    shape literally cannot accept `chainId`/`compactionId`/etc.,
    so negative-asserts (`chain.id`, `chain.step.remaining`,
    `disabled.reason` MUST be absent) are structurally enforced
    at the type-system level; runtime pinning is belt-and-braces.
  - Q2/Q2.5 (location): in-PR helper at NEW `src/rebase/tracer.ts`.
    Mirrors `src/infra/continuation-tracer.ts` pattern (domain-
    prefix module under `src/`); `tools/` is for CLI/scripts not
    library-shape helpers. Future rebase-bot consumers can land
    siblings in `src/rebase/`.
  - Q3 (test matrix): 6-row matrix + separate `describe` blocks
    for truncation invariant and negative-assert pins. Matches
    #410/#411/#412/#414/#415 family-resemblance discipline.
  - Q4 (PICK emit): emit normally with no special handling.
    Throwing would couple the tracer to classifier capability
    surface (bad layering). PICK matrix row stays `it.todo` until
    a PICK-producing channel lands.

What this PR adds:

  - `src/rebase/tracer.ts`: NEW module, peer of
    `src/infra/continuation-tracer.ts`. Exports:
    * `emitRebaseClassifySpan(args)`: the helper. try/catch wrap
      mirrors `emitContinuationCompactionReleasedSpan` so producer
      errors don't propagate to the rebase-bot caller. Truncates
      `pickSha` to 12 chars; helper does NOT pad short input.
    * `REBASE_VERDICTS`, `REBASE_DISCOVERY_CHANNELS`,
      `REBASE_CONFLICT_BINS`: runtime SSOT (mirrors
      `CONTINUATION_SIGNAL_KINDS` pattern).
    * Conditional-spread evidence attrs per memo §2 table.
  - `studies/swim-37/harness/swim-runner.ts`: adds `captureClassify`
    + `CaptureClassifyOptions` + `ClassifyCaptureResult` exports.
    Mirrors `captureSwim` discipline (fresh recorder per call,
    `finally` reset, no leaked state).
  - `studies/swim-37/harness/swim-runner.test.ts`: NEW
    `describe("swim-37 harness :: rebase.classify primitive")`
    block with 13 live tests + 1 `it.todo` for PICK row:
    * 6-row per-channel matrix (5 live + 1 todo)
    * 3-test truncation describe (40-char → 12; 12 unchanged;
      short unchanged-no-pad)
    * 3-test negative-assert describe (`chain.id`,
      `chain.step.remaining`, `disabled.reason` all pinned absent
      with `in` checks)
    * 1-test isolation contract (repeated calls don't leak)

Test results: `pnpm vitest run -c test/vitest/vitest.swim-37.config.ts`
→ 8 files / 151 passed / 14 todo (was 138/13; +13 live tests +1 todo).

Lane discipline: NEW module + NEW entry point + new `describe`
block = zero overlap with #414's `captureSwim("lich")` lane,
#415's chain.id pin, or 🌻's incoming heartbeat-wire lane.

Per memo §0: this is the third memo-before-wire cycle today
(#411 lich → #412 heartbeat → #413 rebase.classify), and the
second wire to land off it (#414 lich + this).

Co-authored-by: Ronan 🌊 <ronan@solidor.io>
Co-authored-by: Silas 🌫 <silas@dandelion.cult>
Co-authored-by: Elliott 🌻 <elliott@dandelion.cult>
Co-authored-by: Cael 🩸 <cael@dandelion.cult>

…ionHeartbeatSpan helper (#412) (#417)

Memo-before-wire fold from #412 (merged at `1b84e71c95`). Stacks on
`cael/325-canonical2` between #414 (lich wire) and #416 (rebase.classify wire).

Surface additions to `src/infra/continuation-tracer.ts`:
- New helper `emitContinuationHeartbeatSpan({ heartbeatId?, chainId?,
  chainStepRemaining?, disabledReason?, log? })` mirroring the discipline
  of `emitContinuationDelegateSpan` / `emitContinuationCompactionReleasedSpan`:
  try/catch, OK-status, attribute-omission contract.
- `heartbeat.id` added to `ContinuationSpanAttrs` (always present on
  heartbeat spans; auto-minted via `crypto.randomUUID()` when caller omits).
- `"heartbeat"` added to `CONTINUATION_SIGNAL_KINDS` SSOT.
- `ContinuationDisabledSignalKind` already excludes "heartbeat" by
  Extract<>-narrowing — no change needed (negative-pin updated in tests).

Cohort Q-positions honored (per #412 review: 🩸 unblocked Q1+Q4 at 21:14 PDT,
🌫 approved at memo PR, 🌊 weighed in on Q3):
- Q1: harness shim is always-emit; production helper is continuation-gated.
  Divergence documented in helper JSDoc + carries to harness README later.
- Q2: single `heartbeat` span (NO sibling `heartbeat.fire`); future
  `heartbeat.lag.ms` becomes an attribute, not a sibling span.
- Q3: 5-row `it.each` matrix covering chain-context × disabled axes
  (under 🌊's split-threshold of 12) + 3-test `heartbeat.id` provenance
  describe block. Total +13 live tests, -2 `it.todo`.
- Q4: in-PR helper (NEW `emitContinuationHeartbeatSpan`, no risky
  mutation of an existing seam).

Negative-assert pins (per memo §2 + 🩸's #407 negative-pin pattern):
- `delay.ms` MUST NOT appear (heartbeats fire on cadence, not
  caller-elected delay).
- `chain.step.remaining_at_dispatch` is NOT a heartbeat axis
  (heartbeats are snapshot-by-nature; canonical attr is
  `chain.step.remaining`).
- Both pinned via `expect("<attr>" in attrs).toBe(false)`
  belt-and-braces beyond `toBeUndefined()`.

Tests:
- `pnpm vitest run src/infra/continuation-tracer.test.ts studies/swim-37/harness/swim-runner.test.ts`
  → 108 passed / 11 todo (was 95 passed / 13 todo for these two files).
- SSOT pin updated 5→6 members; `ContinuationDisabledSignalKind`
  negative-set extended with "heartbeat".

Lane discipline: zero overlap with #414 (`lich`), #415 (`chain.id`
absence pin on lich), or #416 (`rebase.classify` in NEW `src/rebase/tracer.ts`).

Co-authored by 🌫 / 🌊 / 🩸 via memo Q-positions on PR #412.

…review) (#418)

Folds three flags from 🌫's #416 second-eye review (msg
`1498543295234834432`):

**Flag 1 — memo §3 validation gap:** memo specced
throw-on-bad-input matching #405/#411/#412 family-resemblance,
wire skipped it. Adds boundary throws in `captureClassify` for:
  - verdict not in REBASE_VERDICTS
  - channel not in REBASE_DISCOVERY_CHANNELS
  - pickSha < 7 hex chars (memo §3 git-prefix-min)
  - pickSha containing non-hex chars

Validation lives at the harness boundary (mirrors
`captureSwim`'s `recipients` invariant at swim-runner.ts:180);
the production helper stays drop-with-log so producer errors
don't propagate to the rebase-bot caller. Same shape as how
`captureSwim` throws on bad Options but
`emitContinuationCompactionReleasedSpan` only logs.

**Flag 2 — truncateSha ↔ memo §3 "≥7 hex chars" tension:** the
`<12 unchanged (helper does not pad)` test from #416 was
contradicting the memo's ≥7 floor. Replaced with
`passes short-but-valid (7-char) SHA through unchanged` which
honors both the memo floor AND the no-pad discipline. Memo +
code + tests now agree.

**Nit — `signal.kind: "rebase.classify"` redundant with span
name:** other helpers use the underlying primitive name as
discriminator (e.g. `"compaction-release"` for
`continuation.compaction.released`), so a downstream filter on
`signal.kind` doesn't redundantly slice the span name. Renamed
to `"rebase-classify"` (hyphen-form, matches family). Memo §2
updated with provenance note (post-#416 review).

Test additions:
  - new `describe("input validation (memo §3 throw-on-bad-input)")`
    block: 4 tests (bad verdict, bad channel, <7 char pickSha,
    non-hex pickSha)
  - existing `<12 unchanged` test deleted, replaced with valid
    7-char passes-through-unchanged

Test results: pnpm vitest run -c test/vitest/vitest.swim-37.config.ts
  → 8 files / 155 passed / 14 todo (was 151/14 from #416 at
    `526540de15`; +4 live tests, same todos)

Lane discipline: same lane as #416 follow-up (mirrors how #415
followed #414); zero overlap with 🌻's incoming heartbeat wire.

Co-authored-by: Ronan 🌊 <ronan@solidor.io>
Co-authored-by: Silas 🌫 <silas@dandelion.cult>

This reverts commit 3396b88.

The original commit mass-deleted 30 files (6745 deletions) under the label
"rejected rebase artifacts." ~5141 of those deletions are landed swim-37
durability harness substrate from merged PRs #412/#413/#414/#416/#417/#418/#419
plus collateral docs/scripts. These are not rejected artifacts — they are
committed, merged test infrastructure that proves continuation durability
across compaction.

Cohort review (🩸 + 🌊 + 🌻 + 🌫) confirmed the block finding at
PR #515 issuecomment-4362337067.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…6.4.24) (#515)

* wo(canonical2-rebase-pathB): rebase Path-B's 5 cleanup commits onto canonical2 (figs directive 22:55Z)

* chore(v3-cleanup): wave A cohort-identity scrub

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* chore(v3-cleanup): drop rejected rebase artifacts

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* docs: scrub workspace template wording

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* refactor(v3-cleanup): wave B structural dedup of continuation runtime

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* docs: journal canonical2 wave B

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* fix(v3-cleanup): wave C import discipline and build warnings

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* docs: journal canonical2 wave C

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* fix(v3-cleanup): wave D surface continuation failures

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* fix: surface compaction count reconcile failures

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* test(v3-cleanup): wave E continuation coverage

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* docs: journal canonical2 wave E

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* fix: align bundled plugin dependency types

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* test: isolate bedrock app profile runtime deps

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* chore: scrub fork process labels from source comments

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* fix: close continuation type design blockers

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* chore: scrub continuation prompt process link

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* docs: journal canonical2 final checkpoint

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Revert "chore(v3-cleanup): drop rejected rebase artifacts"

This reverts commit 3396b88.

The original commit mass-deleted 30 files (6745 deletions) under the label
"rejected rebase artifacts." ~5141 of those deletions are landed swim-37
durability harness substrate from merged PRs #412/#413/#414/#416/#417/#418/#419
plus collateral docs/scripts. These are not rejected artifacts — they are
committed, merged test infrastructure that proves continuation durability
across compaction.

Cohort review (🩸 + 🌊 + 🌻 + 🌫) confirmed the block finding at
PR #515 issuecomment-4362337067.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* docs: release-note for context-pressure band-derivation behavior change

Wave B (cefa09d) changed context-pressure bands from fixed
[25, 80, 90, 95] to threshold-derived [thresholdPct, 90, 95].
At default 0.8 the implicit 25% early-warning band is removed.
Ship-acceptable per cohort review; release-note documents the change
and points to #516 for the earlyWarningBand config opt follow-up.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* fix: restore landed-PR tests missing from rebase fork-point

Three test files from merged PRs (#462, #468, #511) were absent because
this branch forked from canonical2 before those PRs landed. The post-revert
allow-list audit (§3.4) flagged them as deletions from landed PRs.
Restored from canonical2 HEAD (74940e5).

- types.mode-shape.test.ts (#462)
- agent-runner.continuation-span-uniformity.test.ts (#511)
- store.continuation-merge.test.ts (#468)

tmp-drop-me-otel-span-uniformity.md omitted (copilot scratch; safe to drop).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* fix: add rebase.classify to ContinuationSpanName for restored tracer

The revert of 3396b88 restored src/rebase/tracer.ts which emits
"rebase.classify" spans. Commit 4871c81 (fix: close continuation
type design blockers) narrowed startSpan from string to
ContinuationSpanName after tracer.ts was deleted — additive fix to
include the span name in the union.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* feat(continuation): add earlyWarningBand config opt for post-compaction cycle primer

* test(continuation): pin earlyWarningBand default-preservation + opt-out branches

* fix(continuation): add curly braces to satisfy linter

* fix(continuation): unblock early-warning band fire path + make field optional

Three bugs caught in cohort review of v5 (3e88ce5):

1. Suppression guard bug (Silas): non-postCompaction call sites bailed
   with 'ratio < threshold' BEFORE the resolved early-warn band could
   fire. Even with earlyWarningBand explicitly set, ratio=0.25 +
   threshold=0.8 resolved band=25 then was discarded. Guard now
   suppresses only when 'band === 0 && ratio < threshold' — preserves
   the round-to-band-0 dedup edge case while letting early-warn fire.

2. Type-required regression (Elliott): ContinuationRuntimeConfig had
   'earlyWarningBand: number' (required), breaking 3 test fixtures
   (config.test, scheduler.test, post-compaction-delegate-dispatch.test)
   with TS2741. Field already optional at zod + resolver-default site;
   making the type optional matches.

3. Schema baseline regen (Elliott): src/config/schema.base.generated.ts
   needed regen to absorb the new earlyWarningBand field; preexisting
   models.providers.*.request.tls.insecureSkipVerify drift also
   absorbed in the same regen.

Tests added:
- checkContextPressure 'fires early-warning band below threshold when
  earlyWarningBand is set' (default-preservation path)
- checkContextPressure 'does NOT fire below threshold when
  earlyWarningBand is 0' (opt-out path)

All 107 affected tests pass: context-pressure (19), config (9),
scheduler (12), schema.base.generated (10), post-compaction-delegate-
dispatch (23), reply/context-pressure (34).

Cohort cosign chain: 🩸 (root catch v5), 🌊 (default=0 catch),
🌫 (suppression-guard catch), 🌻 (type-required + baseline catch).

Refs #515

---------

Co-authored-by: frond-scribe <frond-scribe@karmaterminal>
Co-authored-by: Test User <test@example.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: dandelion cult - cael 🩸 <cael@dandelion.cult>
Co-authored-by: dandelion cult - silas 🌫 <silas.dandelion.cult@hotmail.com>