dsh-github-copilot 0.4.0-alpha.81 → 0.4.0-alpha.82

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/AGENTS.md CHANGED
@@ -240,6 +240,8 @@ Never say GPT-6/search works merely because settings, typecheck or a package imp
240
240
 
241
241
  ## Changing capabilities
242
242
 
243
+ Completed-turn Usage diagnostics (#259) are read-only plugin conversation data and an additive assistant-actions explanation. Official rc.2 hides its total if any attempt lacks complete accounting; the plugin's finish-only pre-dispatch pressure block can trigger this rule even after recovery. Never fabricate zero usage or replace it with successful-step partial totals. Identify local interception only from its exact recorded finish-only diagnostic, keep other missing samples and paged evidence uncertain, and suppress the explanation whenever native `tokenUsage` exists. Preserve native accounting, history, pressure and recovery; see `docs/copilot-usage.md`.
244
+
243
245
  Auto task routing (#258) uses current `model_picker_category` facts, never model
244
246
  names, effort or context capacity as a quality category. Hard eligibility/input
245
247
  fit precede task/preference policy; unknown category and uncertain task evidence
package/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.4.0-alpha.82 (prepared)
4
+
5
+ - Explain missing native Turn Usage on completed Copilot replies through a plugin-owned read-only conversation projection and a compact, keyboard-accessible footer disclosure (#259).
6
+ - Distinguish the exact recorded local pre-dispatch input-budget block, other settlements without usage, and incomplete history. A recovered turn can contain reported successful steps without a provable whole-turn total.
7
+ - Preserve native Usage when complete; do not fabricate zero usage, aggregate partial totals, change history or replace compaction/retry ownership. Record the observed plugin/Core integration gap and its limits.
8
+
3
9
  ## 0.4.0-alpha.81 (prepared)
4
10
 
5
11
  - Route Auto through current supplier Powerful/Versatile/Lightweight categories and contextual task evidence instead of advertised-capacity bands (#258). Preserve hard input/image/exclusion/account admission and native no-fit recovery.
package/README.md CHANGED
@@ -20,6 +20,7 @@ Core still owns image conversion and history. See [image compatibility limits](.
20
20
  - **Search routing:** choose the primary and fallback search providers under **Plugins → dsh-github-copilot → Details**. The page intentionally exposes only those user-facing choices; protocol probes, timeouts, allowlists, and transport switches are not presented as routine UI. It also keeps the rc.2 lifecycle warning visible before disable/remove/upgrade actions. If the updated routed service is not active yet, the card reports **Restart required** instead of presenting a broken form.
21
21
  - **Usage:** eligible Copilot sessions get an optional **Credits** control beside the composer, with provider-reported billing-cycle data and explicit unavailable/stale states. The quota request alone combines Node default and OS trust roots without disabling certificate verification or relying on Desktop launcher environment inheritance.
22
22
  - **Context evidence:** managed requests suppress terminal all-zero usage on failure or cancellation. A separate composer disclosure can identify historical failed-zero readings and show the last applicable input sample, including cache. This is not current occupancy, does not replace the native `0%` meter, and does not rewrite history. See [context evidence boundaries](./docs/copilot-usage.md#historical-context-evidence).
23
+ - **Missing Turn Usage:** a completed Copilot reply without a native total can show **Turn Usage unavailable**. Its read-only explanation distinguishes recorded local pre-dispatch budget blocks, other missing samples and incomplete history; it never invents zero usage or a partial turn total. [Observation and boundaries](./docs/copilot-usage.md#missing-completed-turn-usage).
23
24
  - **Compatibility:** the plugin applies Copilot-only tool-schema, reasoning-presentation, request-budget, and account-model compatibility through published DSH APIs. It does not patch Core or maintain a second model catalog.
24
25
 
25
26
  ![Current Web search provider routing on the plugin details page](./docs/images/copilot-search-routing.png)
@@ -108,7 +109,7 @@ The Host reads GitHub's internal quota endpoint using the existing canonical OAu
108
109
 
109
110
  ## Install and sign in
110
111
 
111
- The commands below target the package version `0.4.0-alpha.81`. Versioned URLs describe the intended release artifacts, not proof that publication or local activation has completed; use them only once that Release and its checksums are available. Install into the profile you use (replace `web` when targeting another profile):
112
+ The commands below target the package version `0.4.0-alpha.82`. Versioned URLs describe the intended release artifacts, not proof that publication or local activation has completed; use them only once that Release and its checksums are available. Install into the profile you use (replace `web` when targeting another profile):
112
113
 
113
114
  Before installing/updating, unpack the **checksum-verified** archive into a temporary directory and run its read-only composition preflight (replace all paths with absolute paths for the intended profile):
114
115
 
@@ -121,10 +122,10 @@ Include any launcher patch files with repeated `--patch /absolute/file` argument
121
122
  For a standalone named profile only, the supported CLI command is:
122
123
 
123
124
  ```sh
124
- dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.81/dsh-github-copilot-0.4.0-alpha.81.tgz
125
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.82/dsh-github-copilot-0.4.0-alpha.82.tgz
125
126
  ```
126
127
 
127
- For Desktop profiles, use Desktop's native package manager with `dsh-github-copilot@0.4.0-alpha.81` after the same preflight and only when registry access is permitted. Desktop reserves its `desktop` profile from CLI management. If registry access is blocked or unavailable, stop; the documented [controlled offline CLI procedure](./docs/npm-distribution.md#controlled-offline-cli-maintenance-for-standalone-profiles) is not a Desktop workaround.
128
+ For Desktop profiles, use Desktop's native package manager with `dsh-github-copilot@0.4.0-alpha.82` after the same preflight and only when registry access is permitted. Desktop reserves its `desktop` profile from CLI management. If registry access is blocked or unavailable, stop; the documented [controlled offline CLI procedure](./docs/npm-distribution.md#controlled-offline-cli-maintenance-for-standalone-profiles) is not a Desktop workaround.
128
129
 
129
130
  Then open the Models UI listed above, find **GitHub Copilot**, select **Sign in**, and complete the GitHub device-code flow. Plugin installation changes the selected profile; activation follows that profile's normal reload/restart policy.
130
131
 
@@ -183,7 +184,7 @@ Agents should treat the browser authorization as a human handoff, not as a token
183
184
  5. Confirm **Signed in** and inspect the automatic discovery result before asking the user to choose a model. Already-signed-in Models opening ensures missing/stale metadata automatically; fresh ready cache makes no request. Use visible **Retry** for errors or **Manage → Refresh models** for an intentional forced update, not routine setup. Status alone does not discover, and login, metadata and successful model calls remain separate evidence.
184
185
  6. Use **Sign out** only when the user explicitly asks to disconnect the account. It deletes the Copilot credential record but preserves route settings.
185
186
 
186
- GitHub Releases and npm are the default distribution channels for each new version, using the same verified tarball. Pin the version and verify the evidence for the channel used: Release `SHA256SUMS`, and npm `dist.integrity` when installing from npm. Install into Desktop profiles only through Desktop's native package manager; the reserved `desktop` profile is not managed by the DSH CLI. After npm publication is verified, the native manager accepts `dsh-github-copilot@0.4.0-alpha.81`, not a URL or file. Controlled offline CLI maintenance is documented for standalone named profiles only, never Desktop-managed profiles. Follow the mandatory search-composition preflight, backup, single-writer and post-install checks; do not bypass a corporate registry ban, disable TLS verification or restart without separate approval. See [distribution and publication requirements](./docs/npm-distribution.md).
187
+ GitHub Releases and npm are the default distribution channels for each new version, using the same verified tarball. Pin the version and verify the evidence for the channel used: Release `SHA256SUMS`, and npm `dist.integrity` when installing from npm. Install into Desktop profiles only through Desktop's native package manager; the reserved `desktop` profile is not managed by the DSH CLI. After npm publication is verified, the native manager accepts `dsh-github-copilot@0.4.0-alpha.82`, not a URL or file. Controlled offline CLI maintenance is documented for standalone named profiles only, never Desktop-managed profiles. Follow the mandatory search-composition preflight, backup, single-writer and post-install checks; do not bypass a corporate registry ban, disable TLS verification or restart without separate approval. See [distribution and publication requirements](./docs/npm-distribution.md).
187
188
 
188
189
  **Desktop package-update and Web-lifecycle boundaries:** the native manager's `restart-required` result for an in-place installed-package upgrade is authoritative and distinct from plugin-bundle removal/re-add behavior. Any disable, removal, or upgrade involving service recomposition (`cordis.patch.yml`, such as the isolated routed web search layer) may leave dependent entries pending until Desktop is fully exited and cold-restarted. If the native manager reports only entries such as `pending (waiting for service: web)` while this plugin already shows **Off**, the requested disabled state has been persisted; cold-restart Desktop instead of repeatedly toggling or reinstalling the plugin. Other errors are not covered by this guidance and must still be investigated.
189
190
 
@@ -465,8 +466,8 @@ Report the published Release URL, version, tag/commit and verified asset SHA-256
465
466
  `package.json` declares public npm distribution. A release tag must equal `v${package.json.version}`. Versions use standard SemVer prerelease labels (`alpha`, `beta`, or `rc`), each with its matching npm dist-tag; only stable versions use `latest`. The Release workflow performs the frozen install and complete verification gate, packs once (or recovers the original archive on retry), verifies `SHA256SUMS`, publishes the immutable GitHub Release and then publishes those same bytes to npm through OIDC. Either channel failing means delivery is incomplete. First package creation needs an authorized maintainer; staging requires an existing package and is not a first-package bootstrap. Historical releases are not republished.
466
467
 
467
468
  ```sh
468
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.81/dsh-github-copilot-0.4.0-alpha.81.tgz
469
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.81/SHA256SUMS
469
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.82/dsh-github-copilot-0.4.0-alpha.82.tgz
470
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.82/SHA256SUMS
470
471
  sha256sum --check SHA256SUMS
471
472
  ```
472
473
 
@@ -474,7 +475,7 @@ PowerShell can verify the same two downloaded files with:
474
475
 
475
476
  ```powershell
476
477
  $expected = (Get-Content .\SHA256SUMS).Split()[0]
477
- $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.81.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
478
+ $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.82.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
478
479
  if ($actual -cne $expected) { throw 'Release checksum mismatch' }
479
480
  ```
480
481
 
package/README.zh.md CHANGED
@@ -20,13 +20,14 @@ Core 管理。详见[图片兼容性与限制](./docs/image-input-compatibility.
20
20
  - **搜索路由:**在 **插件 → dsh-github-copilot → 详情**选择主搜索 Provider 与兜底 Provider。页面只保留用户真正需要的两项选择,不再把协议探测、超时、白名单或传输开关作为日常配置暴露;同时会在停用/移除/升级前常驻显示 rc.2 生命周期提示。更新后的路由服务尚未激活时,卡片会明确显示 **需要重启生效(Restart required)**,而不是继续展示无法使用的表单。
21
21
  - **用量:**符合条件的 Copilot 会话会在输入框旁显示可选的 **Credits / 额度** 控件,展示供应方明确返回的计费周期数据,并如实区分不可用与历史快照。仅额度请求组合 Node 默认证书与系统信任根,无需依赖 Desktop launcher 的环境变量继承,且保持 TLS 验签。
22
22
  - **上下文证据:**托管请求失败或取消时,不再传递终止前的全零用量。独立的输入框提示可识别历史失败零值,并显示仍适用的最后输入采样(含缓存);它不是当前占用率,不替换原生 `0%` 表盘,也不改写历史。详见[上下文证据边界](./docs/copilot-usage.md#historical-context-evidence)。
23
+ - **整轮 Usage 缺失:**已完成的 Copilot 回复没有原生总量时,可显示**本轮 Usage 不可用**。只读说明区分已记录的插件发出前预算拦截、其他缺失采样和不完整历史;不会补造零用量或把部分步骤合计当成整轮总量。详见[观察与边界](./docs/copilot-usage.md#missing-completed-turn-usage)。
23
24
  - **兼容处理:**插件通过 DSH 已发布公开接口提供 Copilot 专用 Tool Schema、Thinking 展示、请求预算及账号模型兼容,不修改 Core,也不维护第二套模型目录。
24
25
 
25
26
  ![当前插件详情页的 Web 搜索 Provider 路由](./docs/images/copilot-search-routing.png)
26
27
 
27
28
  截图来自当前构建 Client 的隔离浏览器 fixture,使用合成 Provider。它只证明已发布配置界面的形态,不证明真实凭据、账号权限、搜索成功或当前 Desktop 已加载。
28
29
 
29
- > 当前文档与安装命令对应版本 `0.4.0-alpha.81`。源码、发布制品、已安装版本和实际加载运行时需分别确认;本地升级和中断会话的重启仍需用户批准。
30
+ > 当前文档与安装命令对应版本 `0.4.0-alpha.82`。源码、发布制品、已安装版本和实际加载运行时需分别确认;本地升级和中断会话的重启仍需用户批准。
30
31
 
31
32
  Web search 路由现在优先显示在插件详情页;宿主不支持详情页插槽时才回退到 **设置 → 模型**或独立 Web search section。搜索子 Fiber 仍独立等待 Remote,不影响账号控件和既有搜索安全检查。
32
33
 
@@ -123,10 +124,10 @@ node package/scripts/check-search-composition.mjs --profile-dir /absolute/profil
123
124
  仅对独立的具名 profile,获准且网络可用时,可通过受支持的 CLI 命令安装:
124
125
 
125
126
  ```sh
126
- dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.81/dsh-github-copilot-0.4.0-alpha.81.tgz
127
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.82/dsh-github-copilot-0.4.0-alpha.82.tgz
127
128
  ```
128
129
 
129
- Desktop profile 请在完成同样的预检后,使用 Desktop 原生包管理器安装 `dsh-github-copilot@0.4.0-alpha.81`。Desktop 保留 `desktop` profile,CLI 不负责管理。若 registry 被公司封禁或不可用,不要更换网络绕行或使用离线 CLI;请停止。[受控离线 CLI 流程](./docs/npm-distribution.md#controlled-offline-cli-maintenance-for-standalone-profiles)仅适用于独立具名 profile,不适用于 Desktop。
130
+ Desktop profile 请在完成同样的预检后,使用 Desktop 原生包管理器安装 `dsh-github-copilot@0.4.0-alpha.82`。Desktop 保留 `desktop` profile,CLI 不负责管理。若 registry 被公司封禁或不可用,不要更换网络绕行或使用离线 CLI;请停止。[受控离线 CLI 流程](./docs/npm-distribution.md#controlled-offline-cli-maintenance-for-standalone-profiles)仅适用于独立具名 profile,不适用于 Desktop。
130
131
 
131
132
  随后打开上表对应的 Models UI,找到 **GitHub Copilot**,点击 **Sign in** 并完成 GitHub device-code 流程。安装会修改指定 profile;是否立即激活取决于该 profile 的常规 reload/restart 策略。
132
133
 
@@ -185,7 +186,7 @@ Agent 应把浏览器授权视为需要用户完成的 handoff,而不是自行
185
186
  5. 确认 **Signed in** 并检查自动发现结果,再请用户选择模型。已登录时打开 Models 会自动确保缺失/过期元数据,新鲜 ready 缓存不发请求。错误可使用 **Retry**,有意强制更新时使用 **Manage → Refresh models**,不作为常规设置步骤。状态读取本身不发现;登录、元数据与真实调用成功是独立证据。
186
187
  6. 只有用户明确要求断开账号时才使用 **Sign out**;它会删除 Copilot credential record,但保留 route settings。
187
188
 
188
- 每个新版本默认同时分发到 GitHub Releases 和 npm,两个渠道使用同一份已验证 tarball。应固定版本并核对所用渠道的证据:Release 的 `SHA256SUMS`;从 npm 安装时另核对 `dist.integrity`。Desktop profile 只能通过原生 Desktop 包管理器安装;获准且 registry 可用时输入 `dsh-github-copilot@0.4.0-alpha.81`,不是 URL 或本地文件。Desktop 保留 `desktop` profile,不能通过 DSH CLI 管理。受控离线 CLI 维护仅适用于独立具名 profile,不得作为 Desktop 安装绕行方案。[双渠道发布与 OIDC 要求](./docs/npm-distribution.md)保持不变。
189
+ 每个新版本默认同时分发到 GitHub Releases 和 npm,两个渠道使用同一份已验证 tarball。应固定版本并核对所用渠道的证据:Release 的 `SHA256SUMS`;从 npm 安装时另核对 `dist.integrity`。Desktop profile 只能通过原生 Desktop 包管理器安装;获准且 registry 可用时输入 `dsh-github-copilot@0.4.0-alpha.82`,不是 URL 或本地文件。Desktop 保留 `desktop` profile,不能通过 DSH CLI 管理。受控离线 CLI 维护仅适用于独立具名 profile,不得作为 Desktop 安装绕行方案。[双渠道发布与 OIDC 要求](./docs/npm-distribution.md)保持不变。
189
190
 
190
191
  **Desktop package 更新与 Web 生命周期边界:**原生 manager 对已安装 package 原位升级返回的 `restart-required` 是权威结果,与移除/重加 plugin bundle 的行为是两个不同问题。涉及服务重编排补丁(`cordis.patch.yml`,如本插件所采用的隔离路由 Web 搜索层)的停用、移除或升级,可能让依赖条目保持 pending,直到完全退出并冷重启 Desktop。若原生 manager 只报告类似 `pending (waiting for service: web)` 的条目,同时本插件已经显示 **Off**,说明请求的停用状态已经落盘;请冷重启 Desktop,不要反复切换或重装插件。其它错误不属于此提示范围,仍需单独排查。
191
192
 
@@ -476,8 +477,8 @@ node scripts/agent.mjs attribution "DeepSeek Harness (DSH)"
476
477
  `package.json` 声明公开 npm 分发。Release tag 必须严格等于 `v${package.json.version}`。预发布使用 `alpha`、`beta` 或 `rc` 及对应 npm dist-tag,只有稳定版使用 `latest`。Release workflow 执行 frozen install 和完整门禁,只打包一次(重试恢复原始归档),验证 `SHA256SUMS`,发布不可变 GitHub Release,再通过 OIDC 将同一份字节发布到 npm。任一渠道失败都表示交付未完成。首次建包须由获准环境中的维护者完成;staging 要求包已存在,不能代替首次建包。不会批量补发历史版本。
477
478
 
478
479
  ```sh
479
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.81/dsh-github-copilot-0.4.0-alpha.81.tgz
480
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.81/SHA256SUMS
480
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.82/dsh-github-copilot-0.4.0-alpha.82.tgz
481
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.82/SHA256SUMS
481
482
  sha256sum --check SHA256SUMS
482
483
  ```
483
484
 
@@ -485,7 +486,7 @@ PowerShell 可以对已下载的同一组文件执行:
485
486
 
486
487
  ```powershell
487
488
  $expected = (Get-Content .\SHA256SUMS).Split()[0]
488
- $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.81.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
489
+ $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.82.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
489
490
  if ($actual -cne $expected) { throw 'Release checksum mismatch' }
490
491
  ```
491
492
 
@@ -8,7 +8,7 @@
8
8
  },
9
9
  "package": {
10
10
  "name": "dsh-github-copilot",
11
- "version": "0.4.0-alpha.81"
11
+ "version": "0.4.0-alpha.82"
12
12
  },
13
13
  "evidence": {
14
14
  "kind": "source-and-synthetic-test-inventory",
@@ -288,6 +288,25 @@
288
288
  ]
289
289
  },
290
290
  "capabilities": [
291
+ {
292
+ "id": "missing-turn-usage-explanation",
293
+ "required": true,
294
+ "sourceMarkers": [
295
+ {"file": "src/turn-usage-evidence.ts", "marker": "github-copilot-turn-usage-evidence"},
296
+ {"file": "src/turn-usage-evidence.ts", "marker": "tail.tokenUsage !== undefined"},
297
+ {"file": "src/turn-usage-notice.ts", "marker": "Turn Usage unavailable"},
298
+ {"file": "src/auto-model-presentation.ts", "marker": "turnUsageEvidenceDefinition"},
299
+ {"file": "scripts/verify-tagged-core.mjs", "marker": "tests/fixtures/turn-usage-core.fixture.ts"}
300
+ ],
301
+ "tests": [
302
+ {"file": "tests/turn-usage-evidence.spec.ts", "name": "explains a recovered local block alongside reported successful steps without summing tokens"},
303
+ {"file": "tests/turn-usage-evidence.spec.ts", "name": "does not label generic overflow, provider errors or ambiguous streams as pre-dispatch"},
304
+ {"file": "tests/turn-usage-notice.spec.ts", "name": "keeps the fixed-height footer compact and opens a bounded nonmodal explanation"},
305
+ {"file": "tests/turn-usage-integration.spec.ts", "name": "explains native missing usage even when the independent selection Remote fails"},
306
+ {"file": "tests/fixtures/turn-usage-core.fixture.ts", "name": "reproduces the finish-only local block and explains it without changing native accounting"},
307
+ {"file": "tests/fixtures/reasoning-presentation-core.fixture.ts", "name": "explains missing turn Usage through native assembly and scoped actions (%s)"}
308
+ ]
309
+ },
291
310
  {
292
311
  "id": "historical-context-evidence",
293
312
  "required": true,
@@ -30,6 +30,24 @@ An additive composer disclosure identifies missing or unreliable context evidenc
30
30
 
31
31
  Local synthetic tests establish guarded-stream, historical-fold and presentation behavior only. Exact published-adapter and public-registry acceptance, complete CI, publication and loaded Desktop state must be verified separately. No live provider call or Session restart is needed for these tests.
32
32
 
33
+ ## Missing completed-turn Usage
34
+
35
+ ### Observed plugin/Core integration gap (#259)
36
+
37
+ One observed completed turn contained 57 successful assistant messages with reported usage and one failed `assistant/attempt` without a usage sample. That attempt recorded the plugin's exact local estimated-input-budget diagnostic: 796299 estimated tokens exceeded a 781113-token input budget, before provider dispatch. Native compaction recovered and the subsequent steps completed. No conversation content, credentials or opaque replay is needed to explain this observation; the exact loaded plugin bytes were not independently attested.
38
+
39
+ Official rc.2 `deriveTurnTokenUsage` requires complete lifecycle and exact usage for every attempt. One attempt without a sample makes its whole-turn result unavailable, so `TurnTailNodeView` omits native Usage. This is Core's existing fail-closed accounting rule triggered by our preventive pressure path, not evidence that all requests had no usage and not a regression in single-model exclusion saves.
40
+
41
+ ### Plugin-local explanation
42
+
43
+ A plugin-owned public conversation definition retains only bounded counts of settlements without reported samples and finish-only attempts with the exact recorded local diagnostic. On a completed Copilot reply whose native tail has no `tokenUsage`, the additive assistant-actions control opens **Turn Usage unavailable**. It uses the incumbent nonmodal popover pattern rather than expanding the native fixed-height footer.
44
+
45
+ The explanation distinguishes recorded local budget blocks, other settlements without samples, and missing turn-start/projection evidence. Generic provider overflow is never labeled pre-dispatch. Invalid reported samples and missing lifecycle boundaries can also make native accounting unavailable; if no cause is established, the explanation remains unknown rather than reimplementing the native validator. Projection and selection Remote failures remain independent, with named diagnostics; Retry only rereads selection evidence, never inference or accounting.
46
+
47
+ The control is historical evidence, not current context occupancy, account credits, dispatch attestation or a supplier receipt. It adds no token sum or fabricated zero usage, changes no native projection key, reads no opaque replay, and rewrites no history. Native complete Usage suppresses the explanation. Ordinary pressure protection, compaction transactions, errors, cancellation and retry remain unchanged. Removing the plugin removes the explanation without a data migration.
48
+
49
+ Synthetic unit/UI tests and exact unchanged Core accounting/registry fixtures prove these boundaries, not live provider receipts or loaded Desktop behavior. A native representation for unbilled pre-dispatch attempts may eventually remove the gap, but would require a separately requested upstream scope; it is not a prerequisite for this plugin-local explanation. Retire the companion diagnostic when native public presentation communicates the same uncertainty and the supported-version acceptance is verified.
50
+
33
51
  ## Account data boundary
34
52
 
35
53
  The Host uses the existing `llm-pi-ai/github-copilot` OAuth grant through public credential APIs. GitHub's `copilot_internal/user` endpoint uses the GitHub grant, not a second sign-in or a newly pasted token. Access-token renewal remains owned by pi-ai; quota inspection must not introduce a refresh implementation or credential persistence.