ds4-context-engine 0.4.6 → 0.4.8

package/README.md

@@ -16,7 +16,7 @@ bounded active context with provenance
 Pi provider
 ```
 
-> **Project status:** The coordinated `0.4.0` release adds `storage.scope: "agent" | "project"`, now defaulting to per-project SQLite projections with shared token calibration in the agent database (opt out with `storage.scope: "agent"`). The opt-in BPE estimation and bounded auto-tuning from `0.3.10` keep `chars-v1` and disabled auto-tuning as their defaults. The bounded compaction controls from `0.3.9` remain in place; canonical history, SQLite schema 16 and runtime contracts are unchanged. Pi remains pinned to `0.84.3`. Patch `0.4.1` states the contiguous-span rule for compaction summaries in the summarizer prompt while leaving validation strictness, the eight-bullet repair bound and every provider-facing default unchanged. Patch `0.4.2` adds class-only diagnostics for rejected exact-value spans: the existing `custom_fallback` warning carries `unsupportedSpanClasses` as class names and counters, never span text, with validation, repair bounds and provider-facing defaults unchanged. Patch `0.4.3` makes those diagnostics interpretable: every distinct span receives the cheap transformed-form lookups before the bounded near-miss analysis starts, each near-miss candidate may spend only an equal share of what remains, and spans that were not analysed report `not-classified-length`, `not-classified-partial` or `not-classified-budget` instead of `no-near-miss`. Patch `0.4.4` accepts a backticked exact value whose canonical JSON-escaped rendering is literally present in the evidence — the decoded rendering a summarizer produces when it quotes serialized JSON — while absent values, the reverse escape direction, span composition and single-character variants stay rejected; the diagnostics probe budget rises from 4000 to 24000 evidence-source scans. Patch `0.4.5` grades the summarizer quoting fallback: the prompt requires one contiguous excerpt per backticked span, tells the model to backtick only the fragments that are themselves contiguous or to keep the fact as ordinary text without backticks instead of composing a span, and reserves bullet omission for facts with no support in the evidence; diagnostics split composition into `composed-adjacent-present` (both parts next to each other in one source, so the span may be a re-rendering of a contiguous region) and `composed-two-present-parts` (parts found at unrelated positions), with validation strictness, the eight-bullet and 25% repair bounds and every provider-facing default unchanged. Patch `0.4.6` makes an engine/core artifact mismatch visible instead of a missing function: the core exports `CORE_VERSION` and the engine verifies at session start and at every compaction attempt that the loaded core matches its own version and exposes the entry points it calls, so a core rebuilt under a running Pi — which a `/reload` does not pick up — reports one actionable line, keeps the DS4 compaction layer inert instead of failing mid-generation, and never blocks Pi; validation strictness, repair bounds and every provider-facing default stay unchanged. See the [0.4.6 release record](docs/releases/0.4.6.md), the [0.4.5 release record](docs/releases/0.4.5.md), the [0.4.4 release record](docs/releases/0.4.4.md), the [0.4.3 release record](docs/releases/0.4.3.md), the [0.4.2 release record](docs/releases/0.4.2.md), the [0.4.1 release record](docs/releases/0.4.1.md) and the [0.4.0 release record](docs/releases/0.4.0.md), [ADR 067](docs/ADR/067-core-version-guard.md), [ADR 066](docs/ADR/066-quoting-downgrade-and-span-adjacency.md), [ADR 065](docs/ADR/065-exact-value-escaped-equivalence.md), [ADR 064](docs/ADR/064-per-project-databases-with-shared-calibration.md) and [model-awareness validation](docs/MODEL_AWARENESS.md).
+> **Project status:** The coordinated `0.4.0` release adds `storage.scope: "agent" | "project"`, now defaulting to per-project SQLite projections with shared token calibration in the agent database (opt out with `storage.scope: "agent"`). The opt-in BPE estimation and bounded auto-tuning from `0.3.10` keep `chars-v1` and disabled auto-tuning as their defaults. The bounded compaction controls from `0.3.9` remain in place; canonical history, SQLite schema 16 and runtime contracts are unchanged. Pi remains pinned to `0.84.3`. Patch `0.4.1` states the contiguous-span rule for compaction summaries in the summarizer prompt while leaving validation strictness, the eight-bullet repair bound and every provider-facing default unchanged. Patch `0.4.2` adds class-only diagnostics for rejected exact-value spans: the existing `custom_fallback` warning carries `unsupportedSpanClasses` as class names and counters, never span text, with validation, repair bounds and provider-facing defaults unchanged. Patch `0.4.3` makes those diagnostics interpretable: every distinct span receives the cheap transformed-form lookups before the bounded near-miss analysis starts, each near-miss candidate may spend only an equal share of what remains, and spans that were not analysed report `not-classified-length`, `not-classified-partial` or `not-classified-budget` instead of `no-near-miss`. Patch `0.4.4` accepts a backticked exact value whose canonical JSON-escaped rendering is literally present in the evidence — the decoded rendering a summarizer produces when it quotes serialized JSON — while absent values, the reverse escape direction, span composition and single-character variants stay rejected; the diagnostics probe budget rises from 4000 to 24000 evidence-source scans. Patch `0.4.5` grades the summarizer quoting fallback: the prompt requires one contiguous excerpt per backticked span, tells the model to backtick only the fragments that are themselves contiguous or to keep the fact as ordinary text without backticks instead of composing a span, and reserves bullet omission for facts with no support in the evidence; diagnostics split composition into `composed-adjacent-present` (both parts next to each other in one source, so the span may be a re-rendering of a contiguous region) and `composed-two-present-parts` (parts found at unrelated positions), with validation strictness, the eight-bullet and 25% repair bounds and every provider-facing default unchanged. Patch `0.4.6` makes an engine/core artifact mismatch visible instead of a missing function: the core exports `CORE_VERSION` and the engine verifies at session start and at every compaction attempt that the loaded core matches its own version and exposes the entry points it calls, so a core rebuilt under a running Pi — which a `/reload` does not pick up — reports one actionable line, keeps the DS4 compaction layer inert instead of failing mid-generation, and never blocks Pi; validation strictness, repair bounds and every provider-facing default stay unchanged. Patch `0.4.7` stops the recurrent fail-closed fallback at its source: when the summarizer re-renders a value the evidence holds in another form — JSON-escaped or unescaped, collapsed whitespace, stripped typographic characters, or two parts adjacent in one source — the repair retracts only the backticks and keeps the fact, so those spans no longer consume the eight-bullet bound; invented values, unrelated compositions, one-character deviations, case changes and unanalysed spans keep the existing fail-closed bullet removal, validation strictness is unchanged, and both effects are recorded as counters (`unsupported-exact-bullets-pruned`, `unsupported-exact-spans-unquoted`). Patch `0.4.8` ends the recurrent exact-value fallback at its root: an unsupported backticked value no longer costs its bullet or the whole compaction — the repair retracts the quoting of every rejected span, keeps the text as prose and re-validates, so exact-value failures cannot end a compaction while every surviving backticked value is still verified literally or as its canonical JSON-escaped rendering; the eight-bullet and 25% removal bounds no longer apply to this path, structural, transport and budget failures still fall back to Pi, and the class report remains class-only diagnostics. See the [0.4.8 release record](docs/releases/0.4.8.md), the [0.4.7 release record](docs/releases/0.4.7.md), the [0.4.6 release record](docs/releases/0.4.6.md), the [0.4.5 release record](docs/releases/0.4.5.md), the [0.4.4 release record](docs/releases/0.4.4.md), the [0.4.3 release record](docs/releases/0.4.3.md), the [0.4.2 release record](docs/releases/0.4.2.md), the [0.4.1 release record](docs/releases/0.4.1.md) and the [0.4.0 release record](docs/releases/0.4.0.md), [ADR 069](docs/ADR/069-retract-quoting-of-every-unsupported-exact-value.md), [ADR 068](docs/ADR/068-downgrade-rendering-equivalent-spans.md), [ADR 067](docs/ADR/067-core-version-guard.md), [ADR 066](docs/ADR/066-quoting-downgrade-and-span-adjacency.md), [ADR 065](docs/ADR/065-exact-value-escaped-equivalence.md), [ADR 064](docs/ADR/064-per-project-databases-with-shared-calibration.md) and [model-awareness validation](docs/MODEL_AWARENESS.md).
 
 **Current compaction defaults:** `compaction.directUpdate=true`, `compaction.inputBudget="context"`, `compaction.segmentTargetTokens=30000`, `compaction.maxRequestInputTokens=64000`, `compaction.maxOperationInputTokens=2000000`, `compaction.maxConcurrentSegments=2`. Every DS4 provider attempt is bounded by the effective request limit, and the operation limit includes retries; `inputBudget="summary"` remains an explicit throughput-oriented opt-in. Existing compaction/master switches still apply. See [latency controls and compatibility](docs/COMPACTION.md#latency-controls). No real-provider speedup is claimed from mock tests. The five optional editing/reading/artifact/job features introduced in `0.3.4` remain default-off.
 
@@ -515,6 +515,7 @@ scripts             package and release-readiness checks
 - [Roadmap 0.2.0](docs/ROADMAP_0.2.0.md)
 - [Release process](docs/RELEASING.md)
 - [0.2.0 release readiness](docs/RELEASE_READINESS_0.2.0.md)
+- [0.4.7 release notes](docs/releases/0.4.7.md)
 - [0.4.6 release notes](docs/releases/0.4.6.md)
 - [0.4.5 release notes](docs/releases/0.4.5.md)
 - [0.4.4 release notes](docs/releases/0.4.4.md)

package/docs/ADR/068-downgrade-rendering-equivalent-spans.md

@@ -0,0 +1,75 @@
+# 068 — Downgrade rendering-equivalent spans instead of spending the bullet budget
+
+**Date:** 2026-09-27
+**Status:** Accepted
+**Related:** [065](065-exact-value-escaped-equivalence.md), [066](066-quoting-downgrade-and-span-adjacency.md), [067](067-core-version-guard.md)
+
+## Context
+
+Five coordinated releases reduced, but never removed, the recurrent
+`compaction.custom_fallback` with `unsupported-exact-value;
+repair=too-many-bullets`. The affected-bullet series from production was 30/20 →
+23/19 → 19/15 → 17/11 → 16/12, and the class-only reports attributed the majority
+of the rejected spans to rendering or composition, never to invention:
+`escaped-form-present` 11 of 16 in the first interpretable run, then composition
+9 of 14 with 2 one-character deviations, 2 absences and 1 over-length span in the
+next.
+
+Each patch removed one class — escaped equivalence in 0.4.4, prompt grading in
+0.4.5 — while the bound stayed exhausted by the remaining ones. The repair was
+treating a *re-rendered* value exactly like an *invented* one: it deleted whole
+bullets, and beyond eight bullets it refused to repair at all and handed the
+session to Pi. The information in those spans is present in the evidence; only
+the verbatim surface form is not. Discarding a supported fact, or failing, is the
+wrong response to a rendering difference.
+
+## Decision
+
+- Validation is unchanged. A backticked value is still accepted only when it
+  occurs literally in the evidence or as its canonical JSON-escaped rendering.
+  Nothing that was rejected before becomes an accepted exact value.
+- The bounded repair splits the rejected spans into two groups.
+  - **Rendering-equivalent** — `escaped-form-present`, `unescaped-form-present`,
+    `whitespace-collapsed-present`, `typographic-variant-present`,
+    `composed-adjacent-present`: DS4 removes only the two backticks. The text
+    stays, the fact stays, the exact-value claim is retracted, and the result is
+    re-validated. This applies deterministically the ladder the 0.4.5 prompt asks
+    the model to follow, instead of depending on the model complying.
+  - **Everything else** — `single-deletion-present`,
+    `composed-two-present-parts`, `case-variant-present`, `no-near-miss` and
+    every `not-classified-*`: the existing fail-closed treatment, whole-bullet
+    removal within the eight-bullet and 25% bounds, otherwise fallback to Pi.
+- The excluded relations are excluded because prose would hide a wrong claim
+  rather than a re-rendered one: a case change can alter an identifier, a
+  one-character deviation is indistinguishable from a wrong value, and
+  `composed-two-present-parts` is precisely the association the evidence does not
+  contain ([ADR 066](066-quoting-downgrade-and-span-adjacency.md)).
+  `not-classified-*` means *not analysed*, which is not evidence of support, so
+  those spans stay fail-closed as well.
+- The eight-bullet and 25% bounds are not raised. They now count only the bullets
+  that still need removal, because a downgraded span costs no bullet.
+- Both effects are recorded as counters, never as span text:
+  `unsupported-exact-bullets-pruned` for removed bullets and
+  `unsupported-exact-spans-unquoted` for downgraded spans.
+
+## Consequences
+
+- The dominant production failure mode no longer consumes the bullet bound. In
+  the core fixtures, twelve affected bullets now downgrade to plain text and
+  validate, where the same input previously answered `too-many-bullets`; the
+  integration fixture with eleven affected bullets completes with
+  `validationStatus: "warning"` instead of Pi compacting the session.
+- Fail-closed survives where it matters. An invented value keeps the
+  bullet-removal path, and the same eleven-bullet fixture still answers
+  `repair=too-many-bullets` when the evidence holds the two parts at unrelated
+  positions rather than next to each other.
+- The repair now consumes the class analysis, which is bounded and deterministic
+  but budget-limited (default 24000 evidence-source scans). A span left
+  unanalysed is never downgraded.
+- A downgraded value is still *stated* as prose: DS4 stops asserting exactness it
+  cannot verify, but it does not delete the fact. That is the deliberate trade —
+  a fact with a possibly imperfect surface form beats losing the fact or losing
+  the whole compaction — and it is visible in the recorded counters.
+- The `UnsupportedSpanClassReport` documentation no longer claims the relations
+  are observation-only: they now select the repair treatment. Validation still
+  never consults them.

package/docs/ADR/069-retract-quoting-of-every-unsupported-exact-value.md

@@ -0,0 +1,78 @@
+# 069 — Retract the quoting of every unsupported exact value instead of failing the compaction
+
+**Date:** 2026-09-28
+**Status:** Accepted
+**Related:** [065](065-exact-value-escaped-equivalence.md), [066](066-quoting-downgrade-and-span-adjacency.md), [068](068-downgrade-rendering-equivalent-spans.md)
+
+## Context
+
+Six coordinated releases (0.4.1–0.4.7) reduced, but never removed, the recurrent
+`compaction.custom_fallback` with `unsupported-exact-value;
+repair=too-many-bullets`. The affected-bullet series from production was 30/20 →
+23/19 → 19/15 → 17/11 → 16/12, and the report that closed the case carried 25
+spans across 15 bullets.
+
+That report shows why the class-by-class repair cannot converge:
+
+| Relation | Count |
+| --- | --- |
+| `composed-two-present-parts` | 11 |
+| `not-classified-partial` | 5 |
+| `not-classified-length` | 4 |
+| `composed-adjacent-present` | 3 |
+| `no-near-miss` | 2 |
+
+`spansClassifiedCheap` was 0: not one span was a rendering variant of contiguous
+evidence, so the escape path was exhausted. The 0.4.7 repair could retract the
+quoting of at most the three adjacent spans; the remaining 22 spans kept the
+bullet-removal path, and 15 − 3 = 12 bullets still exceeded the eight-bullet
+bound. On that input 0.4.7 would have fallen back by construction.
+
+The classes are not a finite list of odd renderings to eliminate one release at a
+time. They are one behaviour: the summarizer composes and paraphrases spans. The
+validator cannot accept `composed-two-present-parts` — that association is
+precisely what the evidence does not contain — and no rendering normalization
+turns a composed span into a contiguous excerpt.
+
+## Decision
+
+- Validation is unchanged. A backticked value that the evidence does not hold
+  literally, or as its canonical JSON-escaped rendering, is still invalid.
+- The repair retracts the two backticks of **every** unsupported span in place,
+  keeps the text, and the repaired summary is re-validated. No bullet is deleted
+  for an exact-value failure, so the eight-bullet and 25% removal bounds no
+  longer apply to this path.
+- The repair no longer consults the span classification. The class-only report
+  stays as diagnostics and is still attached to the fallback warning, which now
+  fires only for structural, transport or budget failures.
+- Fallback remains for missing, duplicate or empty sections, unsupported file
+  paths, unknown sections or headings, malformed content, transport and budget
+  failures, and any summary that is still invalid after the retraction
+  (`post-downgrade-invalid`).
+- Outcomes are counters, never span text: `unsupported-exact-spans-unquoted`
+  records the retracted spans, and `unsupported-exact-bullets-pruned` no longer
+  exists.
+
+## Consequences
+
+- The dominant production failure mode cannot fail the compaction any more. The
+  fact stays as prose, the exactness claim goes, and every value that remains
+  backticked is still verified literally or as its canonical JSON-escaped
+  rendering. This supersedes the exclusion list of
+  [ADR 068](068-downgrade-rendering-equivalent-spans.md).
+- The trade is explicit: a value the evidence does not carry — including an
+  invented one — is no longer deleted, and the eight-bullet and 25% bounds no
+  longer protect it. Losing a fact, or losing the whole DS4 compaction to Pi's
+  default, was judged worse; the fallback this replaces does not check exact
+  values at all.
+- An unsupported value remains visible in the summary as prose and in the
+  recorded counter, so the operator can review it instead of relying on the
+  bullet removal.
+- The public core repair API changes: `analyzeUnsupportedExactValueDowngrade`
+  and `downgradeUnsupportedExactValues` replace
+  `analyzeUnsupportedExactValueBullets` and `pruneUnsupportedExactValueBullets`,
+  and `ExactValueDowngradeResult`/`ExactValueDowngradeAttempt` replace the
+  `ExactValuePrune*` types. The engine/core compatibility guard turns a mixed
+  artifact pair into one actionable line instead of a missing function.
+- No configuration key, no SQLite migration, no schema change, and no
+  provider-facing default change.

package/docs/ADR/README.md

@@ -71,5 +71,7 @@ The initial decisions from the development plan are accepted:
 | [065](065-exact-value-escaped-equivalence.md) | Accept canonical JSON-escaped exact values in compaction summary validation | Accepted |
 | [066](066-quoting-downgrade-and-span-adjacency.md) | Grade the summarizer quoting fallback and separate adjacent from unrelated span composition | Accepted |
 | [067](067-core-version-guard.md) | Detect an engine/core artifact mismatch before compaction runs | Accepted |
+| [068](068-downgrade-rendering-equivalent-spans.md) | Downgrade rendering-equivalent spans instead of spending the bullet budget | Accepted |
+| [069](069-retract-quoting-of-every-unsupported-exact-value.md) | Retract the quoting of every unsupported exact value instead of failing the compaction | Accepted |
 
 Each decision will receive a dedicated record when implementation pressure introduces alternatives or consequences not already covered by the development plan.

package/docs/COMPACTION.md

@@ -32,17 +32,17 @@ Fan-out and fan-in are bounded to 32 segment requests, 64 aggregate requests, an
 ## Critical Exact Values
 ```
 
