dsh-github-copilot 0.1.0-alpha.1.dsh.0.2.1.alpha.5
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 +439 -0
- package/CHANGELOG.md +875 -0
- package/CONTRIBUTING.md +55 -0
- package/LICENSE +21 -0
- package/README.md +366 -0
- package/README.zh.md +341 -0
- package/SECURITY.md +29 -0
- package/cordis.patch.yml +16 -0
- package/deployment-baseline.json +1580 -0
- package/docs/account-management-experience.md +143 -0
- package/docs/agent-readiness.md +110 -0
- package/docs/auto-high-cost.md +255 -0
- package/docs/auto-iteration-review.json +22 -0
- package/docs/auto-review-sampling.md +60 -0
- package/docs/auto-task-routing.md +341 -0
- package/docs/automatic-model-routing.md +236 -0
- package/docs/copilot-accounts.md +424 -0
- package/docs/copilot-compaction.md +148 -0
- package/docs/copilot-usage.md +133 -0
- package/docs/dual-model.md +66 -0
- package/docs/evidence-driven-iteration.md +86 -0
- package/docs/image-input-compatibility.md +64 -0
- package/docs/images/copilot-accounts-credits.png +0 -0
- package/docs/images/copilot-accounts.png +0 -0
- package/docs/images/copilot-current-provenance.json +39 -0
- package/docs/images/copilot-model-preferences.png +0 -0
- package/docs/images/copilot-search-routing.png +0 -0
- package/docs/images/copilot-session-continuation.png +0 -0
- package/docs/images/dual-model-desktop.png +0 -0
- package/docs/images/dual-model-mobile.png +0 -0
- package/docs/images/dual-model-provenance.json +35 -0
- package/docs/images/parent-model-follow.png +0 -0
- package/docs/manual-compaction-recovery.md +109 -0
- package/docs/mockups/copilot-account-dropdown.html +71 -0
- package/docs/mockups/copilot-account-management.html +393 -0
- package/docs/model-compatibility-acceptance.md +182 -0
- package/docs/npm-distribution.md +202 -0
- package/docs/official-first-016-alpha2.md +66 -0
- package/docs/official-first-020-rc1.md +32 -0
- package/docs/official-first-020-rc2.md +17 -0
- package/docs/official-first-021-alpha4.md +157 -0
- package/docs/official-first-021-alpha5.md +83 -0
- package/docs/plugin-diagnostics.md +605 -0
- package/docs/session-continuation.md +141 -0
- package/docs/session-search-routing.md +133 -0
- package/docs/single-route-migration.md +131 -0
- package/docs/web-lifecycle-rc2.md +55 -0
- package/lib/client.js +13236 -0
- package/lib/client.js.map +1 -0
- package/lib/copilot-identity-DRZY_d2X.js +15 -0
- package/lib/diagnostics-analysis-io.js +78 -0
- package/lib/diagnostics-analysis.js +427 -0
- package/lib/diagnostics-types-CF-qg8Do.js +708 -0
- package/lib/index.js +15661 -0
- package/lib/manual-compaction-recovery.js +485 -0
- package/lib/remote.js +1507 -0
- package/lib/request-budget-DLY_aRq0.js +87 -0
- package/lib/routed-web.js +120 -0
- package/lib/search-routing-CV2hs8as.js +792 -0
- package/lib/types/account-dropdown.d.ts +22 -0
- package/lib/types/account-model-auth.d.ts +15 -0
- package/lib/types/account-model-catalog.d.ts +70 -0
- package/lib/types/account-model-source.d.ts +85 -0
- package/lib/types/agent-compaction.d.ts +4 -0
- package/lib/types/authorization-code-clipboard.d.ts +4 -0
- package/lib/types/authorization-controller.d.ts +121 -0
- package/lib/types/auto-allocation-card.d.ts +9 -0
- package/lib/types/auto-allocation-diagnostics.d.ts +126 -0
- package/lib/types/auto-allocation-evidence.d.ts +44 -0
- package/lib/types/auto-allocation.d.ts +47 -0
- package/lib/types/auto-assessment-evidence.d.ts +111 -0
- package/lib/types/auto-model-host.d.ts +30 -0
- package/lib/types/auto-model-intent.d.ts +36 -0
- package/lib/types/auto-model-presentation.d.ts +57 -0
- package/lib/types/auto-model-routing.d.ts +64 -0
- package/lib/types/auto-review-sampling.d.ts +6 -0
- package/lib/types/auto-selection-explanation.d.ts +9 -0
- package/lib/types/auto-task-assessment.d.ts +49 -0
- package/lib/types/auto-task-classifier.d.ts +10 -0
- package/lib/types/background-compaction.d.ts +30 -0
- package/lib/types/client.d.ts +129 -0
- package/lib/types/compact-account.d.ts +42 -0
- package/lib/types/compaction-continuation-ui.d.ts +29 -0
- package/lib/types/compaction-continuation.d.ts +48 -0
- package/lib/types/compaction-input-estimate.d.ts +28 -0
- package/lib/types/compaction-pressure.d.ts +23 -0
- package/lib/types/compaction-replay.d.ts +18 -0
- package/lib/types/compatibility.d.ts +17 -0
- package/lib/types/composer-notice-style.d.ts +7 -0
- package/lib/types/config.d.ts +141 -0
- package/lib/types/content-file.d.ts +10 -0
- package/lib/types/context-evidence-ui.d.ts +28 -0
- package/lib/types/context-evidence.d.ts +256 -0
- package/lib/types/context-usage.d.ts +4 -0
- package/lib/types/copilot-account-presentation.d.ts +7 -0
- package/lib/types/copilot-accounts-card.d.ts +43 -0
- package/lib/types/copilot-accounts-host.d.ts +93 -0
- package/lib/types/copilot-accounts-remote.d.ts +85 -0
- package/lib/types/copilot-accounts-types.d.ts +43 -0
- package/lib/types/copilot-auth.d.ts +31 -0
- package/lib/types/copilot-grant.d.ts +11 -0
- package/lib/types/copilot-identity.d.ts +11 -0
- package/lib/types/copilot-request.d.ts +11 -0
- package/lib/types/copilot-stream-liveness.d.ts +23 -0
- package/lib/types/copilot-usage-card.d.ts +51 -0
- package/lib/types/copilot-usage-host.d.ts +61 -0
- package/lib/types/copilot-usage-normalize.d.ts +9 -0
- package/lib/types/copilot-usage-remote.d.ts +63 -0
- package/lib/types/copilot-usage-types.d.ts +20 -0
- package/lib/types/copilot-usage-ui.d.ts +4 -0
- package/lib/types/current-provider.d.ts +59 -0
- package/lib/types/deepseek-search-fallback.d.ts +11 -0
- package/lib/types/diagnostics-analysis-io.d.ts +23 -0
- package/lib/types/diagnostics-analysis.d.ts +298 -0
- package/lib/types/diagnostics-card.d.ts +12 -0
- package/lib/types/diagnostics-client.d.ts +13 -0
- package/lib/types/diagnostics-collector.d.ts +50 -0
- package/lib/types/diagnostics-host.d.ts +183 -0
- package/lib/types/diagnostics-remote.d.ts +113 -0
- package/lib/types/diagnostics-types.d.ts +893 -0
- package/lib/types/dual-model-host.d.ts +119 -0
- package/lib/types/dual-model-remote.d.ts +63 -0
- package/lib/types/dual-model-types.d.ts +34 -0
- package/lib/types/external-link.d.ts +3 -0
- package/lib/types/failure.d.ts +38 -0
- package/lib/types/http.d.ts +48 -0
- package/lib/types/image-input-admission.d.ts +5 -0
- package/lib/types/index.d.ts +39 -0
- package/lib/types/manual-compaction-recovery.d.ts +67 -0
- package/lib/types/migration-status.d.ts +50 -0
- package/lib/types/model-exclusions.d.ts +15 -0
- package/lib/types/model-preferences-card.d.ts +9 -0
- package/lib/types/model-protocol.d.ts +31 -0
- package/lib/types/native-select-style.d.ts +4 -0
- package/lib/types/native-settings-style.d.ts +10 -0
- package/lib/types/parent-model-follow-card.d.ts +32 -0
- package/lib/types/parent-model-follow.d.ts +44 -0
- package/lib/types/pi-provider-bridge.d.ts +22 -0
- package/lib/types/plan.d.ts +148 -0
- package/lib/types/pre-step-pressure.d.ts +8 -0
- package/lib/types/preview-provider.d.ts +77 -0
- package/lib/types/preview-route.d.ts +76 -0
- package/lib/types/probe.d.ts +39 -0
- package/lib/types/remote-codec.d.ts +10 -0
- package/lib/types/remote.d.ts +202 -0
- package/lib/types/replay-recovery-host.d.ts +28 -0
- package/lib/types/replay-recovery-remote.d.ts +14 -0
- package/lib/types/replay-recovery-types.d.ts +24 -0
- package/lib/types/replay-recovery-ui.d.ts +28 -0
- package/lib/types/replay-recovery.d.ts +17 -0
- package/lib/types/request-body-composition.d.ts +17 -0
- package/lib/types/request-body-evidence.d.ts +37 -0
- package/lib/types/request-body-timeout-marker.d.ts +2 -0
- package/lib/types/request-body-timeout.d.ts +4 -0
- package/lib/types/request-budget.d.ts +58 -0
- package/lib/types/request-diagnostics.d.ts +278 -0
- package/lib/types/request-upload-evidence.d.ts +23 -0
- package/lib/types/response-error-body.d.ts +3 -0
- package/lib/types/responses-reasoning-text.d.ts +24 -0
- package/lib/types/responses-reasoning.d.ts +7 -0
- package/lib/types/responses-replay-compat.d.ts +31 -0
- package/lib/types/responses-request-compression.d.ts +33 -0
- package/lib/types/route-ownership.d.ts +70 -0
- package/lib/types/routed-web.d.ts +50 -0
- package/lib/types/search-backend.d.ts +16 -0
- package/lib/types/search-routing-host.d.ts +19 -0
- package/lib/types/search-routing-policy.d.ts +18 -0
- package/lib/types/search-routing-remote.d.ts +20 -0
- package/lib/types/search-routing.d.ts +43 -0
- package/lib/types/search-tool-routing.d.ts +22 -0
- package/lib/types/serialize.d.ts +106 -0
- package/lib/types/session-accounts-controller.d.ts +20 -0
- package/lib/types/session-accounts-host.d.ts +33 -0
- package/lib/types/session-accounts-remote.d.ts +114 -0
- package/lib/types/session-accounts.d.ts +38 -0
- package/lib/types/session-continuation-host.d.ts +45 -0
- package/lib/types/session-continuation-remote.d.ts +22 -0
- package/lib/types/session-continuation-types.d.ts +62 -0
- package/lib/types/session-continuation-ui.d.ts +49 -0
- package/lib/types/session-continuation.d.ts +14 -0
- package/lib/types/settings-reader.d.ts +16 -0
- package/lib/types/sse.d.ts +28 -0
- package/lib/types/temporary-models.d.ts +25 -0
- package/lib/types/tool-schema-compat.d.ts +17 -0
- package/lib/types/traditional-search.d.ts +17 -0
- package/lib/types/turn-model-provenance.d.ts +45 -0
- package/lib/types/turn-request-models.d.ts +55 -0
- package/lib/types/turn-selection-card.d.ts +24 -0
- package/lib/types/turn-selection-host.d.ts +35 -0
- package/lib/types/turn-selection-remote.d.ts +17 -0
- package/lib/types/turn-selection.d.ts +186 -0
- package/lib/types/turn-usage-evidence.d.ts +66 -0
- package/lib/types/turn-usage-notice.d.ts +7 -0
- package/lib/types/types.d.ts +69 -0
- package/lib/types/usage.d.ts +26 -0
- package/lib/types/watchdog.d.ts +22 -0
- package/lib/types/web-delegate.d.ts +12 -0
- package/lib/types/web-search-routing-card.d.ts +16 -0
- package/lib/types/web-search-routing-config.d.ts +12 -0
- package/lib/types/wire-anthropic.d.ts +37 -0
- package/lib/types/wire.d.ts +56 -0
- package/lib/web-delegate.js +9 -0
- package/output/auto-model-mockup/index.html +207 -0
- package/package.json +261 -0
- package/scripts/analyze-diagnostics.mjs +91 -0
- package/scripts/check-search-composition.mjs +191 -0
- package/scripts/iteration-review.mjs +53 -0
- package/scripts/release-policy.mjs +353 -0
- package/scripts/select-core-release.mjs +11 -0
package/CONTRIBUTING.md
ADDED
|
@@ -0,0 +1,55 @@
|
|
|
1
|
+
# Contributing
|
|
2
|
+
|
|
3
|
+
## Scope first
|
|
4
|
+
|
|
5
|
+
Read [AGENTS.md](./AGENTS.md) before changing code. This repository is a narrow companion to DSH's built-in `@deepseek-ai/dsh-llm-pi-ai`; do not add a second general Copilot adapter, catalog, credential store, external gateway, or sandbox owner. Exact temporary model compatibility remains constrained by the documented account/ownership gates.
|
|
6
|
+
|
|
7
|
+
Use a tracking issue to describe the problem and owning seam. Security-sensitive reports belong in [private vulnerability reporting](./SECURITY.md), not a public issue. Use native DSH tools, local Git and the GitHub REST API; no external orchestrator or special VCS tool is required.
|
|
8
|
+
|
|
9
|
+
## Plugin-only delivery
|
|
10
|
+
|
|
11
|
+
Follow the **plugin-only** boundary in [AGENTS.md](./AGENTS.md#plugin-only-implementation-boundary). Fixes must live in this plugin and use existing published public APIs. Do not modify Core source, patch installed Core or `node_modules`, monkey-patch Core internals/shared catalogs, or prepare Core PRs/releases as part of this work. A new Core export or patch being merged is not an acceptable plugin delivery prerequisite.
|
|
12
|
+
|
|
13
|
+
Core inspection is read-only. Isolated tests may use unchanged pinned Core artifacts and owned temporary fixtures, never edits to tracked Core implementation or a live deployment. If an API is insufficient, document the limitation and a plugin-local alternative; do not silently move the task into Core. A separate, explicit human Core task is required for any future Core work—generic compatibility or optimization requests do not authorize it.
|
|
14
|
+
|
|
15
|
+
## Change workflow
|
|
16
|
+
|
|
17
|
+
1. Determine `pwd`, Git status, remote and actual default branch. Preserve other people's changes. Start a feature branch such as `feature/issue-73-agent-readiness`; branch names need not contain an owner name.
|
|
18
|
+
2. Read `node scripts/agent.mjs describe --json` and run `node scripts/agent.mjs doctor --json`. These are read-only repository diagnostics, not live health checks. Plans from `node scripts/agent.mjs plan <task> --json` contain unexecuted argv lists.
|
|
19
|
+
3. Use Node 24 LTS for development (runtime floor: 22.19.0), the pinned pnpm version, and frozen install inside the checkout/worktree.
|
|
20
|
+
4. Add focused regression tests before changing capability claims. Keep READMEs, deployment evidence and the Agent task map aligned.
|
|
21
|
+
5. State expected outcomes and scope; run:
|
|
22
|
+
|
|
23
|
+
```sh
|
|
24
|
+
pnpm install --frozen-lockfile
|
|
25
|
+
pnpm verify
|
|
26
|
+
pnpm pack --pack-destination artifacts
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
Validate the resulting exact path with `pnpm verify:tarball -- artifacts/dsh-github-copilot-<package-version>.tgz`. The release task plan supplies that path automatically. Never run broad cleanup on an existing artifacts directory just to package again.
|
|
30
|
+
6. Inspect the complete diff, compare expected versus actual results, and report what was NOT checked. Source markers, stubbed unit tests, built module imports, upstream config fixtures, authenticated API calls, installation, and loaded UI are different evidence layers.
|
|
31
|
+
7. Commit with the issue reference and accurate attribution. For work assisted by DSH use `Assisted-by: DeepSeek Harness (DSH)`. Other agents must name the actual tool; do not infer authorship from the model vendor or copy a bot identity. Add `Co-authored-by` only for real verified collaborators. No fabricated email, author replacement or published-history rewrite.
|
|
32
|
+
8. Push the feature branch and open a PR containing `Fixes #<issue>`, verification, risks and rollback. For user-requested delivery, merge without an additional approval prompt after required review/CI and branch protection; respect explicit code-only, review-only or do-not-merge restrictions.
|
|
33
|
+
|
|
34
|
+
Generated `lib/` output, archives, `.env`, tokens, local credentials, machine state and production screenshots with real authorization codes must not be committed. Use synthetic fixtures for screenshots and report staged UI honestly.
|
|
35
|
+
|
|
36
|
+
## Release changes
|
|
37
|
+
|
|
38
|
+
GitHub Releases and npm are the default distribution channels for every new version, superseding the Release-only decision in #43 at the user's request. The public package uses the exact same verified tarball in both channels. No automatic npm opt-out is allowed. See [npm distribution](./docs/npm-distribution.md) for initial maintainer bootstrap, OIDC, retry recovery and organizational access requirements.
|
|
39
|
+
|
|
40
|
+
Important user-requested features, behavior fixes, compatibility fixes, and security or stability fixes include release follow-through by default after a reviewed merge and green required CI. Do not stop at the merged PR or ask for a second release confirmation. User instructions limiting delivery to code/review or forbidding publication take precedence; documentation-only, internal-only and unrelated releases are not implicitly authorized. Follow the [important-update delivery rule](./AGENTS.md#important-update-release-delivery).
|
|
41
|
+
|
|
42
|
+
Prepare version alignment in the implementation PR. Important runtime or delivery changes fail the `release-ready` PR check unless `package.json` is strictly newer than the base and `deployment-baseline.json` plus both README install URLs agree. Retain the current prerelease channel unless promotion is requested. Docs/tests-only changes may keep the current version. Never move or reuse a tag. Local installation, sign-out and worktree checkout still need explicit approval; restarting active Sessions requires acknowledgement of the interruption.
|
|
43
|
+
|
|
44
|
+
After the release-ready PR merges, the successful main CI run calls the reusable Release workflow on that exact SHA. It creates or reconciles the annotated version tag and a draft-first Release, rebuilds and verifies the package, writes and verifies `SHA256SUMS`, checks remote asset digests, and only then publishes an immutable Release. Identical reruns reconcile safely; conflicting tags, releases or bytes fail closed. A tag created by `GITHUB_TOKEN` does not trigger a second workflow, so publication occurs in the gated main workflow rather than depending on recursive tag events. Do not hand-upload a replacement or bypass failed CI.
|
|
45
|
+
|
|
46
|
+
Release-bearing work is complete only after reporting the published Release URL and verified version/commit/assets/checksum, or clearly identifying a concrete publication blocker and pending step. A merged PR or a local tarball alone is not release delivery. After publication, independently verify the Release is not a draft, its prerelease flag, exact tag/commit, asset names and downloaded SHA-256. An install command must include the target `--profile`; never overwrite a shipped preset. Compare the installed package to the downloaded asset, then separately validate activation after restart. HTTP 200 alone does not prove the new plugin loaded.
|
|
47
|
+
|
|
48
|
+
## Auto policy evidence
|
|
49
|
+
|
|
50
|
+
Before Auto routing, assessment, high-cost, continuity or assistance changes,
|
|
51
|
+
read and validate `docs/auto-iteration-review.json`. Follow
|
|
52
|
+
[`docs/evidence-driven-iteration.md`](./docs/evidence-driven-iteration.md) and
|
|
53
|
+
record the prior decision, evidence status/denominator, actual validation and
|
|
54
|
+
post-delivery owner/trigger in the PR. Missing observations are not a pass.
|
|
55
|
+
Never upload raw local exports or infer billing/quality from allocation counts.
|
package/LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2025 yms
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
package/README.md
ADDED
|
@@ -0,0 +1,366 @@
|
|
|
1
|
+
# dsh-github-copilot
|
|
2
|
+
|
|
3
|
+
[](https://github.com/cloga/dsh-github-copilot/actions/workflows/ci.yml)
|
|
4
|
+
[](https://github.com/cloga/dsh-github-copilot/releases)
|
|
5
|
+
[](./LICENSE)
|
|
6
|
+
|
|
7
|
+
**English** | [简体中文](./README.zh.md)
|
|
8
|
+
|
|
9
|
+
GitHub Copilot account discovery, contextual Auto routing and hosted search for DSH. The plugin reuses DSH's published native adapter, retaining a profile-wide account default with independent Session next-turn choices; it does not patch Core or maintain a second model catalog.
|
|
10
|
+
|
|
11
|
+
**Historical stable release: [`0.4.1`](https://github.com/cloga/dsh-github-copilot/releases/tag/v0.4.1); pending DSH alpha.5 line: `0.1.0-alpha.1.dsh.0.2.1.alpha.5`.** Each exact DSH Core version starts an independent plugin sequence at `0.1.0-alpha.1.dsh.<Core>`; same-Core fixes increment `alpha.N`. The suffix normalizes Core `0.2.1-alpha.5` to `dsh.0.2.1.alpha.5`, but compatibility is validated against explicit metadata, not guessed from the name. This resets numbering, not code, history or qualification requirements. Existing versions/tags remain unchanged. Candidate Desktop artifacts/signatures are unverified; this is not a Desktop-upgrade recommendation. Published, installed and loaded states remain separate.
|
|
12
|
+
|
|
13
|
+
Select by **exact Core**, never global SemVer maximum or npm `latest`/`alpha`.
|
|
14
|
+
The read-only `node scripts/select-core-release.mjs 0.2.0-rc.2` command checks
|
|
15
|
+
`deployment-baseline.json`'s mapping and verifies the exact public GitHub Release,
|
|
16
|
+
tarball/checksum assets and npm version's `engines.dsh` before returning an
|
|
17
|
+
install spec. Rc.2 maps to alpha.15, Core alpha.4 to alpha.16, and Core alpha.5
|
|
18
|
+
to this candidate; until both channels are observable, it reports pending or
|
|
19
|
+
incomplete without an install recommendation. Unknown targets fail explicitly. The existing npm
|
|
20
|
+
`alpha` channel remains global and is not compatibility-aware; `latest` remains
|
|
21
|
+
the historical stable pointer. No automatic updater integration or old-Core
|
|
22
|
+
maintenance is promised. See [release selection](./docs/npm-distribution.md#exact-core-release-lines).
|
|
23
|
+
|
|
24
|
+
**Native refresh protection:** 0.4.1 introduced preservation of already-dispatched HTTP streams across proven plugin-owned refresh with unchanged account, endpoint and entitlements. Versions through 0.4.2-alpha.13 still missed this proof across real Cordis traced service faces; 0.4.2-alpha.14 fixes that identity mismatch. Subsequent requests use freshly validated auth and metadata. Unknown/external credential notifications, revocation, cancellation and provider rejections remain explicit—not a promise of invisible recovery or automatic retry. See [the refresh boundary](./docs/copilot-accounts.md#native-oauth-refresh-and-dispatched-requests-385).
|
|
25
|
+
|
|
26
|
+
**Compaction planning:** alpha.15 fixes byte counts being compared with token budgets in the separately selected recovery engine. Planning now uses the public native token meter, preserving complete tool relations and final native admission. Truly oversized balanced units still fail explicitly; this is not history repair or guaranteed recovery. See [compaction recovery](./docs/manual-compaction-recovery.md).
|
|
27
|
+
|
|
28
|
+
**DSH alpha.5 adaptation:** exact public APIs use pi-ai `1.1.0`, the official
|
|
29
|
+
Cordis/schemastery peers and storage-domain's Zod `4.4.3`. The
|
|
30
|
+
[fixed-target official-first review](https://github.com/cloga/dsh-github-copilot/blob/main/docs/official-first-021-alpha5.md)
|
|
31
|
+
records every retain/migrate/retire/defer decision. Alpha.4 natively hides blank
|
|
32
|
+
Thinking disclosures; the redundant plugin renderer and provenance projection
|
|
33
|
+
are retired without changing messages or replay. Exact native reviewer identity,
|
|
34
|
+
dynamic system/tool conversion, replay, account/Remote/compaction and mounted
|
|
35
|
+
selector regressions gate admission. No Core patch, version exemption, new
|
|
36
|
+
wire/catalog, policy migration or durable decision recording is introduced.
|
|
37
|
+
|
|
38
|
+
|
|
39
|
+
Alpha.5 qualification also preserves code-first PTC schemas and function-body/REPL instructions. The new inline model-label slot is an opportunity only: no label UI or historical model attribution is added. Alpha.4 hosts may retain alpha.16.
|
|
40
|
+
|
|
41
|
+
## What you can do
|
|
42
|
+
|
|
43
|
+
**High-cost Auto:** in **Manage → Model preferences**, mark costly models with
|
|
44
|
+
**High cost**. Cost and task difficulty are independent: across every category,
|
|
45
|
+
all eligible fitting candidates retain a nonzero chance. Ordinary
|
|
46
|
+
weight `1` gets a finite continuity bonus (`1.5×` for the previous model).
|
|
47
|
+
High-cost base weight is `0.2`; if that model was used in the previous turn,
|
|
48
|
+
its weight decays tenfold to `0.02` instead of receiving a bonus.
|
|
49
|
+
This one-turn recency penalty is a declared trial, not calibrated quality.
|
|
50
|
+
Marking does not change fixed choices or admitted turns. This is a declared
|
|
51
|
+
policy, not a price/quality ranking or proven savings.
|
|
52
|
+
|
|
53
|
+
The existing turn selection dialog exposes **Auto allocation observations**:
|
|
54
|
+
local retained opportunities, expected shares and actual selections for this
|
|
55
|
+
Session, with a read-only JSON export. This view remains Host-lifetime only.
|
|
56
|
+
For durable evaluation, default-off **Local diagnostics** also retains daily
|
|
57
|
+
aggregates by policy/model/category, demand and assessment source, high-cost
|
|
58
|
+
and continuity state, expected/actual selections and no-fit decisions for 14
|
|
59
|
+
days. Enable it independently through the plugin detail settings page; this
|
|
60
|
+
does not enable account/Checking or compaction collection. No Session/turn IDs,
|
|
61
|
+
conversation content, execution/outcome claims, automatic tuning or upload.
|
|
62
|
+
`autoAllocationEvidence: false` stops future candidate evidence in the
|
|
63
|
+
turn-selection view without changing routing. The auxiliary classifier
|
|
64
|
+
prefers unmarked eligible Lightweight models separately. Advisor calls are not
|
|
65
|
+
implemented. See [requirements](./docs/auto-high-cost.md),
|
|
66
|
+
[local diagnostics](./docs/plugin-diagnostics.md) and the
|
|
67
|
+
[required iteration review](./docs/evidence-driven-iteration.md).
|
|
68
|
+
|
|
69
|
+
The [local diagnostics pilot](./docs/plugin-diagnostics.md) records bounded
|
|
70
|
+
account/Checking, compaction and Auto allocation aggregates, **default off**. After installing
|
|
71
|
+
and loading the published build, open the plugin detail settings page →
|
|
72
|
+
**Local diagnostics → Read status → Enable local collection**. This enables
|
|
73
|
+
local account/Checking and compaction persistence, not uploads or scheduled
|
|
74
|
+
analysis. Enable **Auto allocation observation** separately to collect only
|
|
75
|
+
Auto allocation aggregates. **Enable request observations** is a third, independent,
|
|
76
|
+
default-off control: up to 128 content-free managed-adapter physical requests
|
|
77
|
+
for 24 hours, with model, JSON/wire byte counts, timings, HTTP status and terminal
|
|
78
|
+
categories. No bodies, headers, credentials or Session/turn IDs are collected.
|
|
79
|
+
Local body-write completion does not prove supplier receipt; these diagnostics
|
|
80
|
+
do not fix timeouts or alter retry/Usage behavior.
|
|
81
|
+
All diagnostic groups, including Auto, are independently collapsed by default
|
|
82
|
+
inside the Local diagnostics region. Request consent also covers up to 128
|
|
83
|
+
credential-change notification/commit observations for 24 hours: fixed
|
|
84
|
+
qualification reasons and live-wire counts only. Unknown source remains unknown;
|
|
85
|
+
no past incident or account/Session attribution is reconstructed. See
|
|
86
|
+
[credential-change evidence](./docs/plugin-diagnostics.md#credential-change-decisions-402).
|
|
87
|
+
Large JSON bodies up to 32 MiB can receive bounded, cooperative composition
|
|
88
|
+
counts without a full payload parse; the approximately 20.4 MiB class no longer
|
|
89
|
+
necessarily hits the old 16 MiB diagnostic blind spot. Time/work/cancellation
|
|
90
|
+
limits remain explicit, and settled rows may acquire counts on a later read.
|
|
91
|
+
No gzip, history trimming or extra retry is enabled. See [request observations](./docs/plugin-diagnostics.md#content-free-physical-request-observations-392).
|
|
92
|
+
The package also has an explicit offline analyzer
|
|
93
|
+
for a caller-selected persisted unit or reviewed aggregate view; it writes only
|
|
94
|
+
to a new local report file and never scans, uploads or changes collection. Pause
|
|
95
|
+
preserves evidence; Clear requires separate confirmation. Client/Host
|
|
96
|
+
populations, uncovered paths and reporting/storage gaps remain explicit.
|
|
97
|
+
Descriptive counts are not reconstructed history, failure rates or proof of an
|
|
98
|
+
improvement. The diagnostics page opens on a daily Auto allocation table by UTC
|
|
99
|
+
date, policy, model and cohort, with opportunities, expected selections, selected
|
|
100
|
+
counts and no-fit decisions. Compare expected and selected counts only within
|
|
101
|
+
matching cohorts. New cohorts distinguish assessment timeouts, unavailable/invalid
|
|
102
|
+
results, omitted context, disabled assessment and genuinely unknown local/semantic
|
|
103
|
+
results; legacy reasons remain **not recorded**. Count tasks with Selected plus
|
|
104
|
+
No-fit, not candidate opportunities. This is diagnostic coverage, not a routing
|
|
105
|
+
change or proof of the supplier root cause. Account/Checking and compaction reports, collection controls,
|
|
106
|
+
and detailed scope, limits and JSON are in collapsed disclosures; clearing still
|
|
107
|
+
requires separate confirmation.
|
|
108
|
+
|
|
109
|
+
To analyze an explicitly qualified file from a built package or source checkout:
|
|
110
|
+
|
|
111
|
+
```sh
|
|
112
|
+
node scripts/analyze-diagnostics.mjs --input "ABSOLUTE_UNIT_FILE.json" --mode persisted-unit --profile-name "PROFILE_NAME" --output "NEW_LOCAL_REPORT.json"
|
|
113
|
+
```
|
|
114
|
+
|
|
115
|
+
Replace the placeholders with the reviewed file/profile and a new absolute output path. For a reviewed aggregate view export, use `--mode reviewed-view` without `--profile-name`. [Read qualification and interpretation limits](./docs/plugin-diagnostics.md#explicit-offline-analysis-368) explain the accepted envelope, bounds and persisted-only evidence; no daily schedule is included.
|
|
116
|
+
|
|
117
|
+
| Task | Where to start |
|
|
118
|
+
|---|---|
|
|
119
|
+
| Sign in and manage account models | **Settings → Models → GitHub Copilot → Sign in** |
|
|
120
|
+
| Add or switch GitHub accounts | **Manage → Account management → Switch**; managed-only profiles |
|
|
121
|
+
| Select this Session's next-turn account | **Credits → Switch account**; saved authorizations only |
|
|
122
|
+
| Return this Session to the global default account | **Credits → Follow global default**; account selection only, not the model |
|
|
123
|
+
| Exclude or restore individual models | **Manage → Model preferences** |
|
|
124
|
+
| Choose models automatically | Pick **Auto · Balance**, **Auto · Efficiency** or **Auto · Intelligence** |
|
|
125
|
+
| Follow a parent model in supported subagents | **Plugins → dsh-github-copilot → Details → Follow parent model** |
|
|
126
|
+
| Choose primary/fallback search providers | **Plugin details → Web search** |
|
|
127
|
+
| Set the visible-history default for new Sessions | **Settings → Models → GitHub Copilot → Manage → New Session continuation default** |
|
|
128
|
+
| Enable visible-history for an existing Session | Select a managed Copilot model, open the composer **Credits/usage** pill → **Visible-history continuation** → **Session policy → On** |
|
|
129
|
+
| Read account Credits and context evidence | Copilot Session composer; native Turn Usage stays separate |
|
|
130
|
+
|
|
131
|
+

|
|
132
|
+
|
|
133
|
+
This 0.4.0 release-candidate capture uses the built Client with synthetic accounts and models. It shows the Models account controls, the expanded **New Session continuation default**, and exact-ID model preferences including High cost. The default applies only to eligible Sessions created after its policy epoch; it does not enroll existing or seeded histories. This is not live sign-in, model availability or loaded Desktop proof.
|
|
134
|
+
|
|
135
|
+

|
|
136
|
+
|
|
137
|
+

|
|
138
|
+
|
|
139
|
+

|
|
140
|
+
|
|
141
|
+
These Credits captures use the 0.4.0 release-candidate Client and synthetic identities, quota and Session state. The account panel shows **Follow global default** for this Session's account choice; the continuation capture shows the persistent **Session policy → On** disclosure, same-account loss notice and next-turn boundary. No real account or billing data is shown; no message is sent or retried. [Capture provenance](./docs/images/copilot-current-provenance.json) accompanies the images.
|
|
142
|
+
|
|
143
|
+
## Install and sign in
|
|
144
|
+
|
|
145
|
+
Use the exact verified release, the intended profile and an authorized package source. No `copilot2api`, external gateway, pasted GitHub token, placeholder key or separate `dsh-web-search-provider` is required.
|
|
146
|
+
|
|
147
|
+
Before installation, extract the checksum-verified archive and run its **read-only composition preflight** with absolute paths:
|
|
148
|
+
|
|
149
|
+
```sh
|
|
150
|
+
node package/scripts/check-search-composition.mjs --profile-dir /absolute/profile --home /absolute/DSH_HOME --install-anchor /absolute/dsh/package.json
|
|
151
|
+
```
|
|
152
|
+
|
|
153
|
+
Supply any launcher patches with repeated `--patch /absolute/file`. Require `supported: true`: the install command does not automatically run this preflight. Unsupported/custom Web composition and `NONEMPTY_DISPOSABLE_PROFILE_ROOT` are stop conditions. Preserve a nonempty root and review whether public composition reconstructs it before any separately approved normalization; never assume it can be cleared. Check effective shared-peer resolution so stale profile-local packages do not shadow Desktop's official peers.
|
|
154
|
+
|
|
155
|
+
For a **standalone named profile**:
|
|
156
|
+
|
|
157
|
+
```sh
|
|
158
|
+
dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.1.dsh.0.2.1.alpha.5/dsh-github-copilot-0.1.0-alpha.1.dsh.0.2.1.alpha.5.tgz
|
|
159
|
+
```
|
|
160
|
+
|
|
161
|
+
The command above is a prepared-release example, usable only after publication, and requires official DSH `0.2.1-alpha.5`. **Desktop rc.2 must not install alpha.16 or `0.1.0-alpha.1.dsh.0.2.1.alpha.5`**; retain `dsh-github-copilot@0.4.2-alpha.15` there. Candidate Desktop package/signature and profile peer composition remain unverified. The [historical rc.2 bundled-CLI qualification](./docs/npm-distribution.md#desktop-bundled-cli-on-official-rc2) is not alpha.5 acceptance; a generic/global `dsh` shim is not equivalent. No install, restart, registry-policy bypass, peer patch or configuration deletion is authorized by this release.
|
|
162
|
+
|
|
163
|
+
Desktop's native package manager and qualified bundled CLI are profile-specific.
|
|
164
|
+
[Standalone offline maintenance](./docs/npm-distribution.md#controlled-offline-cli-maintenance-for-standalone-profiles)
|
|
165
|
+
is not a workaround for a Desktop-managed/reserved profile.
|
|
166
|
+
|
|
167
|
+
After an approved reload/restart:
|
|
168
|
+
|
|
169
|
+
1. Open **Settings → Models → GitHub Copilot** and select **Sign in with GitHub**. No native provider or manual model definition is needed.
|
|
170
|
+
2. Copy the displayed one-time code and complete GitHub's device flow in your own browser. Desktop uses its system-browser handoff; a selectable verification URL remains available if it does not open.
|
|
171
|
+
3. Wait for **Signed in** and account discovery, then choose a model. Opening Models and normal use ensure missing/stale metadata; **Manage → Refresh models** is an intentional forced refresh, not routine setup.
|
|
172
|
+
|
|
173
|
+
Sign-out requires an explicit action and removes only the active account's authorization, not other saved grants or route settings. Upgrades preserve existing native Copilot profiles; two groups can remain until [explicit single-route migration](./docs/single-route-migration.md). Installation never migrates conversations or defaults.
|
|
174
|
+
|
|
175
|
+
In **Manage → Account management**, the **Switch** dropdown lists saved accounts and **Add GitHub account** at the bottom. Adding never replaces the global default. During device authorization, the card keeps the verification URL, one-time code, **Copy authorization code** and **Cancel adding account** together; identity/model verification follows separately. A confirmed switch changes future inherited turns, not running turns or explicit Session overrides. **Manage saved authorizations** contains **Reauthorize** and **Remove**; removal affects only a nondefault saved authorization, never a running turn's pinned account or GitHub-side access. **Refresh account information** updates identity, not authorization. Native-route or incomplete evidence blocks switching; missing/revoked accounts never fall back. A new account may lack your selected model, and encrypted replay may be account-bound: no automatic model substitution or history removal occurs. See [account requirements](./docs/copilot-accounts.md).
|
|
176
|
+
|
|
177
|
+
Completed managed turns show **Account** beside native Usage. It records the request account, not billing or subagent totals. A verified name is frozen at admission; if missing, an existing bounded non-forcing lookup for that exact account runs without delaying model delivery and can fill identity only while the same turn remains active. No account evidence exists before native delivery. Missing identity remains unavailable; completed history is never backfilled from current settings. Evidence is bounded to the Host lifetime; restart, cold history or missing delivery displays unknown. Credits labels an unidentified original or saved authorization without displaying opaque account IDs.
|
|
178
|
+
|
|
179
|
+
Saved account names can load without activating the account. Names are cached for the Host lifetime, invalidated by credential changes or failed verification, and never prove authorization or model access. A global switch requires fresh identity/model validation and confirmed settings persistence. If switching is blocked, let authorization or pinned work settle and use **Refresh account information**; unknown route/activity evidence remains a blocker. The dropdown, not a button beside each saved account, is the selection control.
|
|
180
|
+
|
|
181
|
+
**Desktop lifecycle:** disable/remove/upgrade can require a full cold restart for Web service recomposition. If the plugin is Off and the native manager reports only `pending (waiting for service: web)`, do not repeatedly toggle or reinstall. Obtain restart approval and follow [rc.2 lifecycle guidance](./docs/web-lifecycle-rc2.md).
|
|
182
|
+
|
|
183
|
+
## Auto and model preferences
|
|
184
|
+
|
|
185
|
+
**Saving preferences:** Exclude/Restore and High cost save immediately with confirmed settings readback. Other rows remain usable: up to 32 distinct-row edits can wait, marked **Waiting…**, while one is **Saving…**. An unconfirmed result or changed scope cancels unsent edits; **Retry** reads saved settings without replaying writes. The queue does not survive unmount.
|
|
186
|
+
|
|
187
|
+
**Provider-directory load failures:** native Models `llm/listProviders failed: Failed to fetch` is a Client-to-Host/gateway transport failure, not proof of forced Copilot discovery. Use the native page's **Retry** after the connection recovers; the plugin does not substitute a stale or empty catalog.
|
|
188
|
+
|
|
189
|
+
All three Auto preferences use the same account-verified, non-excluded eligible pool. Hard input/image capability checks run before soft task preferences.
|
|
190
|
+
|
|
191
|
+
| Task demand | Efficiency | Balance | Intelligence |
|
|
192
|
+
|---|---|---|---|
|
|
193
|
+
| Proven simple | Lightweight | Lightweight | Lightweight |
|
|
194
|
+
| Routine | Lightweight | Versatile | Powerful |
|
|
195
|
+
| Complex | Powerful | Powerful | Powerful |
|
|
196
|
+
| Unknown | Versatile | Versatile | Powerful |
|
|
197
|
+
|
|
198
|
+
Categories come from authenticated supplier metadata, not model names, context capacity or measured quality rankings. Every eligible fitting model retains positive opportunity across categories. The table above is the preferred target, not a hard filter: category factors are target `1`, second `0.25`, third `0.05`, unknown `0.02`, multiplied by cost/recency weights. These are uncalibrated trial coefficients, not fixed category probability quotas; candidate counts also affect shares. The penalty applies to the previous high-cost model, not other marked peers, and resets after a different model's turn. Fit does not prove task success; non-target selection is intentional opportunity, not task-failure escalation. One real answer model stays fixed throughout each admitted turn's steps and retries; compaction preserves its independently resolved native summary route.
|
|
199
|
+
|
|
200
|
+
Semantic assessment is **enabled by default only for locally unknown tasks**. It makes at most one bounded auxiliary call with a **30-second default end-to-end deadline** and **128-token output budget**. Set `github-copilot.autoSemanticAssessment: false` to opt out. The native plugin configuration exposes `autoSemanticAssessmentTimeoutMs` (1000–120000 ms; `8000` restores the old budget) and `autoSemanticAssessmentModel` (empty for automatic selection, or an exact current-account model ID). They apply to subsequent assessments, not admitted retries. An unavailable/excluded/unsuitable explicit classifier reports unavailable, never silently switches. Automatic selection is metadata-driven, not measured optimal; the new default is a trial, not proof of past timeout causes. See [assessment settings](./docs/auto-task-routing.md#using-auto).
|
|
201
|
+
|
|
202
|
+
Timeout/invalid output leaves demand unknown and uses the preference fallback; it never means simple or triggers another classifier. Caller cancellation and account invalidation remain terminal. Auxiliary calls add latency and supplier charges outside native answer Usage.
|
|
203
|
+
|
|
204
|
+
The deadline is checked against a monotonic clock at preparation, native request and result boundaries, even if the event loop delays the timer. Such delays can postpone settlement; they do not authorize late dispatch or late-result acceptance. Eligible Lightweight classifiers must advertise an explicit reasoning-disable mode: `off`, or protocol-native `none` for Responses/Completions or `disabled` for Anthropic. Deterministic ID tie-breaking follows. This is not a measured speed ranking. Explanations distinguish the fitting category pool and previous-model continuity from semantic merit.
|
|
205
|
+
|
|
206
|
+
The auxiliary classifier always requests the protocol's explicit disabled-reasoning mode (`none` for Responses/Completions, `disabled` for Anthropic) and receives no tools. A candidate is not dispatched unless both account metadata and the isolated public adapter model expose that capability; otherwise assessment fails closed. Missing or empty effort metadata is not proof that a model never reasons. The classifier does not inherit configured Chat reasoning effort, and its off mapping is not added to shared account models. Synthetic tests verify the outgoing payload, not supplier-side implementation. One call, bounded text input and 128 requested output tokens constrain overhead without promising a hard credit cap; ordinary Chat reasoning/tools remain unchanged.
|
|
207
|
+
|
|
208
|
+
Classification preserves the current request and a bounded substantive continuation
|
|
209
|
+
anchor before verbose historical output. Incidental historical omission alone no
|
|
210
|
+
longer forces a valid simple/routine result to unknown; missing anchors, limited
|
|
211
|
+
task text and nontext task dependencies still block downshift. The prompt does not
|
|
212
|
+
pre-fill an unknown answer. Assessment details distinguish projection limitations
|
|
213
|
+
from the classifier's returned demand. Unknown remains valid; retained text and
|
|
214
|
+
synthetic regressions do not prove calibrated accuracy or a reduced live unknown rate.
|
|
215
|
+
|
|
216
|
+
Request-local strict selection evidence includes candidate counts and one fixed first-rejection reason per model: exclusion, configured-ID mismatch, category, text input, unproven disable capability or budget. No model IDs are added to these counts. No-fit warnings use fixed codes only, and native off preparation failure is distinguished from selection failure. This evidence is ephemeral, not a new persisted diagnostic population; legacy records without these fields remain unknown.
|
|
217
|
+
|
|
218
|
+
The reply's selection disclosure shows captured reasons and optional content-free auxiliary milestones. `uncertain` and `insufficient-evidence` do not mean the conversation is empty. **Selection unknown** means no retained record; **Selection unavailable → Retry** means the read failed. Retry rereads that turn, not inference. Evidence is bounded and Host-local, so restart/eviction can lose it.
|
|
219
|
+
|
|
220
|
+
When a failed/incomplete turn has no native Usage model row, the existing ⓘ opens **Turn model and selection evidence**: successful same-turn sources show **Recorded models** with incomplete failed-attempt attribution; reliable same-turn recorded request configuration shows **Requested model**, not dispatch, execution or billing proof. Missing evidence stays **Unknown**, never inferred from today's picker/default or adjacent turns. Selection reasons remain in a disclosure underneath. Complete native routes avoid repeated model UI; turns without a closing message have no existing assistant-actions entry. Native Usage and retries are unchanged. [Evidence boundaries](./docs/automatic-model-routing.md#attribution-and-explanation).
|
|
221
|
+
|
|
222
|
+
**Model exclusions** remove exact IDs from the managed picker and new Auto pools. Selected models are excludable: an admitted turn keeps its model, but a new turn/direct request cannot use an excluded ID. A fixed selection is never silently replaced. Unknown preference settings leave controls read-only, not falsely enabled. Saves use narrow native CAS without credentials, discovery or Session scans.
|
|
223
|
+
|
|
224
|
+
See [task assessment](./docs/auto-task-routing.md) and [routing contracts, exclusions and history recovery](./docs/automatic-model-routing.md).
|
|
225
|
+
|
|
226
|
+
Explicit Auto intent survives native pending-selection consumption and cold restore through a plugin-owned projection of existing selection events. Later explicit fixed choices still win for future turns; admitted turns keep their route. This does not backfill historical selection reasons or turn unknown evidence into guessed Auto.
|
|
227
|
+
|
|
228
|
+
## Subagents and search
|
|
229
|
+
|
|
230
|
+

|
|
231
|
+
|
|
232
|
+
This 0.4.0 release-candidate capture shows the built Client's parent-following switch, Web search routing and default-off local diagnostics together. Settings/providers and paused, empty diagnostics are synthetic. No search, collection or live service was invoked for the capture; see [provenance](./docs/images/copilot-current-provenance.json).
|
|
233
|
+
|
|
234
|
+
**Follow parent model** defaults Off and applies profile-wide to supported native children/Team mates of managed Copilot parents. Fixed parents apply on each child's next turn; Auto parents pass the exact preference while each child evaluates its own context. Child-owned explicit selections win. Running turns, roots, forks, other providers and dedicated legacy policies are not rewritten. Existing legacy bindings remain independent when the broad switch is Off. [Parent-following contract](./docs/parent-model-follow.md).
|
|
235
|
+
|
|
236
|
+
**Web search** has two ordinary controls in the plugin-detail page: primary provider and final fallback. Routing can be saved without Copilot sign-in or account-model discovery; the choices must be registered search providers. Saving only records routing and does not prove Copilot search capability, which is checked when a search runs. Auto follows the initiating Chat provider when a corresponding search registration exists; fixed choices stay fixed when Chat changes. At most one distinct final fallback is tried, with possible charges disclosed. Cancellation/account-proof loss never authorizes a fallback.
|
|
237
|
+
|
|
238
|
+
Copilot search requires current account/protocol evidence and capability proof. Fixed/fallback Copilot preserves a nonempty legacy `searchModel`; otherwise it considers at most three account-owned Responses candidates. The final user query is sent once, never replayed across those candidates. A saved choice or successful Chat request does not prove hosted search. [Search routing and composition](./docs/session-search-routing.md).
|
|
239
|
+
The legacy `github-copilot.searchFallback` setting applies only to its separate
|
|
240
|
+
canonical inline path; it is not a third routed fallback. Fetch is unchanged.
|
|
241
|
+
|
|
242
|
+
## Usage, request limits and recovery
|
|
243
|
+
|
|
244
|
+
**Credits** shows validated account billing-cycle data, not context tokens or Session cost. Stale, pooled and unavailable readings keep their real meanings. The quota request alone uses Node plus system CA roots with TLS verification enabled; it does not change trust for sign-in, models, search or Desktop globally.
|
|
245
|
+
|
|
246
|
+
Native context occupancy and Turn Usage remain Core-owned. The plugin forwards usage unchanged, including zero samples on failure/cancellation. Ordinary in-progress requests and missing new samples stay quiet; only a concrete failed-zero or invalid-sample incident opens the separate, dismissible context warning. Any retained count is labeled historical evidence, never current occupancy or a replacement percentage. **Turn Usage incomplete** explains missing samples/lifecycle and recorded local blocks; it invents neither zero usage nor partial totals. Cancellation can retain usage, but does not guarantee a final supplier receipt. [Usage boundaries](./docs/copilot-usage.md).
|
|
247
|
+
|
|
248
|
+
Owned timeout/replay errors preserve native usage before terminal failure restoration, including nonzero samples. A failed zero can still make the native ring show `0%`; this is not proof of an empty request. Retry-entry times describe backoff, not the failed request's duration. These accounting fixes do not cure supplier HTTP 408 or change retry policy.
|
|
249
|
+
|
|
250
|
+
Compaction planning prices model-facing content and tools, not native IDs/provenance or opaque replay envelopes, avoiding metadata-driven exhaustion of the 16-call limit. The original messages/replay remain unchanged; final native admission still checks converted input. A typed capacity fallback keeps fixed prefixes and balanced tool units, never repeats an indivisible rejected input. This is conservative planning, not provider-exact token accounting.
|
|
251
|
+
|
|
252
|
+
Managed request admission preserves truthful input/output limits and native transactions. Automatic pressure uses the initiating Agent's actual bound compaction service; a preset without an engine cannot borrow global recovery. The separately selected [recovery engine](./docs/manual-compaction-recovery.md) defaults to automatic segmented fallback for oversized summaries or an explicit summary context-limit failure. Fitting summaries stay native; timeout/408/auth/quota failures do not trigger segmentation. Up to 16 calls may add time and charges; cancellation or incomplete recovery never commits a partial summary. `automaticRecovery: false` disables this fallback; native `auto: false` still disables automatic compaction. Installation alone does not select the engine: follow the explicit same-scope configuration migration, preserving preset/custom-engine ownership and existing policies.
|
|
253
|
+
|
|
254
|
+
For continuing steps with a committed managed route and no pending model change, known input pressure is reduced before Core opens the next model attempt. Successful native reduction avoids an unsampled local-pressure attempt that would make whole-turn Usage unavailable. First steps, pending selections, new fixed-prefix growth and final hard-budget refusals retain existing admission; this does not repair historical totals or invent missing usage.
|
|
255
|
+
|
|
256
|
+
**Visible-history continuation also covers this Session's native managed Responses compaction**, including automatic summaries: no extra manual recovery command or failure-first retry is required when enabled. Old encrypted reasoning and embedded summaries are omitted from outgoing input; hidden context may be lost. Visible messages/tool pairs and source history remain intact, and only the native transaction commits a smaller checkpoint. A composer notice identifies degradation and distinguishes committed, failed and cancelled outcomes. When off, an exact replay-scope rejection offers the same loss-disclosed enable control; unknown failures do not authorize loss. `/copilot-compact visible-history` remains a one-time alternative through the selected recovery engine. Read [recovery consent and limits](./docs/manual-compaction-recovery.md#explicit-visible-history-summary-recovery); this does not enable an absent engine or repair capacity, quota or timeout failures.
|
|
257
|
+
|
|
258
|
+
Compaction feedback separates **compaction completed** and **subsequent request succeeded** during the existing eight-second result window. It does not turn ordinary request progress or absence of a fresh sample into a persistent composer warning. A later concrete sampling incident can appear independently and may include a labeled historical count, but never an occupancy percentage. The plugin sends no extra test request, adds no retry and leaves the native context ring, Usage accounting and expandable compaction history unchanged. See [context evidence](./docs/copilot-usage.md#historical-context-evidence).
|
|
259
|
+
|
|
260
|
+
Running visible-history compaction notices stay visible. Confirmed success disappears eight seconds after first observation; settled failures, cancellation, unavailable status and enable prompts stay until **Close** (or the existing **Cancel**). Closing only hides this Session/operation/status notice, never changes consent, history or native proof, and never sends or retries. A bounded Client registration retains expiry/dismissal across incidental remounts and Session switches, not across teardown or eviction.
|
|
261
|
+
|
|
262
|
+
For exact verified `408 / user_request_timeout`, diagnostics describe bounded request composition and observable timing, not a proven payload limit or root cause. Image counts include native Responses tool outputs; older stored diagnostics may have counted those images as residual history. Bytes are not tokens; timing is not upload duration. Small, image-free requests can also time out. Follow [request-budget and timeout guidance](./docs/copilot-compaction.md); do not automatically trim history, disable proof, switch models or add retries.
|
|
263
|
+
|
|
264
|
+
The experimental `github-copilot.responsesRequestCompression` option is **off by default**. When explicitly enabled, it losslessly gzips only eligible managed HTTP Responses requests through the existing native Fetch seam. It starts at 256 KiB, skips compression work above 32 MiB and requires at least 5% and 4 KiB savings; every skip sends the original request. This changes prepared HTTP body bytes, not context/token admission. Custom Fetch, explicit `auto`/WebSocket and other protocols remain native, and a gzip rejection is never automatically resent uncompressed. On a verified 408, diagnostics distinguish original JSON composition from the prepared gzip body size; neither proves delivery or cures every timeout. Installation does not enable the option.
|
|
265
|
+
|
|
266
|
+
The same failure can include request-scoped native local body-write/header milestones, negotiated TLS ALPN and a Node writable-buffer count. These are local submission observations, not kernel ACK or supplier receipt; missing events do not prove an incomplete upload. Unsupported or ambiguous transports report unavailable evidence. No request contents are logged and no connection, proxy, dispatcher or retry is changed.
|
|
267
|
+
|
|
268
|
+
HTTP/SSE liveness separates five-minute byte idle from bounded ten-minute assistant-output silence by default. Consumer work is excluded; WebSocket/explicit `auto` stays native-only. This does not cure supplier HTTP 408s. Images are admitted against actual native-projected MIME evidence; the plugin does not own conversion or infer format support from filenames. [Image compatibility](./docs/image-input-compatibility.md).
|
|
269
|
+
|
|
270
|
+
Native rc.2 Auto authorization review requests `temperature: 0`. The plugin now automatically omits it **only for the authenticated official Auto reviewer root on account-discovered managed OpenAI Responses**; no switch is needed. Concurrent ordinary Chat, even on the same Session/model, retains its temperature. Public Loader callback identity and same-profile package ownership authenticate the caller; unknown identity, aliases, descendants, other protocols/providers and canonical Core-owned Copilot remain native, with bounded diagnostics for unqualified reviewer scope. No capability is inferred from `supports.thinking`. Frozen inputs, native account/cancellation guards, strict verdicts and fail-closed tool denial remain intact; no retries, permission changes or settings migration occur. The independent legacy `github-copilot.responsesOmitTemperature` override remains default `false`; explicit `true` still omits temperature from **all** managed Responses requests, not just review. See [public scope and qualification limits](./docs/auto-review-sampling.md).
|
|
271
|
+
|
|
272
|
+
## Settings and troubleshooting
|
|
273
|
+
|
|
274
|
+
Configuration is under `github-copilot`. Credentials, endpoint definitions and a static model catalog are not plugin settings.
|
|
275
|
+
|
|
276
|
+
| Key | Default | Purpose |
|
|
277
|
+
|---|---:|---|
|
|
278
|
+
| `autoSemanticAssessment` | `true` | One auxiliary assessment for locally unknown Auto tasks |
|
|
279
|
+
| `followParentModel` | `false` | Supported child following; explicit child selections win |
|
|
280
|
+
| `excludedModelIds` | `[]` | Exact exclusions through Model preferences |
|
|
281
|
+
| `accountModelTtlMs` | `86400000` | 24h maximum metadata reuse, not token/proof validity |
|
|
282
|
+
| `accountModelFailureCooldownMs` | `300000` | 5min non-forcing discovery failure cooldown |
|
|
283
|
+
| `chatStreamLiveness` | `true` | Managed HTTP/SSE byte observation |
|
|
284
|
+
| `chatStreamIdleTimeoutMs` | `300000` | Byte-idle deadline; separate from search |
|
|
285
|
+
| `responsesRequestCompression` | `false` | Experimental lossless gzip for eligible managed HTTP Responses requests |
|
|
286
|
+
| `responsesOmitTemperature` | `false` | Explicitly omit temperature from every managed Responses request |
|
|
287
|
+
| `chatMaxRequestImageBytes` | `20971520` | Native 20 MiB outgoing-image budget, not a total JSON limit |
|
|
288
|
+
| `requestBudgetSafetyTokens` | `4096` | Estimated input safety allowance |
|
|
289
|
+
| `requestBudgetPressureRatio` | `0.9` | Early pressure with supported enabled recovery |
|
|
290
|
+
| `compactionReasoning` | `prefer-low` | Supported low effort only when none is resolved |
|
|
291
|
+
| `enabled` / `probe` | `true` / `true` | Hosted search / capability proof |
|
|
292
|
+
| `providers` | `[]` | Optional explicit search route allowlist |
|
|
293
|
+
| `includeSources` / `stripServerTools` | `true` / `true` | Inline citations / hosted-tool schema handling |
|
|
294
|
+
| `idleTimeoutMs` / `probeTimeoutMs` | `300000` / `30000` | Search request / probe deadlines |
|
|
295
|
+
|
|
296
|
+
| Symptom | Next safe action |
|
|
297
|
+
|---|---|
|
|
298
|
+
| No sign-in controls | Check active profile and loaded Host/Client; do not add a native provider merely to reveal login |
|
|
299
|
+
| Signed in, missing models | Inspect discovery diagnostics; use visible Retry or intentional Refresh, not repeated sign-in |
|
|
300
|
+
| Two Copilot groups | Review [explicit migration](./docs/single-route-migration.md); no automatic removal |
|
|
301
|
+
| Selection unknown/unavailable | Distinguish lost evidence from read failure; Retry only rereads |
|
|
302
|
+
| Missing/cancelled Turn Usage | Read [usage limitations](./docs/copilot-usage.md); do not infer zero billing |
|
|
303
|
+
| History fails on `github-copilot/auto-model-decision` | Use [detached, check-first recovery](./docs/automatic-model-routing.md#recovering-affected-histories); never replace live history without stopped writers and approval |
|
|
304
|
+
| AUTH, Responses replay-scope or TLS failure | Review [request diagnostics](./docs/model-compatibility-acceptance.md#authentication-replay-and-request-diagnostics) and [usage TLS boundaries](./docs/copilot-usage.md#account-data-boundary). After an exact scope rejection, **Replay recovery** shows the same persistent Session continuation policy: when off, disclose loss and offer **Enable visible-history continuation** or Cancel; when already on, show diagnostic guidance without repeated authorization. No duration or next-turn-only choice. Evidence expiry does not disable the policy. Use native Retry separately; no automatic send/retry or history rewrite, and not a 408 fix. Never reset credentials or disable TLS as an automatic repair. |
|
|
305
|
+
| Hosted search unavailable | Check account/protocol/probe diagnostics; a legacy override stays authoritative until explicitly reset |
|
|
306
|
+
|
|
307
|
+
Confirmed account saves restore controls immediately, independently of quota loading. Changing only follow mode for the same account retains its attributed quota without another read. Switching accounts clears the old quota and loads the new snapshot without blocking further account edits; quota errors do not undo a confirmed selection.
|
|
308
|
+
|
|
309
|
+
The Credits account panel shows the current account and **Switch account**. Its dropdown lists only configured accounts, marks the effective account and scrolls long lists internally. **Follow global default** is a separate checkbox for the account only—not the global model choice: enabling it clears this Session's account override; disabling it fixes the current account. Choosing any account also fixes it, even if it is today's default. The choice affects subsequent turns in this Session, not a running turn or another Session. Both actions retain continuation confirmation and revision-checked saving. Account addition belongs only in Models, where one **Manage** disclosure contains account management and shared model preferences. Models retains Add in its dropdown footer without selecting the new account, plus guarded local removal and reauthorization. Neither surface has account search. Exact-ID exclusions are shared across accounts; availability is account-specific. See the [approved experience and interactive mock](./docs/account-management-experience.md).
|
|
310
|
+
|
|
311
|
+
[Visible-history continuation](./docs/session-continuation.md) has two controls: **Manage → New Session continuation default** sets what eligible new Sessions inherit; **Credits → Visible-history continuation → Session policy** controls the current Session. The initial default-on epoch is recorded at first successful activation. Only new, unseeded Sessions created after that epoch inherit it; existing, seeded/forked, or unknown histories are not enrolled retroactively. Changing the global default affects future Sessions only.
|
|
312
|
+
|
|
313
|
+
The name “New Session” describes default inheritance, not a one-message feature: an enabled Session policy is frozen at admission for each subsequent managed Copilot turn and also governs that Session's managed native compaction summaries. For an existing eligible Session, select the managed Copilot model, open the composer **Credits/usage** pill, expand **Visible-history continuation**, then choose **On** in **Session policy**. This control appears only for an open Session using the managed account-discovered route; it is not shown for the canonical/native route. The loss disclosure is shown before the choice. Enabling is explicit consent to omit prior encrypted reasoning and embedded summaries, even on the same account; hidden details may be lost, while visible messages, tool relations and source history remain. The policy persists across account switches and restarts until changed. It takes effect on the next turn; an already admitted turn keeps its captured policy. With continuation off, switching to a different account offers persistent enable, keep off or cancel—there is no next-turn-only choice. `/copilot-compact visible-history` is a separate one-time operation through the selected recovery engine, not the persistent Session setting. Neither path auto-sends/retries or cures quota/context limits; exact replay failures use the same persistent Session policy and require a separate native retry. The pinned Core lacks a public Models deep link, so Chat omits the nonfunctional management entry.
|
|
314
|
+
|
|
315
|
+
Context evidence and Replay recovery use compact, centered notices bounded by the native composer width. Model/item counts and status refresh live in collapsed technical details; loss consent remains explicit. Context sampling warns only for a concrete incident, can be dismissed for that Session/incident, and never asserts the native meter's current value; native statistics stay unchanged. Switching accounts does not make old encrypted reasoning portable. The concise scope error points to explicit recovery or a new conversation; bounded, sanitized dispatch counts stay in Host diagnostics, not the main error. **Authorized** means permission is ready, not that a message was sent or recovery succeeded.
|
|
316
|
+
|
|
317
|
+
## Ownership and further reading
|
|
318
|
+
|
|
319
|
+
DSH Core owns Sessions, tools, sandboxing, attachments, native accounting and other providers. `llm-pi-ai` owns OAuth, token exchange/refresh and normal model transport. This plugin composes the published adapter with authenticated account metadata; new supported account model IDs need no name-based routing patch. Credentials stay Host-only: `llm-pi-ai/github-copilot` is the canonical compatibility record; additional accounts are independently authorized plugin-owned records in the same DSH credentials service, never copied grants.
|
|
320
|
+
|
|
321
|
+
Public APIs cannot replace Core Edit/Delete, restructure its flat picker or make native Add a single-route enforcement mechanism. Retired [Model roles](./docs/dual-model.md) remain compatibility-only. Fixes must stay [plugin-only](./AGENTS.md#plugin-only-implementation-boundary).
|
|
322
|
+
|
|
323
|
+
| Guide | Scope |
|
|
324
|
+
|---|---|
|
|
325
|
+
| [Compatibility acceptance](./docs/model-compatibility-acceptance.md) | Metadata, reasoning, replay and public-interface limits |
|
|
326
|
+
| [Current official-first review](./docs/official-first-020-rc2.md) | Exact rc.2 seams and retained gaps |
|
|
327
|
+
| [Migration](./docs/single-route-migration.md) | Fresh read-only readiness and explicit config-only maintenance |
|
|
328
|
+
| [Distribution](./docs/npm-distribution.md) | Same-byte GitHub/npm publication and qualified installation |
|
|
329
|
+
| [Agent guide](./AGENTS.md), [contributing](./CONTRIBUTING.md) | Owners, task plans, gates and delivery policy |
|
|
330
|
+
|
|
331
|
+
Version history belongs in [CHANGELOG.md](./CHANGELOG.md) and immutable [Releases](https://github.com/cloga/dsh-github-copilot/releases), not the setup instructions. `deployment-baseline.json` retains historical pins without admitting them as current support.
|
|
332
|
+
|
|
333
|
+
## Build and verify
|
|
334
|
+
|
|
335
|
+
Use Node 24 LTS and the exact pnpm version in `package.json`; runtime Node must be >=22.19.0.
|
|
336
|
+
|
|
337
|
+
```sh
|
|
338
|
+
pnpm install --frozen-lockfile
|
|
339
|
+
pnpm verify
|
|
340
|
+
pnpm pack --pack-destination artifacts
|
|
341
|
+
pnpm verify:tarball -- artifacts/dsh-github-copilot-<package-version>.tgz
|
|
342
|
+
```
|
|
343
|
+
|
|
344
|
+
`pnpm verify` covers contracts, types, baseline, build, tests and built entry smoke. Required CI targets unchanged official rc.2 source and published artifacts on Windows/Linux. Passing synthetic tests does not prove live account/model/search behavior.
|
|
345
|
+
|
|
346
|
+
Agents start with `node scripts/agent.mjs describe --json`, `doctor --json` and `plan <task> --json`; plans are unexecuted arguments, not action approval. Follow [AGENTS.md](./AGENTS.md) for the full change/release policy. Important updates require protected merge and verified dual-channel publication; documentation-only work does not release by default. Profile installation, sign-out and session-interrupting restart need separate authorization.
|
|
347
|
+
|
|
348
|
+
Commit attribution uses `Assisted-by` with the actual tool, never the model provider or an unverified collaborator identity.
|
|
349
|
+
|
|
350
|
+
## Release and checksum verification
|
|
351
|
+
|
|
352
|
+
GitHub Releases and npm distribute the same original verified tarball. Pin a version; verify Release SHA-256 or npm `dist.integrity`. Never repack an immutable release or move/reuse its tag.
|
|
353
|
+
|
|
354
|
+
```sh
|
|
355
|
+
curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.1.dsh.0.2.1.alpha.5/dsh-github-copilot-0.1.0-alpha.1.dsh.0.2.1.alpha.5.tgz
|
|
356
|
+
curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.1.dsh.0.2.1.alpha.5/SHA256SUMS
|
|
357
|
+
sha256sum --check SHA256SUMS
|
|
358
|
+
```
|
|
359
|
+
|
|
360
|
+
```powershell
|
|
361
|
+
$expected = (Get-Content .\SHA256SUMS).Split()[0]
|
|
362
|
+
$actual = (Get-FileHash .\dsh-github-copilot-0.1.0-alpha.1.dsh.0.2.1.alpha.5.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
|
|
363
|
+
if ($actual -cne $expected) { throw 'Release checksum mismatch' }
|
|
364
|
+
```
|
|
365
|
+
|
|
366
|
+
Checksums detect corruption/drift; protected workflows and repository controls establish publisher provenance. Report vulnerabilities privately through [SECURITY.md](./SECURITY.md).
|