dsh-github-copilot 0.4.0-alpha.88 → 0.4.0-alpha.92

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.
@@ -28,6 +28,14 @@ The pinned SDK already has its own context-dependent output clamp. This plugin p
28
28
 
29
29
  ## Earlier pressure and transaction ownership
30
30
 
31
+ For [#280](https://github.com/cloga/dsh-github-copilot/issues/280), a public `agent/pre-step` listener additionally prevents known continuing-step pressure before Core appends `step/start`. It awaits downstream decisions, delegates rejection/cancellation, and requires a committed plugin-owned managed route, no model-selection notice, and a readable native `modelSelection` projection with `pending: null`. First steps and unknown/pending selections delegate: a prior request header is not proof of the next selected route.
32
+
33
+ The account callback supplies only a current capacity threshold; an empty message array used for this lookup is not an input estimate. The public native token meter measures the existing surface. Above that threshold, the initiating Agent's currently bound engine runs one `compactIfNeeded(agent, 'context-overflow', signal)` transaction, respecting disabled auto and the effective zero/invalid overflow policy. Native failures and cancellation propagate before model-attempt admission; a null/no-progress result delegates to the retained final protections. The next native request is built from the replacement surface. No retry counter, history, usage sample or selected model is rewritten.
34
+
35
+ This is **partial prevention**, not general accounting repair. In the unchanged rc.2 synthetic AgentLoop fixture, the existing post-start pressure refusal creates an unsampled attempt and the strict native turn aggregate is unavailable, even after successful recovery. With pre-step reduction, the same two real model steps retain their complete native total without that attempt. Native turn-tail matches events by their recorded turn; compaction replacements for an earlier turn are not samples of the current turn. No samples are suppressed to produce the total.
36
+
37
+ Cold/first-step routes, pending model changes, later system/tool-prefix growth, unavailable evidence, indivisible oversized units and final converted hard-admission errors can still produce missing native turn Usage. Already-recorded totals remain unchanged. The plugin does not fabricate zero usage, display partial sums as full totals, or reinterpret transport failures as compaction pressure.
38
+
31
39
  The public `llm/stream` listener sees a committed, frozen loop request. It requires:
32
40
 
33
41
  - The exact plugin-owned managed route and an ordinary marked agent-loop call, not an auxiliary purpose.
@@ -86,15 +86,13 @@ The internal client observes per-turn `copilot_usage.total_nano_aiu`, but existe
86
86
 
87
87
  Synthetic tests cover parsing, lifecycle, failure states, strict transport and UI. They do not establish production quota permissions, billing latency, live OAuth/model transport, installed Desktop bytes or loaded plugin state. No real account calls are made merely to generate test evidence.
88
88
 
89
- ## Session selector correction (alpha.33)
89
+ ## Current Session and responsive presentation
90
90
 
91
- Alpha.32 called `useSession()` without the selector required by the public Core hook. A registration can therefore exist while the Slot renderer has retired its crashed entry; installed-version receipts and signed-out absence tests are not proof that the control renders in an eligible Session.
92
-
93
- The correction consumes the existing `useSession(selector)` contract and selects only a boolean for the current, open, non-removed Session. It does not introduce a compatibility shim, copy Session data, patch Core, substitute model selection, or alter quota requests. The exact official alpha.1/alpha.2 contract is `SnapshotSelectorHook<T>` in `packages/client/store/src/contract.ts`, with the `bindSnapshotSelector` implementation in `packages/client/ui-renderer/src/client/bind.ts`. Model projection remains the public `useProjection('modelSelection')` reader, whose key-only overload is supported.
94
-
95
- Validation must include positive rendering with actual selector-hook behavior for both canonical and managed Copilot routes, reactive provider/Session changes and disposal. A null/hidden signed-out surface alone is insufficient. Synthetic quota results prove rendering and lifecycle only, not live account permissions or balances. Current-runtime activation must be checked separately after an explicitly authorized upgrade; reloading alpha.32 does not fix its source call.
96
-
97
- ## Responsive statistics presentation (alpha.35)
91
+ The control uses public `useSession(selector)` for only the current open,
92
+ non-removed Session, with public `useProjection('modelSelection')`. Acceptance
93
+ must include positive rendering on canonical and managed routes, reactive
94
+ provider/Session changes and disposal. A registered or hidden signed-out entry
95
+ alone proves neither rendering nor live account permission.
98
96
 
99
97
  The unavailable Session credits section is omitted rather than permanently displaying a placeholder. Reset metadata is optional and independent from validated quota amounts: missing, malformed, zero or elapsed values are ignored. Select a supplier-reported next reset later than the snapshot observation, preferring the snapshot timestamp before valid UTC account, account or limited-user dates; never invent the next billing date. Invalid optional date metadata does not discard otherwise valid account amounts. The Client also hides reset rows without a known observation time or a later reset.
100
98
 
@@ -102,7 +100,7 @@ The compact control uses the native secondary font-size and line-height tokens,
102
100
 
103
101
  The host owns placement of the existing public dock entries. On a shared-row host, the usage entry follows the native statistics group and can appear immediately after Cache hit; on an older stacked host, it retains that host's placement. The plugin neither relocates native DOM nor overrides native statistics styles, and it does not require a modified Core to activate. A separately authorized Desktop Client layout task owns wrapping and actual assembled native-statistics geometry checks.
104
102
 
105
- Official `0.1.6-alpha.2` already provides the shared dock row in [`InputBar.module.css`](https://github.com/deepseek-ai/deepseek-harness/blob/ddefc45fbc7f8e46dd73185e68295696d1297887/packages/client/ui-conversation/src/client/skeleton/InputBar.module.css) and an intrinsic native statistics group in [`StatsPills.module.css`](https://github.com/deepseek-ai/deepseek-harness/blob/ddefc45fbc7f8e46dd73185e68295696d1297887/packages/client/ui-chat/src/client/chat/StatsPills.module.css). Reuse that official presentation primitive rather than inventing another statistics Slot or copying its token calculations. Wide/narrow layout and popup acceptance must use actual native components alongside the released Client; standalone plugin tests or a synthetic sibling label are not proof of native Cache hit alignment.
103
+ Official rc.2 retains the shared dock row in [`InputBar.module.css`](https://github.com/deepseek-ai/deepseek-harness/blob/639ed015397290b3745d163aafe02ffee4aa3f84/packages/client/ui-conversation/src/client/skeleton/InputBar.module.css) and intrinsic native statistics group in [`StatsPills.module.css`](https://github.com/deepseek-ai/deepseek-harness/blob/639ed015397290b3745d163aafe02ffee4aa3f84/packages/client/ui-chat/src/client/chat/StatsPills.module.css). Reuse that official presentation primitive rather than inventing another statistics Slot or copying its token calculations. Wide/narrow layout and popup acceptance must use actual native components alongside the released Client; standalone plugin tests or a synthetic sibling label are not proof of native Cache hit alignment.
106
104
 
107
105
  ## Official-first retirement
108
106
 
@@ -1,52 +1,66 @@
1
1
  # Retired Copilot model roles
2
2
 
3
- Issue [#158](https://github.com/cloga/dsh-github-copilot/issues/158) retires the planner/executor experience introduced in [#127](https://github.com/cloga/dsh-github-copilot/issues/127). This is a plugin-only removal, not a Core upgrade or a claim that the running Desktop has changed.
4
-
5
- ## Ordinary Sessions instead of dedicated roles
6
-
7
- The alpha.34 candidate removes the Models-page **Model roles** card, the older **Copilot · Model roles** Settings fallback, both role selectors and the dedicated-session creation action. There is no replacement planner/executor page. Account sign-in, model discovery, ordinary model selection, search routing and the usage control retain their existing owners.
8
-
9
- Use ordinary Sessions and native subagents. Automatic parent-model → child-model rules and their native Subagent settings editor are separate work in [Core PR #95](https://github.com/cloga/deepseek-harness/pull/95), not yet delivered by this plugin. The removal does not require that PR to merge, does not enable its feature on an older Core, and does not alter native model-selection permission settings.
10
-
11
- ## Existing histories remain compatible
12
-
13
- - Saved `github-copilot-dual-model` configuration is left intact but no longer writable through the legacy role Remote. No settings migration or namespace deletion runs on mount.
14
- - Existing dedicated roots and children retain their captured policy, Session history and model routes. Ordinary Sessions are never enrolled. No conversion, replay of work, automatic replacement or silent model substitution occurs.
15
- - The retained Host projection, route guards and scoped tools exist only for these historical policies. A historical planner can still continue its workflow through `copilot_execute`; that is compatibility for an existing root, not an entry point for creating a new dedicated root.
16
- - Policy restrictions are workflow controls, not a malicious-code sandbox. Core sandbox/approval ownership remains unchanged. The plugin must remain mounted to enforce those policies; uninstalling it is not a supported migration to ordinary Sessions.
17
- - Do not change a dedicated role with the ordinary picker: a mismatched route remains `DUAL_MODEL_SELECTION_LOCKED`. Start an ordinary Session for new work rather than creating another dedicated root or editing history to remove its policy.
18
-
19
- ## Legacy Remotes and uncertain requests
20
-
21
- The three strict legacy descriptors retain their identities and wire shapes so stale clients fail explicitly rather than invoking a missing or different endpoint:
22
-
23
- - `view()` reports `supported: false`, `writable: false`, and `DUAL_MODEL_RETIRED`, with retained configuration/revision and empty model/workspace choices. It performs no account discovery.
24
- - `save()` validates its input and rejects with `DUAL_MODEL_RETIRED`; it does not write settings.
25
- - `create()` validates its input and is recovery-only. The original request UUID, workspace and revision must match an already-created root's durable policy. A new request cannot create a root. Conflicting or uncertain evidence is not treated as absence or permission to retry with a new UUID.
26
-
27
- An already-created matching request can recover its original Session identity and complete the existing workspace attachment. Recovery is not a new root, settings write or automatic browser replay. Inspect the Session list for historical work; no role UI is retained solely to initiate fresh requests.
28
-
29
- ## Alpha.25 descriptor and Remote compatibility
30
-
31
- The retained policy projection admits native `subagent/descriptor` **v3**, already v3 in rc.1. The earlier v1 expectation was a plugin bug, not an upstream history-format migration. Projection `stateVersion: 2` forces refolding, not conversion. Unknown/v1/v2, malformed or conflicting descriptors remain fail-closed and unmodified. Never relabel descriptors or fabricate policy provenance.
32
-
33
- Strict Remote `create()` codec factories and the legacy `schema` bridge use the same parser; this is not a `src-json` downgrade. Account authorization, migration, search and usage contracts are unchanged. The [official-first decision record](./official-first-016-alpha2.md) separates historical compatibility from the now-retired product requirement. The old role screenshots/provenance retained in `docs/images` are historical artifacts, not a current settings guide.
34
-
35
- ## Verification boundaries
36
-
37
- - Client registration regressions must prove the role dependency and both slot entries are absent while account/search/usage registrations and cleanup remain.
38
- - Host and real Gateway regressions cover retired read-only view, rejected saves/new roots, strict input validation and original-request recovery. Historical policy fixtures retain restoration, native-child admission and route/tool controls.
39
- - Package smoke must reject an exported `DualModelCard` while retaining strict compatibility Remotes.
40
- - Required Windows/Linux and exact-Core compatibility CI remains mandatory. Source assertions, isolated mocks or a successful build alone do not prove installed Desktop behavior or a real model call.
41
-
42
- This task requests a PR only. Prepared version metadata is not publication. Do not install or restart a running DSH to verify this removal without separate authorization.
3
+ Compatibility guide for existing planner/executor histories. **Model roles**
4
+ and dedicated-root creation are retired; they are not current setup features.
5
+ Use ordinary Sessions and native subagents for new work. The separate
6
+ [Follow parent model](./parent-model-follow.md) policy supports ordinary children
7
+ without restoring role UI or depending on upstream native rules/settings UI.
8
+
9
+ ## Existing histories
10
+
11
+ - Saved `github-copilot-dual-model` settings stay intact but are not writable
12
+ through the retired role Remote. No migration/deletion runs on activation.
13
+ - Existing dedicated roots/children retain captured policy, routes and history.
14
+ Their `copilot_execute` tool is compatibility for existing work, not a way to
15
+ create new roots or enroll ordinary Sessions.
16
+ - Policy restrictions are workflow controls, not a shell-code sandbox.
17
+ Uninstalling the plugin is not a supported conversion to ordinary Sessions.
18
+ - Do not use the ordinary picker to change a dedicated role:
19
+ `DUAL_MODEL_SELECTION_LOCKED` remains. Start an ordinary Session rather than
20
+ stripping policy from history, replaying work or substituting another model.
21
+
22
+ ## Legacy Remotes
23
+
24
+ Three strict descriptors retain their identities:
25
+
26
+ | Method | Current behavior |
27
+ |---|---|
28
+ | `view()` | Read-only `supported: false`, `writable: false`, `DUAL_MODEL_RETIRED`; no account discovery |
29
+ | `save()` | Validates input, then rejects `DUAL_MODEL_RETIRED`; no write |
30
+ | `create()` | Recovers only an already-created root matching original UUID, workspace and revision |
31
+
32
+ Conflicting/uncertain recovery is not evidence of absence or permission to
33
+ retry with another UUID. Exact recovery can complete the original attachment;
34
+ it creates no new root and is not automatic browser replay.
35
+
36
+ Native `subagent/descriptor` v3 is required; the old v1 assumption was a plugin
37
+ bug, not a history migration. Projection `stateVersion: 2` refolds without
38
+ conversion. Unknown/v1/v2, invalid or conflicting descriptors fail closed.
39
+ Never relabel them or fabricate policy provenance. Strict `create()` codec
40
+ factories and the retained `schema` bridge use the same parser.
41
+
42
+ ## Evidence and historical material
43
+
44
+ Client tests prove removed role dependencies/slots alongside preserved account,
45
+ search and usage cleanup. Host/Gateway fixtures prove rejected new roots/writes,
46
+ original-request recovery and historical policy restoration. Synthetic tests
47
+ do not prove a particular Desktop's loaded state or live inference.
48
+
49
+ The [retirement issue](https://github.com/cloga/dsh-github-copilot/issues/158),
50
+ [original design](https://github.com/cloga/dsh-github-copilot/issues/127) and
51
+ [historical official-first review](./official-first-016-alpha2.md) retain context.
52
+ Old role images/provenance under `docs/images` are historical artifacts, not
53
+ current screenshots or installation instructions.
43
54
 
44
55
  ## 中文摘要
45
56
 
46
- alpha.34 candidate 移除「模型分工」、旧版设置回退入口、规划/执行选择器和新建专用双模型会话按钮。普通 Session 与原生 subagent 是今后的使用方式;父模型到子模型的自动映射及原生 UI 属于另一个仍待交付的 Core PR #95,本插件不会重复实现,也不会假装旧 Core 已支持。
47
-
48
- 已有专用会话保留历史、固定策略和模型路由,继续由兼容 Host 支持;旧设置不删除、不迁移,普通 Session 不会被自动加入旧流程。已有专用根会话中的执行工具可以继续工作,但不能再通过旧入口新建专用根会话。
49
-
50
- 旧 Remote 的 view 明确报告已退役且只读,不发现模型;save 拒绝写入;create 只允许凭完全匹配的旧请求身份恢复已创建会话,不创建新根。冲突或未知结果仍保守处理,不通过换 UUID 绕过。不要编辑历史、自动换模型或将插件卸载当作会话迁移。
57
+ 模型分工与新建专用根会话已退役;新工作使用普通 Session。独立的父模型跟随
58
+ 开关不恢复旧角色界面,也不依赖上游原生规则 UI。已有专用历史、固定策略和
59
+ 旧设置原样保留;旧 Remote 只读/拒绝保存,仅允许凭完全匹配原请求恢复已有根。
60
+ 不转换历史、不静默换模型、不用新 UUID 绕过未知恢复,也不将卸载当作迁移。
61
+ 发布、安装、加载和真实模型调用须分别验证。
62
+ ## Alpha.25 descriptor and Remote compatibility
51
63
 
52
- 本次仅提交 PR,版本号为仓库检查预备;发布、安装、生效和真实模型调用均需分别验证,不重启当前 DSH。
64
+ Retained native child compatibility uses descriptor v3 and strict Remote codecs.
65
+ Unknown/v1/v2 or invalid child descriptors fail closed without relabeling.
66
+ Projection `stateVersion: 2` refolds evidence; it does not convert history.
@@ -1,93 +1,64 @@
1
- # Image input compatibility investigation and implementation
1
+ # Image input compatibility
2
2
 
3
- Tracking: [#236](https://github.com/cloga/dsh-github-copilot/issues/236).
4
- Baseline: official DSH / Windows Desktop 0.2.0-rc.2. Plugin-only.
3
+ Target: official DSH / Windows Desktop `0.2.0-rc.2`. Plugin-only.
5
4
 
6
- ## Evidence and limits
5
+ ## Current behavior
7
6
 
8
- A failed Auto continuation selected a vision-capable model and received an
9
- image-media-type validation error. Read-only local inspection found historical
10
- `read_image` tool results, including genuine WebP attachments whose display
11
- names ended in `.png`. No conversation bodies, attachment bytes, account data or
12
- opaque replay references are included here.
7
+ Auto checks actual typed image blocks in **all entered messages**, including
8
+ historical user/tool content after a text-only continuation. It does not inspect
9
+ tool arguments or infer images from filenames/textual offload placeholders.
10
+ Core's `offloaded: true` marker means projected text, not image bytes.
13
11
 
14
- This does not establish that the model lacks vision, that WebP is universally
15
- unsupported, or that the historical attachment's encoding was sent unchanged.
16
- [AWS's Grok 4.7 model card](https://docs.aws.amazon.com/bedrock/latest/userguide/model-card-xai-grok-4-7.html)
17
- documents image input, but is not evidence of GitHub Copilot endpoint format
18
- acceptance. Do not exclude a model by name to conceal this error.
12
+ The picker advertises aggregate image input only with an eligible account image
13
+ model. Auto filters text-only candidates before task preferences; no eligible
14
+ image model fails explicitly rather than sending content to an unverified route.
19
15
 
20
- Two distinct gaps were identified:
16
+ For fixed and Auto managed calls, the account-bound public `inspectRequest`
17
+ hook checks the native transcript's **projected MIME** before wire dispatch:
21
18
 
22
- 1. Auto classified image requirements from only the latest user message.
23
- Historical user and tool image blocks were missed after a text-only continuation.
24
- 2. Account discovery retains `visionMediaTypes`, but dispatch did not check
25
- the native projected image MIME against that explicit account evidence.
19
+ | Diagnostic | Meaning |
20
+ |---|---|
21
+ | `COPILOT_IMAGE_INPUT_UNSUPPORTED` | Current account model does not admit image input |
22
+ | `COPILOT_IMAGE_MEDIA_TYPE_UNAVAILABLE` | Actual projected MIME evidence is unavailable |
23
+ | `COPILOT_IMAGE_MEDIA_TYPE_UNSUPPORTED` | Explicit account MIME restrictions reject that projection |
26
24
 
27
- Official rc.2 `llm-pi-ai/src/context.ts` prepares request images through the public
28
- attachment service before provider dispatch. `attachment-local/src/request-image.ts`
29
- can re-encode them. Source filename, durable attachment MIME, and projected
30
- request MIME are therefore different evidence layers.
25
+ Omitted account MIME lists preserve existing verified vision behavior but do
26
+ not prove universal format acceptance. The plugin neither invents a list nor
27
+ converts images itself. Native error/finish behavior, historical attachments,
28
+ turn freezing and existing cancellation/retry policy stay unchanged.
31
29
 
32
- ## Implementation plan and delivered code
30
+ ## Evidence layers and recovery limits
33
31
 
34
- 1. Add regressions for historical user/tool images followed by text-only
35
- continuation, all three Auto preferences, and no eligible vision model.
36
- 2. Scan typed content blocks in all messages supplied to Auto by the existing
37
- pre-step hook. Keep latest-user text complexity, account eligibility and
38
- turn-frozen selection. Do not recursively interpret tool arguments, file
39
- names or textual offload placeholders as image blocks. Honor Core's explicit
40
- `offloaded: true` marker, which projects the image to text rather than bytes.
41
- 3. At the existing account-bound `inspectRequest` hook, validate the native
42
- transcript's actual image `mimeType` after Core projection and before wire.
43
- Restore failures as request-local `INVALID_REQUEST` errors:
44
- `COPILOT_IMAGE_INPUT_UNSUPPORTED`, `COPILOT_IMAGE_MEDIA_TYPE_UNAVAILABLE`,
45
- or `COPILOT_IMAGE_MEDIA_TYPE_UNSUPPORTED`.
46
- 4. Honor explicit account MIME restrictions. If the account omits its MIME list,
47
- preserve existing vision behavior; absence is neither proof of universal
48
- format support nor permission to invent an allowlist.
49
- 5. Cover a synthetic native projection that changes durable WebP into PNG:
50
- advertised PNG is admitted; JPEG-only evidence rejects before model fetch.
51
- Keep original attachments unchanged.
32
+ Source filename, durable attachment MIME and outgoing projected MIME are
33
+ different facts. Native rc.2 prepares images through public attachment services
34
+ and may re-encode them. A `.png` display name can belong to durable WebP; that
35
+ alone does not establish what the provider received.
52
36
 
53
- These changes apply to historical image eligibility at the next Auto decision
54
- and actual projected MIME admission for both fixed and Auto managed requests.
55
- They do not introduce image conversion, history repair, model-name rules,
56
- same-turn reselection, fallback wires, retry loops, or Core patches.
37
+ Do not exclude a model by name to conceal a format failure. A supplier/model
38
+ card's general vision claim is not GitHub endpoint format proof. Exact-format
39
+ Auto filtering from durable MIME can reject a model whose native projection
40
+ would be accepted; candidate-specific projection would require another public
41
+ contract and reviewed tests.
57
42
 
58
- ## Deferred capability and acceptance
43
+ The current fix diagnoses explicit incompatibility, not every provider 400.
44
+ When advertised restrictions and outgoing projection agree but the endpoint
45
+ rejects it, retain the native error. Do not invent capability corrections,
46
+ reselect mid-turn, add a fallback wire or replay the request automatically.
47
+ An explicit smaller [native image budget](./copilot-compaction.md) changes
48
+ outgoing visibility through Core offload; it is not a supplier JSON threshold.
59
49
 
60
- Do not implement Auto MIME filtering from durable attachments: that can reject
61
- a model even when native projection produces a format it accepts. Exact-format
62
- candidate selection or conversion requires a public, candidate-specific
63
- projection contract and its own tests. The current fix diagnoses explicit
64
- incompatibility; it does not rescue every image request.
50
+ ## Verification
65
51
 
66
- The original service-side 400 is not proven fixed. Confirm its account-advertised
67
- limits and exact outgoing MIME without recording image bytes or credentials
68
- before attributing its root cause. If advertised compatibility and actual bytes
69
- agree but the endpoint rejects them, preserve the native error rather than
70
- fabricating a capability correction.
52
+ Historical tool-image continuation first reproduced the old missed-image
53
+ requirement. Regressions now cover all Auto preferences, historical user/tool
54
+ images, no vision candidate and native WebP-to-PNG projection against explicit
55
+ PNG/JPEG restrictions. A mismatch emits native `finish(error)` with zero model
56
+ requests.
71
57
 
72
- ## Validation status
73
-
74
- - A pre-fix Node regression reproduced `requiresImage: false` for a historical
75
- tool image followed by a text-only continuation.
76
- - Focused Auto/admission tests: 23 passed with pinned Vitest 3.2.7 and isolated
77
- unchanged rc.2 public message helper source. This is supplemental evidence,
78
- not the complete native integration/full gate.
79
- - Strict targeted TypeScript check passed:
80
- `node node_modules\typescript\bin\tsc --noEmit --strict --skipLibCheck --target es2023 --module nodenext --moduleResolution nodenext --allowImportingTsExtensions src\auto-model-routing.ts src\image-input-admission.ts`.
81
- - `pnpm install --frozen-lockfile --ignore-scripts --fetch-retries=0 --fetch-timeout=20000`
82
- failed: the configured enterprise registry returned HTTP 404 for
83
- `@deepseek-ai/dsh-util-crypto@0.2.0-rc.2`. Full local validation is blocked.
84
- - [CI run 36966798814](https://github.com/cloga/dsh-github-copilot/actions/runs/36966798814)
85
- passed on Windows and Linux using unchanged official rc.2 dependencies:
86
- the published-adapter fixture, tagged-source native runtime, full `pnpm verify`,
87
- `pnpm pack --pack-destination artifacts`, and exact tarball verification.
88
- The full gate includes 1990 passing Vitest tests (2 expected skips) and
89
- 310 passing tooling tests. Native MIME admission preserves Core's streamed
90
- `finish(error)` contract and sends zero model requests for the mismatch case.
91
- - This authorized CI path mitigates the local registry blocker without changing
92
- dependencies or bypassing local registry policy. Publication and live
93
- acceptance remain separate; no installed or published fix is claimed here.
58
+ The [delivery CI](https://github.com/cloga/dsh-github-copilot/actions/runs/36966798814)
59
+ passed exact unchanged rc.2 Windows/Linux source and published-adapter fixtures,
60
+ full verification and archive gates. Local synthetic transport demonstrates
61
+ admission/ownership, not live endpoint acceptance or a particular Desktop's
62
+ loaded version. The original [investigation #236](https://github.com/cloga/dsh-github-copilot/issues/236)
63
+ retains the bounded observation and delivery evidence; old local registry
64
+ failures are not a permanent unsupported/shipping-pending claim.
@@ -48,3 +48,44 @@ Follow the [plugin-only boundary](../AGENTS.md#plugin-only-implementation-bounda
48
48
  - [pi v0.87.1 release](https://github.com/earendil-works/pi/releases/tag/v0.87.1)
49
49
 
50
50
  These references guide parsing and tests; they are not a guarantee that the upstream discovery schema will never change. Schema drift must be surfaced rather than silently guessed.
51
+
52
+ ## Authentication, replay and request diagnostics
53
+
54
+ These failures have different owners; do not repair every rejection by signing out.
55
+
56
+ | Diagnostic | Boundary and safe action |
57
+ |---|---|
58
+ | `COPILOT_AUTHORIZATION_BEGIN_FAILED` | Sign-in did not complete; interaction milestones are not a credential commit or root-cause proof |
59
+ | `COPILOT_ROUTE_REPAIR_FAILED` | Authentication is retained; review legacy configuration and use explicit repair |
60
+ | Native AUTH / HTTP 401 | Exact managed proof may be retired; a later explicit request/discovery can renew natively, not replay the failed message |
61
+ | `COPILOT_RESPONSES_REPLAY_SCOPE_MISMATCH` | Exact uncoded item-scope rejection is request-local INVALID_REQUEST, without invalidating shared proof/other requests |
62
+ | `COPILOT_RESPONSES_REPLAY_UNSUPPORTED` | Incomplete/reference-only historical payload lacks safe reconstruction evidence |
63
+ | `COPILOT_REQUEST_BODY_TIMEOUT` | Strict verified request-body 408; composition/timing is not proof of overflow or network cause |
64
+
65
+ HTTP auth recovery is bounded by account cooldown, including forced discovery.
66
+ An old late response cannot invalidate a newer sign-in. HTTP 403, network errors
67
+ and strings mentioning 401 are not auth evidence; malformed/ambiguous/oversized
68
+ bodies retain native handling. HTTP tests do not prove WebSocket recovery.
69
+
70
+ ### Responses replay compatibility
71
+
72
+ The public SDK payload hook normalizes only direct IDs on complete assistant
73
+ messages, function calls and encrypted reasoning items. A narrowly recognized
74
+ empty completed reasoning shell can be omitted from outgoing requests only with
75
+ empty summary/content, no encrypted content and no unknown fields. Durable
76
+ history, public summaries, opaque bytes, nested IDs, phase and `call_id` pairing
77
+ stay unchanged.
78
+
79
+ After actual HTTP 408, a newly prepared attempt in the same native step can
80
+ reuse exact normalized payload only when transcript/every other field agree,
81
+ with matching references and no conflicts. Evidence is bound to Session/model/
82
+ account proof and original signal, expires in 60 seconds, is limited to 2 MiB
83
+ and clears on next step/turn, concurrency, cancellation or account discontinuity.
84
+ This creates no retry or cold-history reconstruction. Canonical/other routes,
85
+ protocols and native retry policy stay unchanged. Synthetic adapter tests are
86
+ not acceptance proof for an old conversation. Never discard opaque reasoning,
87
+ rewrite history, replay business work or reset credentials automatically.
88
+
89
+ For TLS/quota, see [trust boundaries](./copilot-usage.md#account-data-boundary).
90
+ For HTTP 408 and oversized summaries, see
91
+ [budget and recovery limits](./copilot-compaction.md#existing-oversized-history-and-recovery-limits).