-Every section must occur once, in order, and contain content or `- None`. DS4 replaces each unique `Files Read` and `Files Modified` section with one exact path per bullet from Pi's sanitized file-operation inventory before validation; missing or duplicate sections still fail. Backticked exact values must occur literally in the serialized segment source, ordered child-summary content, or those known file-operation paths, either as written or in the canonical JSON-escaped rendering of the value. A decoded value whose encoded text is present in the evidence is accepted ([ADR 065](ADR/065-exact-value-escaped-equivalence.md)); the reverse direction — an escaped span whose raw form is present — remains unsupported and is reported as `unescaped-form-present`. A bounded unsupported exact-value bullet is removed as a whole and recorded as a validation warning; unsupported prose, more than eight affected bullets, or removal above 25% still fails closed to Pi. The prompt requires every backticked span to be one contiguous excerpt copied as-is and forbids assembling one span from separately supported values (a setting name with its value, a path with a line range, a command with its flags), and it gives the model a cheaper alternative than composing: backtick only the fragments that are themselves contiguous with the joining text outside the backticks, or write the value as ordinary text without backticks, keeping the bullet. A bullet is omitted only when the fact itself has no support in the evidence ([ADR 066](ADR/066-quoting-downgrade-and-span-adjacency.md)). Every segment is validated independently against only its own sanitized source and deterministic file inventory. Every aggregate is validated independently against only the sanitized content of its ordered children and cumulative deterministic file inventory. A direct update is validated against both the sanitized previous summary and new source, plus cumulative sanitized file evidence; previous-summary-only exact values remain valid evidence. Custom focus instructions are not factual evidence. Any unrepaired failure prevents the whole graph batch from being installed.
+Every section must occur once, in order, and contain content or `- None`. DS4 replaces each unique `Files Read` and `Files Modified` section with one exact path per bullet from Pi's sanitized file-operation inventory before validation; missing or duplicate sections still fail. Backticked exact values must occur literally in the serialized segment source, ordered child-summary content, or those known file-operation paths, either as written or in the canonical JSON-escaped rendering of the value. A decoded value whose encoded text is present in the evidence is accepted ([ADR 065](ADR/065-exact-value-escaped-equivalence.md)); the reverse direction — an escaped span whose raw form is present — remains unsupported and is reported as `unescaped-form-present`. Every unsupported span is repaired the same way: the two backticks are retracted and the text stays, so the fact survives as prose and the exact-value claim does not ([ADR 069](ADR/069-retract-quoting-of-every-unsupported-exact-value.md)). No bullet is deleted for an exact-value failure, the eight-bullet and 25% removal bounds no longer apply to it, and the repaired summary is re-validated: any remaining structural problem still fails closed to Pi, and every backticked value that survives is still verified literally or as its canonical JSON-escaped rendering. The prompt requires every backticked span to be one contiguous excerpt copied as-is and forbids assembling one span from separately supported values (a setting name with its value, a path with a line range, a command with its flags), and it gives the model a cheaper alternative than composing: backtick only the fragments that are themselves contiguous with the joining text outside the backticks, or write the value as ordinary text without backticks, keeping the bullet. A bullet is omitted only when the fact itself has no support in the evidence ([ADR 066](ADR/066-quoting-downgrade-and-span-adjacency.md)). Every segment is validated independently against only its own sanitized source and deterministic file inventory. Every aggregate is validated independently against only the sanitized content of its ordered children and cumulative deterministic file inventory. A direct update is validated against both the sanitized previous summary and new source, plus cumulative sanitized file evidence; previous-summary-only exact values remain valid evidence. Custom focus instructions are not factual evidence. Any unrepaired failure prevents the whole graph batch from being installed.
 
-An unrepaired exact-value failure reports only the stage, issue code, categorical repair status, unsupported-span count, and affected-bullet count. Repair statuses distinguish an unsupported location, more than eight bullets, removal above 25%, and an unexpected invalid second validation. The disputed text is intentionally absent from logs, UI notifications, and diagnostics because it may contain sensitive source material.
+A fail-closed compaction reports only the stage, issue codes, the repair status, the unsupported-span count and the affected-bullet count. An exact-value repair either retracts the quoting (`downgraded`) or is not needed; a summary that is still invalid after the retraction is reported as `post-downgrade-invalid` and remains a structural failure. The disputed text is intentionally absent from logs, UI notifications, and diagnostics because it may contain sensitive source material.
 
-The same failure carries a class-only span report on the fallback warning (`unsupportedSpanClasses`): rejected-span count, affected bullets, length buckets, character shapes (spaces, backslashes, escape sequences, separators, quotes, typographic characters, JSON punctuation), and how each distinct span relates to the evidence — escaped or unescaped rendering, collapsed whitespace, case or typographic variant, one-character deletion, two separately present values joined into one span — adjacent in one source with nothing but joining punctuation and spaces between them (`composed-adjacent-present`) or found at unrelated positions (`composed-two-present-parts`) — or no near-miss (every applicable lookup ran and found nothing). The adjacency question separates a join that re-renders a contiguous evidence region from an association the evidence never contains: a joiner gap holds no letters, digits or line breaks, so two parts on separate lines are not adjacent. The report contains class names and counters only, never span text, and the classifier is observation-only: it cannot change validation, repair bounds, or the fail-closed decision. It exists to separate a summarizer that invents values from one whose rendering or composition rules differ from the validation domain, which require opposite fixes. The first production report produced by the 0.4.4 diagnostics attributed 9 of 14 rejected spans to composition, 2 to a one-character deviation, 2 to absence and 1 to the length limit, with no rendering class left at all.
+The same failure carries a class-only span report on the fallback warning (`unsupportedSpanClasses`): rejected-span count, affected bullets, length buckets, character shapes (spaces, backslashes, escape sequences, separators, quotes, typographic characters, JSON punctuation), and how each distinct span relates to the evidence — escaped or unescaped rendering, collapsed whitespace, case or typographic variant, one-character deletion, two separately present values joined into one span — adjacent in one source with nothing but joining punctuation and spaces between them (`composed-adjacent-present`) or found at unrelated positions (`composed-two-present-parts`) — or no near-miss (every applicable lookup ran and found nothing). The adjacency question separates a join that re-renders a contiguous evidence region from an association the evidence never contains: a joiner gap holds no letters, digits or line breaks, so two parts on separate lines are not adjacent. The report contains class names and counters only, never span text, and it is observation-only: neither validation nor the repair consults the relations, because every unsupported span is downgraded whatever its class. It exists to separate a summarizer that invents values from one whose rendering or composition rules differ from the validation domain, which would call for opposite prompt or model changes. The first production report produced by the 0.4.4 diagnostics attributed 9 of 14 rejected spans to composition, 2 to a one-character deviation, 2 to absence and 1 to the length limit, with no rendering class left at all.
 
 Three relations mark spans that were *not* analysed, and they must never be read as invention. `not-classified-length` means the span exceeds the near-miss length limit (96 characters); `not-classified-partial` means its share of the budget ran out; `not-classified-budget` means the shared budget was already exhausted. To keep the histogram interpretable, transformed-form lookups cover every distinct span before any near-miss analysis starts, and each near-miss candidate may spend only an equal share of what remains (at least 32 lookups, never more than the budget left). The report also carries `spansClassifiedCheap` (span occurrences attributed by a transformed-form relation), `corpusSources`, `probeBudget` and `probesUsed`, so a run can be read without guessing how much of the budget was consumed. The shared budget defaults to 24000 evidence-source scans, where one lookup scans every corpus source once. `escaped-form-present` is not expected in reports from 0.4.4 on: validation accepts the canonical escaped rendering and the classifier consumes the same predicate, so such spans no longer reach it; the class stays in the taxonomy for compatibility. `classificationComplete` is false when the shared budget or a per-span share stopped an analysis; a `not-classified-length` span does not clear it, because that limit is deterministic rather than a resource shortfall.
 
 ## Provenance and recovery
 
-The engine checks its own contract with the loaded core at session start and at the start of every compaction attempt: `CORE_VERSION` must equal the extension version and the core entry points the extension calls must be present. Because Pi loads extension sources from TypeScript but keeps dependency modules loaded for the life of the process, a core rebuilt under a running Pi stays stale in memory and a `/reload` is not enough to pick it up; without the check the first missing export surfaced as `... is not a function` deep inside generation. A mismatch now logs `runtime.core_incompatible`, notifies once with the versions and the failing entry point, and leaves the compaction coordinator uncreated, so `/context compaction` reports `enabled: false` with that reason and Pi's own compaction is the only behaviour left. The guard is detection only: it never changes validation, repair bounds or the fail-closed decision, and it never throws while the extension is loading, because Pi treats an extension load error as fatal ([ADR 067](ADR/067-core-version-guard.md)).
+The engine checks its own contract with the loaded core at session start and at the start of every compaction attempt: `CORE_VERSION` must equal the extension version and the core entry points the extension calls must be present. Because Pi loads extension sources from TypeScript but keeps dependency modules loaded for the life of the process, a core rebuilt under a running Pi stays stale in memory and a `/reload` is not enough to pick it up; without the check the first missing export surfaced as `... is not a function` deep inside generation. A mismatch now logs `runtime.core_incompatible`, notifies once with the versions and the failing entry point, and leaves the compaction coordinator uncreated, so `/context compaction` reports `enabled: false` with that reason and Pi's own compaction is the only behaviour left. The guard is detection only: it never changes validation, repair behaviour or the fail-closed decision, and it never throws while the extension is loading, because Pi treats an extension load error as fatal ([ADR 067](ADR/067-core-version-guard.md)).
 
 `CompactionEntry.details` contains cumulative `readFiles` and `modifiedFiles` plus:
 

package/docs/releases/0.4.6.md

@@ -129,9 +129,24 @@ repair bounds or the fail-closed decision changes
 
 ## Publication and registry verification
 
-Published manually in dependency order: `ds4-context-core@0.4.6`, then
-`ds4-context-reference-adapter@0.4.6`, then `ds4-context-engine@0.4.6`, all with
-the default `latest` tag, after `npm run pack:check` on the same commit, followed
-by `npm run registry:check -- 0.4.6` with a fresh npm cache, the annotated tag
-`v0.4.6` and the GitHub Release. No session data, credentials, provider payloads
-or prompt text were read or written while preparing this release.
+Published manually in dependency order from `92912a1`: `ds4-context-core@0.4.6`,
+then `ds4-context-reference-adapter@0.4.6`, then `ds4-context-engine@0.4.6`, all
+with the default `latest` tag, after `npm run pack:check` on the same commit.
+
+The first two `npm run registry:check -- 0.4.6` attempts, each with a fresh npm
+cache, failed with `ETARGET No matching version found for
+ds4-context-core@0.4.6` — the known registry propagation delay after a publish,
+not a packaging fault. Once both `npm view ds4-context-core@0.4.6 version` and
+`npm view ds4-context-engine@0.4.6 version` resolved, the check reported
+"Verified all DS4 registry packages at exact version 0.4.6": all three packages
+install in a clean consumer, the exact adapter/core dependencies resolve, the
+public core and KV exports import, the compiled reference conformance and
+packaged quality corpus run, the `ds4-context-storage` CLI shim responds, and the
+published Pi extension starts against isolated offline RPC state. 
+`npm view <package> dist-tags.latest` resolves to 0.4.6 for all three packages.
+
+Annotated tag `v0.4.6` and the GitHub Release were created from `92912a1`: 
+<https://github.com/Alucard24/ds4-context-engine/releases/tag/v0.4.6>. No session
+data, credentials, provider payloads or prompt text were read or written while
+preparing this release, and no provider call is involved in the release
+procedure.

package/docs/releases/0.4.7.md

@@ -0,0 +1,158 @@
+# Release 0.4.7 — Downgrade rendering-equivalent spans instead of spending the bullet budget
+
+**Coordinated packages:** `ds4-context-core`, `ds4-context-reference-adapter`, and `ds4-context-engine` 0.4.7.
+**Implementation commit:** `1483bce`.
+
+## Summary
+
+Behaviour patch that removes the source of the recurrent fail-closed fallback.
+Until 0.4.6 the repair treated a re-rendered exact value exactly like an invented
+one: it deleted whole bullets, and beyond eight affected bullets it refused to
+repair at all and handed the session to Pi. The class reports had shown for four
+releases that this was the common case — rendering and composition, not
+invention. The repair now retracts only the backticks of a span whose information
+the evidence holds in another rendering, keeps the text and the fact, and
+re-validates. Invented values, unrelated compositions, one-character deviations,
+case changes and unanalysed spans keep the existing fail-closed bullet removal.
+Validation strictness, the eight-bullet and 25% bounds, the fail-closed fallback,
+SQLite schema 16, canonical JSONL history and every provider-facing default are
+unchanged.
+
+## Changes
+
+- `packages/core/src/compaction/summary-contract.ts`:
+  - `RENDERING_EQUIVALENT_RELATIONS` names the relations that mean "the evidence
+    holds this information in a different rendering": `escaped-form-present`,
+    `unescaped-form-present`, `whitespace-collapsed-present`,
+    `typographic-variant-present` and `composed-adjacent-present`.
+  - Deliberately excluded, because prose would hide a wrong claim rather than a
+    re-rendered one: `case-variant-present` (a case change can alter an
+    identifier), `single-deletion-present` (a one-character deviation is
+    indistinguishable from a wrong value), `composed-two-present-parts` (the
+    evidence never contains that association) and every `not-classified-*`
+    relation (*not analysed* is not evidence of support).
+  - `downgradeRenderingEquivalentSpans` removes the two backticks of each
+    rendering-equivalent span, byte-range based and applied after the bullet
+    removals so every span is matched at its final position.
+  - `analyzeUnsupportedExactValueBullets` partitions the rejected spans, applies
+    the unchanged bounds to the ones that still need removal, and reports the
+    new counters. `ExactValuePruneResult` and `ExactValuePruneAttempt` gained
+    `downgradedSpans`, and the attempt status gained `downgraded` and
+    `unrepairable`.
+  - The span classifier is no longer described as observation-only: it is
+    `analyzeSpanClasses` internally, and its relations now also select the repair
+    treatment. Validation still never consults them, and the public
+    `classifyUnsupportedExactValueSpans` report is unchanged.
+- `src/pi-adapter/summary-generator.ts`: the repair outcome is recorded as counts
+  only — `unsupported-exact-bullets-pruned` for removed bullets and the new
+  `unsupported-exact-spans-unquoted` for retracted quotes.
+- `tests/unit/summary-contract.test.ts`: five cases — a composed span with parts
+  adjacent in one source is downgraded and the summary still validates; a span
+  whose whitespace-collapsed and JSON-unescaped renderings are present is
+  downgraded too; unrelated compositions and one-character deviations still cost
+  their bullet; twelve affected bullets downgrade where the same summary without
+  the adjacent rendering still answers `too-many-bullets`; a mixed summary
+  removes only the one bullet that needs it and downgrades the other nine.
+- `tests/integration/compaction.test.ts`: eleven affected bullets complete the
+  compaction with `validationStatus: "warning"` and
+  `validationIssueCodes: ["unsupported-exact-spans-unquoted"]` instead of falling
+  back, and the same fixture with the two parts at unrelated positions still
+  returns `repair=too-many-bullets` with Pi compacting the session.
+- `docs/COMPACTION.md`, `docs/ADR/068-downgrade-rendering-equivalent-spans.md`
+  and the ADR index record the decision.
+
+## Why
+
+The affected-bullet series from production was 30/20 → 23/19 → 19/15 → 17/11 →
+16/12, every run ending in `compaction.custom_fallback` with
+`unsupported-exact-value; repair=too-many-bullets`. The class-only reports
+attributed the rejected spans to rendering or composition in every interpretable
+run: `escaped-form-present` 11 of 16 in the first, then composition 9 of 14 with
+2 one-character deviations, 2 absences and 1 over-length span in the second.
+`no-near-miss` — the class that means invention — was the smallest in both.
+
+Each earlier patch removed one class (escaped equivalence in 0.4.4, prompt
+grading in 0.4.5) while the bound stayed exhausted by the rest, so the fallback
+persisted. The information in those spans was present all along; only the
+verbatim surface form was not, and discarding a supported fact — or losing the
+compaction — is the wrong response to a rendering difference. The repair now
+applies deterministically the ladder the 0.4.5 prompt asks the model to follow,
+instead of depending on the model complying
+([ADR 068](ADR/068-downgrade-rendering-equivalent-spans.md)).
+
+## Privacy and safety
+
+- Only the backticks are removed. Span text is never logged, notified or
+  persisted in diagnostics: the recorded effects are two counters, and the
+  failure path keeps the class-only report.
+- No provider call is added: the downgrade happens after generation, on text the
+  model already produced.
+- The downgraded text is sanitized output that already passed privacy handling;
+  removing backticks does not change its classification.
+
+## Compatibility and persistence
+
+- No configuration key is added or changed. `downgradedSpans` is additive on the
+  repair result, and `unsupported-exact-spans-unquoted` is a new issue code in
+  the recorded node details.
+- The eight-bullet and 25% bounds are not raised: they now count only the bullets
+  that still need removal. A span downgraded in place consumes no bullet.
+- SQLite schema 16, migrations, the Pi JSONL boundary, tool contracts and the
+  reference adapter's public surface are untouched.
+
+## Measured scope and limitations
+
+- Verified by fixtures, not yet by a natural production failure: the first real
+  `compaction.custom_fallback` (or its absence) after updating the failing host
+  remains the end-to-end confirmation.
+- The fallback is still possible — deliberately — when more than eight bullets
+  contain genuinely unsupported spans or when removal would exceed 25% of the
+  summary. Those are the cases where the evidence does not hold the information.
+- A downgraded value is still stated, as prose. DS4 stops asserting exactness it
+  cannot verify but does not delete the fact, and the counters make the trade
+  visible.
+- The repair now consumes the bounded class analysis (default 24000
+  evidence-source scans). A span left unanalysed is never downgraded, so budget
+  exhaustion keeps the previous fail-closed behaviour.
+- `case-variant-present` is intentionally not downgraded, so summaries that only
+  differ by letter case still take the bullet-removal path. If production reports
+  show that class dominating, that is the next measured decision.
+
+## Validation
+
+- `npm run check` on the release commit: builds, `tsc --noEmit`, and
+  **100 test files / 649 tests passed** (7 new: 5 unit cases for the repair rule
+  and 2 integration cases, one of which pins the unchanged fallback on unrelated
+  composition).
+- `npm run pack:check` in a clean consumer: `ds4-context-core@0.4.7`
+  (251 files), `ds4-context-reference-adapter@0.4.7` (7 files) and
+  `ds4-context-engine@0.4.7` (110 files).
+- `npm run quality:compare`: candidate `task-weighted-v0.2-candidate` 0.9875
+  against the frozen baseline `static-ranking-v0.1` 0.808156, unchanged.
+- `npm run schema:context-persistence` (`passed: true`).
+- No provider calls are involved. `jev_verify` is not available in this
+  environment (project verification disabled), so the checks above were run
+  directly.
+
+## Publication and registry verification
+
+Published manually in dependency order from `bf221b5`: `ds4-context-core@0.4.7`,
+then `ds4-context-reference-adapter@0.4.7`, then `ds4-context-engine@0.4.7`, all
+with the default `latest` tag, after `npm run check` and `npm run pack:check` on
+the same commit.
+
+`npm run registry:check -- 0.4.7` needed five attempts, each with a fresh npm
+cache, before the registry CDN served the new packuments (the known propagation
+delay after a publish); the fifth reported "Verified all DS4 registry packages at
+exact version 0.4.7". All three packages install in a clean consumer, the exact
+adapter/core dependencies resolve, the public core and KV exports import, the
+compiled reference conformance and packaged quality corpus run, the
+`ds4-context-storage` CLI shim responds, and the published Pi extension starts
+against isolated offline RPC state. `npm view <package> dist-tags.latest`
+resolves to 0.4.7 for all three packages.
+
+Annotated tag `v0.4.7` and the GitHub Release were created from `bf221b5`:
+<https://github.com/Alucard24/ds4-context-engine/releases/tag/v0.4.7>. No session
+data, credentials, provider payloads or prompt text were read or written while
+preparing this release, and no provider call is involved in the release
+procedure.

package/docs/releases/0.4.8.md

@@ -0,0 +1,109 @@
+# Release 0.4.8 — Retract the quoting of every unsupported exact value
+
+**Coordinated packages:** `ds4-context-core`, `ds4-context-reference-adapter`, and `ds4-context-engine` 0.4.8.
+**Implementation commit:** `f0a457a`.
+
+## Summary
+
+Behaviour patch that ends the recurrent `compaction.custom_fallback` with
+`unsupported-exact-value`. Validation is unchanged: a backticked value the
+evidence does not hold literally, or as its canonical JSON-escaped rendering, is
+still invalid. What changes is the repair: it retracts the two backticks of
+**every** unsupported span in place, keeps the text, and the repaired summary is
+re-validated. No bullet is deleted for an exact-value failure, so the
+eight-bullet and 25% removal bounds no longer apply to that path, and the repair
+no longer consults the span classification, which stays as class-only
+diagnostics on the fallback warning. Fallback remains for structural, transport
+and budget failures. SQLite schema 16, canonical JSONL history and every
+provider-facing default are unchanged.
+
+## Changes
+
+- `packages/core/src/compaction/summary-contract.ts`: the repair API is now
+  `analyzeUnsupportedExactValueDowngrade` and `downgradeUnsupportedExactValues`,
+  with `ExactValueDowngradeResult` / `ExactValueDowngradeAttempt` replacing the
+  `ExactValuePrune*` types and statuses.
+  - `downgradeUnsupportedExactSpans` retracts the backticks of every span
+    returned by the existing `unsupportedExactMatches` and leaves the text.
+  - `affectedBulletCount` reports the bullets that contained a rejected span.
+  - `RENDERING_EQUIVALENT_RELATIONS` and `renderingEquivalentSpans` are removed:
+    the repair no longer needs the classifier.
+  - The classifier keeps its bounded analysis and the class-only report, now
+    documented as observation-only again.
+- `src/pi-adapter/summary-generator.ts`: the downgrade outcome is recorded as
+  `unsupported-exact-spans-unquoted`; `unsupported-exact-bullets-pruned` no
+  longer exists, and a summary still invalid after the retraction is reported as
+  `post-downgrade-invalid`.
+- `tests/unit/summary-contract.test.ts` and
+  `tests/unit/summary-generator.test.ts` cover the downgrade of supported,
+  composed, one-character-deviant, over-length and absent spans, the
+  disappearing bounds, and the class-only report on a structural failure.
+  `tests/unit/compaction-optimizations.test.ts` and
+  `tests/integration/compaction.test.ts` cover the completed compaction with
+  `validationStatus: "warning"` and the privacy-safe counters.
+- `docs/COMPACTION.md`, `docs/ADR/069-retract-quoting-of-every-unsupported-exact-value.md`
+  and the ADR index record the decision; `README.md` links the release.
+
+## Why
+
+The affected-bullet series from production was 30/20 → 23/19 → 19/15 → 17/11 →
+16/12, every run ending in `compaction.custom_fallback` with
+`unsupported-exact-value; repair=too-many-bullets`. The class-only report that
+closed the attribution carried 25 spans across 15 bullets: `spansClassifiedCheap`
+was 0, so no span was a rendering variant of contiguous evidence; 11 spans were
+compositions whose parts sit at unrelated positions, 5 spent their share of the
+analysis budget, 4 exceeded the length limit, 3 were adjacent compositions and 2
+had no near-miss at all.
+
+On that input the 0.4.7 repair could retract the quoting of at most the three
+adjacent spans. The remaining 22 spans kept the bullet-removal path, and
+15 − 3 = 12 bullets still exceeded the eight-bullet bound, so 0.4.7 would have
+fallen back by construction on the same input. The classes are not a finite list
+of odd renderings to eliminate one release at a time: they are the summarizer's
+normal composing and paraphrasing behaviour, and an association the evidence
+does not contain (`composed-two-present-parts`) must never be accepted.
+
+The repair now applies the only deterministic answer that keeps both the fact and
+the verification: the fact stays as prose, the exactness claim goes, and every
+value that remains backticked is still verified against the evidence.
+Instructing the model differently (0.4.1, 0.4.5) was already shown not to
+converge.
+
+## Privacy and safety
+
+- Logs, warnings and diagnostics keep carrying counters only: the number of
+  retracted spans, never span text, fragments or evidence hashes.
+- The class-only report is observation-only and runs only after a validation
+  failure; it never changes validation or the repair.
+- Validation strictness is preserved for every surviving backticked value. The
+  deliberate trade is that a value the evidence does not carry — including an
+  invented one — is no longer deleted: it stays as prose and in the recorded
+  counter, instead of costing the fact or the whole DS4 compaction. The fallback
+  this replaces (Pi's default compaction) does not check exact values at all.
+- No provider call, network access or configuration change is involved in the
+  repair.
+
+## Compatibility and persistence
+
+- No migrations, no schema change (still 16), no new configuration key, and no
+  change to any provider-facing default: `chars-v1` remains the default
+  estimator, `modelAwareness.autoTune` and DS4 native continuation stay
+  disabled, `storage.scope` keeps its `project` default.
+- The core repair API is renamed as listed above; the engine/core compatibility
+  guard turns a mixed artifact pair into one actionable line instead of a
+  missing function.
+- Fallback still exists for missing, duplicate or empty sections, unsupported
+  file paths, unknown sections or headings, malformed content, transport and
+  budget failures, and `post-downgrade-invalid`.
+
+## Validation
+
+On Node 26.5.1 the release passed `npm run check` (100 Vitest files, 650 tests,
+TypeScript builds and root typecheck), `npm run pack:check` in a clean consumer
+for all three packages at 0.4.8 (251 core files, 7 reference-adapter files, 112
+extension files), deterministic `npm run quality:compare` (candidate `0.9875`
+against the frozen baseline `0.808156`), and
+`npm run schema:context-persistence` (`passed: true`). No provider calls are
+involved in this release procedure. `jev_verify` is not available in this
+environment (project verification disabled), so the checks above were run
+directly.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ds4-context-engine",
-  "version": "0.4.6",
+  "version": "0.4.8",
   "description": "Non-destructive, provider-independent context management for Pi.",
   "type": "module",
   "license": "MIT",
@@ -63,7 +63,7 @@
     ]
   },
   "dependencies": {
-    "ds4-context-core": "0.4.6",
+    "ds4-context-core": "0.4.8",
     "js-tiktoken": "1.0.21"
   },
   "peerDependencies": {

package/src/pi-adapter/summary-generator.ts

@@ -6,11 +6,13 @@ import type {
 } from "@earendil-works/pi-coding-agent";
 import type { CompactionThinkingLevel } from "ds4-context-core/config/config";
 import {
-  analyzeUnsupportedExactValueBullets,
+  analyzeUnsupportedExactValueDowngrade,
   classifyUnsupportedExactValueSpans,
   groundSummaryFileSections,
   validateSummary,
+  type ExactValueDowngradeResult,
   type SummaryValidationInput,
+  type SummaryValidationIssue,
   type SummaryValidationResult,
   type UnsupportedSpanClassReport,
 } from "ds4-context-core/compaction/summary-contract";
@@ -320,45 +322,38 @@ export async function generateValidatedSummary(
           message: "Deterministic validation disabled by configuration",
         }],
       };
-  let exactRepair: ReturnType<typeof analyzeUnsupportedExactValueBullets> | undefined;
-  let exactRepairFailure: "post-prune-invalid" | undefined;
+  let exactDowngrade: ReturnType<typeof analyzeUnsupportedExactValueDowngrade> | undefined;
+  let exactDowngradeFailure: "post-downgrade-invalid" | undefined;
   if (validation.status === "invalid") {
     const errors = validation.issues.filter((issue) => issue.severity === "error");
     const exactOnly = errors.length > 0
       && errors.every((issue) => issue.code === "unsupported-exact-value");
-    exactRepair = exactOnly
-      ? analyzeUnsupportedExactValueBullets(content, validationInput)
+    exactDowngrade = exactOnly
+      ? analyzeUnsupportedExactValueDowngrade(content, validationInput)
       : undefined;
-    const pruned = exactRepair?.result;
-    if (pruned) {
-      const repairedValidation = validateSummary(pruned.content, validationInput);
+    const downgraded = exactDowngrade?.result;
+    if (downgraded) {
+      const repairedValidation = validateSummary(downgraded.content, validationInput);
       if (repairedValidation.status !== "invalid") {
-        content = pruned.content;
+        content = downgraded.content;
         validation = {
           status: "warning",
-          issues: [
-            ...repairedValidation.issues,
-            {
-              code: "unsupported-exact-bullets-pruned",
-              severity: "warning",
-              message: `Removed ${pruned.removedBullets} bullet(s) containing unsupported exact values`,
-            },
-          ],
+          issues: [...repairedValidation.issues, ...exactDowngradeIssues(downgraded)],
         };
       } else {
         validation = repairedValidation;
-        exactRepairFailure = "post-prune-invalid";
+        exactDowngradeFailure = "post-downgrade-invalid";
       }
     }
   }
   if (validation.status === "invalid") {
     const codes = unique(validation.issues.map((issue) => issue.code));
-    const repairDiagnostics = exactRepair
-      ? `; repair=${exactRepairFailure ?? exactRepair.status}; unsupportedSpans=${exactRepair.unsupportedSpans}; affectedBullets=${exactRepair.affectedBullets}`
+    const repairDiagnostics = exactDowngrade
+      ? `; repair=${exactDowngradeFailure ?? exactDowngrade.status}; unsupportedSpans=${exactDowngrade.unsupportedSpans}; affectedBullets=${exactDowngrade.affectedBullets}`
       : "";
     const spanClassReport = validation.issues.some((issue) => issue.code === "unsupported-exact-value")
       ? classifyUnsupportedExactValueSpans(content, validationInput, {
-          ...(exactRepair ? { affectedBullets: exactRepair.affectedBullets } : {}),
+          ...(exactDowngrade ? { affectedBullets: exactDowngrade.affectedBullets } : {}),
         })
       : undefined;
     throw new SummaryValidationError(
@@ -370,6 +365,20 @@ export async function generateValidatedSummary(
   return { content, validation, usage: sumUsage([...retryUsages, response.usage]) };
 }
 
+/**
+ * Record what the exact-value repair did, as a count only: the disputed spans
+ * never reach logs, notifications or diagnostics because they may contain
+ * sensitive source material.
+ */
+function exactDowngradeIssues(result: ExactValueDowngradeResult): SummaryValidationIssue[] {
+  if (result.downgradedSpans === 0) return [];
+  return [{
+    code: "unsupported-exact-spans-unquoted",
+    severity: "warning",
+    message: `Retracted the quoting of ${result.downgradedSpans} exact value(s) the evidence does not carry verbatim`,
+  }];
+}
+
 export function sumUsage(usages: readonly Usage[]): Usage {
   const sum = (read: (usage: Usage) => number): number => usages.reduce((total, usage) => total + read(usage), 0);
   const hasReasoning = usages.some((usage) => usage.reasoning !== undefined);

package/src/pi-adapter/version.ts

@@ -1,4 +1,4 @@
-export const EXTENSION_VERSION = "0.4.6";
+export const EXTENSION_VERSION = "0.4.8";
 export const SUPPORTED_PI_VERSION = "0.84.3";
 export const OBSERVER_PLANNER_VERSION = "observer-model-aware-v1";
 export const PLANNER_VERSION = "managed-learned-ranking-v1";