dsh-github-copilot 0.1.0-alpha.3.dsh.0.2.1.rc.3 → 0.1.0-alpha.3.dsh.0.2.2.rc.3

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.
Files changed (51) hide show
  1. package/AGENTS.md +139 -8
  2. package/CHANGELOG.md +38 -0
  3. package/CONTRIBUTING.md +4 -0
  4. package/README.md +121 -368
  5. package/README.zh.md +86 -330
  6. package/cordis.patch.yml +0 -13
  7. package/deployment-baseline.json +121 -268
  8. package/docs/agent-readiness.md +1 -1
  9. package/docs/auto-high-cost.md +4 -0
  10. package/docs/auto-review-sampling.md +27 -4
  11. package/docs/auto-task-routing.md +4 -0
  12. package/docs/automatic-model-routing.md +4 -0
  13. package/docs/copilot-accounts.md +1 -1
  14. package/docs/copilot-usage.md +16 -4
  15. package/docs/dual-model.md +13 -8
  16. package/docs/model-compatibility-acceptance.md +97 -187
  17. package/docs/plugin-diagnostics.md +16 -40
  18. package/docs/session-search-routing.md +4 -0
  19. package/docs/web-lifecycle-rc2.md +19 -10
  20. package/lib/client.js +2696 -1644
  21. package/lib/client.js.map +1 -1
  22. package/lib/{copilot-identity-DRZY_d2X.js → copilot-identity-BF8J8-9O.js} +1 -4
  23. package/lib/diagnostics-analysis.js +1 -1
  24. package/lib/{diagnostics-types-CF-qg8Do.js → diagnostics-types-eEWwFOFD.js} +2 -42
  25. package/lib/index.js +1292 -4819
  26. package/lib/manual-compaction-recovery.js +2 -2
  27. package/lib/remote.js +7 -1
  28. package/lib/routed-web.js +9 -4
  29. package/lib/traditional-search-CgIL4oRu.js +114 -0
  30. package/lib/types/auto-model-presentation.d.ts +4 -0
  31. package/lib/types/client.d.ts +1 -3
  32. package/lib/types/compatibility.d.ts +5 -5
  33. package/lib/types/context-evidence.d.ts +4 -4
  34. package/lib/types/copilot-usage-host.d.ts +5 -0
  35. package/lib/types/copilot-usage-remote.d.ts +3 -0
  36. package/lib/types/copilot-usage-types.d.ts +1 -1
  37. package/lib/types/index.d.ts +2 -15
  38. package/lib/types/model-preferences-card.d.ts +1 -1
  39. package/lib/types/native-copilot-access.d.ts +16 -0
  40. package/lib/types/native-copilot-search.d.ts +5 -0
  41. package/lib/types/preview-route.d.ts +2 -1
  42. package/lib/types/responses-replay-compat.d.ts +21 -1
  43. package/lib/types/session-continuation-ui.d.ts +1 -0
  44. package/lib/types/tool-schema-compat.d.ts +4 -14
  45. package/lib/types/traditional-search.d.ts +3 -1
  46. package/lib/types/turn-selection-card.d.ts +2 -1
  47. package/package.json +73 -72
  48. package/scripts/check-search-composition.mjs +14 -38
  49. package/lib/search-routing-CV2hs8as.js +0 -792
  50. package/lib/types/parent-model-follow-card.d.ts +0 -32
  51. package/output/auto-model-mockup/index.html +0 -207
package/AGENTS.md CHANGED
@@ -22,16 +22,83 @@ This repository follows a **plugin-only** policy: implement fixes in `dsh-github
22
22
  2. Read this file, then `node scripts/agent.mjs describe --json`. `agent-contract.json` maps each task to its owning files, focused tests, risks and approval boundaries; package scripts and release URLs are derived from current metadata.
23
23
  3. Run `node scripts/agent.mjs doctor --json` before install. It is a dependency-free, read-only repository preflight: exit 0 means preflight passed, 1 means prerequisites missing, 2 means invalid arguments/metadata. Build presence is not build freshness, and no live DSH or credential readiness is claimed.
24
24
  4. Choose a task with `node scripts/agent.mjs plan models --json` (or authorization/search/client/compatibility/tooling/release). Output is an unexecuted argv plan, never implicit permission to run destructive operations.
25
- 5. Use Node 24 LTS for development and the exact pnpm version in `package.json`; the runtime dependency floor is Node 22.19.0. Run frozen install in this checkout. Dependencies/build output are not carried into worktrees.
25
+ 5. Use Node 24 LTS for development and the exact pnpm version in `package.json`; the runtime dependency floor is Node 22.19.0. Select the execution environment and task explicitly with `node scripts/agent.mjs guard`. Local auxiliary checks are limited to the guarded dependency-free script tests; dependency installation and full verification belong to GitHub Actions. Do not retry local dependency restoration, change registries, or treat local reports/idle sessions as CI evidence. The guard applies only to operations routed through it; it cannot prevent direct shell bypass.
26
26
  6. Create/reuse a tracking issue and feature branch, implement a regression first, run the full gate, inspect the diff, and open a PR. For requested delivery, merge after required review/CI and branch protection without a separate approval prompt, unless the user limits scope. Important updates continue through the release-delivery rule below. Live-profile install and worktree checkout still require explicit user approval.
27
27
 
28
28
  Use native DSH tools for goals, background jobs and scoped subagents. Use local Git and the GitHub REST API for delivery; no external orchestration daemon, roster or `vcs_*` tool is required. Do not assume a model provider's identity is the assisting agent.
29
29
 
30
30
  ## Product and architecture
31
31
 
32
- `dsh-github-copilot` currently admits and targets only official DSH `0.2.1-rc.3`, a prerelease. The prior thirteen DSH pins remain in `deployment-baseline.json` as historical evidence, not current support or CI release gates. Rc.3 source/artifact CI qualification passed on Windows/Linux in run `40098031196`; Desktop artifacts/signatures remain unverified. Do not treat this unpublished candidate as a production Core upgrade recommendation. The signed rc.2 Desktop evidence is historical peer ownership only. Rc.2 installations must retain alpha.15 or their existing compatible plugin. It does not own a general Copilot chat adapter. DSH's built-in `llm-pi-ai` mount owns the GitHub Copilot provider, catalog, OAuth method and grant format, token exchange, refresh, and normal model transport.
33
-
34
- This repository maintains twelve narrow surfaces and ownership boundaries:
32
+ ### Confirmed product scope (#455, #456)
33
+
34
+ The native enhancement request (#460/#461) adds only reviewer-scoped Responses
35
+ sampling compatibility and an optional canonical-account hosted-search backend.
36
+ Use public native ownership/configuration proof and prepared dispatch; never
37
+ replace Web, select a backend, migrate accounts/settings, or bypass review.
38
+ Search permits one fixed capability proof and one final query within 25 seconds,
39
+ with four concurrent operations and configuration/credential/disposal fences.
40
+ The former plugin routing UI and managed Auto remain retired. Supplier calls,
41
+ live installation and restarts are separate from synthetic CI acceptance.
42
+
43
+ The user-confirmed direction on 2026-11-14 supersedes conflicting legacy feature
44
+ requirements below: this plugin is a lightweight GitHub Copilot model integration
45
+ for DSH Desktop, not a second agent product. The qualification target is the exact
46
+ official DSH `0.2.2-rc.3` source and published package graph; it is a candidate,
47
+ not supported or delivered until the required CI gates pass.
48
+
49
+ DSH owns application login, AgentLoop, model selection, Auto, parent-model
50
+ following, subagents, tools, Web, permissions, history, context/compaction, and
51
+ Usage. The plugin owns only Copilot's native OAuth/credential integration,
52
+ account-proven model and capability discovery, published-adapter composition,
53
+ and narrowly evidenced Copilot compatibility. Do not add a DeepSeek login check,
54
+ read DeepSeek credentials, add another Copilot login or wire, or redirect failed
55
+ Copilot calls to another provider.
56
+
57
+ Parent/child relationships, inheritance, delegation, lifecycle and scheduling
58
+ follow DSH's native contract, not a plugin-defined policy. Subagent compatibility
59
+ means supplying models to that existing flow. Do not add a child-account
60
+ inheritance mode, parent lookup as credential authority, or plugin-owned child
61
+ routing. Verify authentication and request isolation through the same provider
62
+ contract used by ordinary native calls. A missing public seam is a concrete
63
+ compatibility limit to report, not permission to invent a parallel relationship.
64
+
65
+ Retire plugin-owned Auto and parent-follow policy/UI and custom hosted-search
66
+ execution/routing. Old conversation continuity is not an acceptance requirement.
67
+ Retain GitHub Copilot account quota and useful
68
+ enhancements; remove other functionality only when it is demonstrably redundant
69
+ or unnecessary, not merely because it extends the basic model route. Never delete
70
+ or rewrite user settings, accounts, or history, silently substitute a model, or
71
+ claim a native replacement until the
72
+ exact public API and behavior are verified. Preserve necessary Copilot
73
+ authentication, account/turn isolation, request correctness, and actionable
74
+ diagnostics. HydraFusion/Max are explicitly out of scope (#441).
75
+
76
+ Model-facing DSH capabilities added over time, including native subagent model
77
+ selection and actual child invocation (#456), are compatibility goals for
78
+ account-available Copilot models. Verify each against exact public Core APIs and
79
+ supplier-advertised capabilities with focused tests. Unknown metadata or
80
+ unsupported behavior must fail or diagnose explicitly; do not infer support,
81
+ add model-ID routing rules, patch Core, or claim untested parity.
82
+
83
+ When any later legacy detail in this guide conflicts with this confirmed scope,
84
+ follow this section and the current acceptance criteria in #455/#456.
85
+
86
+ The user clarified that the ordinary route should be DSH's native
87
+ `github-copilot` provider, with only useful plugin enhancements through public
88
+ APIs. Retire the separate managed route when native-route acceptance is met;
89
+ do not preserve it solely to continue old conversations or create a history
90
+ migration. Existing stored conversations, credentials and settings are not
91
+ authorized for deletion or rewriting. Explicitly document that old managed
92
+ route selections may become unavailable. Native model selection and actual
93
+ subagent invocation must be verified on `github-copilot`, not inferred from
94
+ managed-route tests. Record enhancements that cannot safely attach to native
95
+ APIs rather than patching Core or misrepresenting support.
96
+
97
+ The last qualified release line is official DSH `0.2.1-rc.3`; its source/artifact CI passed on Windows/Linux in run `40098031196`, while Desktop artifacts/signatures remain unverified. DSH `0.2.2-rc.3` is the current requested candidate and has not passed this repository's required CI. The previous thirteen pins remain historical evidence, not current support or release gates. Do not treat either prerelease as a production Core upgrade recommendation. DSH's built-in `llm-pi-ai` owns the canonical GitHub Copilot provider, OAuth, grant format, token exchange, refresh, and normal model transport.
98
+
99
+ The following is a historical architecture inventory, not a requirement to keep
100
+ every surface as a product feature; apply the confirmed scope above when deciding
101
+ which runtime registrations, UI, and settings remain active:
35
102
 
36
103
  1. A conditional authorization-service bootstrap plus Host controller that joins DSH authorization, credentials, and settings.
37
104
  2. A Client Models provider-card contribution with one shared account-state owner, Client-safe Remote descriptors and a nested plugin-owned model-preferences disclosure; embed in an existing configured canonical row, suppress its separate footer controller, and retain footer/old-Core section fallback when no such row is mounted.
@@ -317,6 +384,60 @@ Desktop plugin upgrades do not necessarily reconcile profile-local copies of Hos
317
384
 
318
385
  ## Mechanical verification
319
386
 
387
+ When a task explicitly requires post-upgrade Desktop/UI acceptance, use acceptance
388
+ contract/report schema 2 described in `docs/agent-acceptance.md`. Exact-head CI
389
+ and installed-on-disk evidence cannot replace live behavior or the public loaded
390
+ plugin version. Attempt safe authorized checks on an already-running Desktop;
391
+ unreliable local npm is not a reason to skip them. Use existing computer-use
392
+ tools, never shell activation or a repository script as an App controller.
393
+ Begin with current app discovery, not a historical "already open" claim. If not
394
+ running, start only with explicit launch authorization via controlled `start_app`
395
+ using the exact approved target; then verify discovery and fresh UI, not merely
396
+ the launch receipt. Do not start an already-running app again. A welcome screen
397
+ is not automatically an auth blocker: inspect an official safe skip first. DSH's
398
+ Add API Key -> Set up later path does not submit/store a key or authenticate;
399
+ use it only when actually exposed, within tool permission rules. Never infer
400
+ Copilot account invalidity from welcome UI or bypass real authentication/warnings.
401
+ Welcome dismissal may replace the window: rediscover app/window and read its fresh
402
+ tree before acting, rather than retrying a stale window on an empty immediate diff.
403
+ Honor user-input interruption: reread UI before retrying the same permitted action.
404
+ Before handoff, freshly discover the current app and inspect the target panel or
405
+ workspace, reporting the observation time only; past success does not establish
406
+ current running state or guarantee the app remains running later.
407
+ An action receipt or empty immediate diff is not a navigation failure: obtain
408
+ a fresh post-action `get_window_state` observation first. Keep one attempt per
409
+ supported navigation method, at most two different methods, then report precise
410
+ `automation-blocked` and request the named panel once. User absence or an
411
+ unanswered request never grants permission or proves the panel opened.
412
+ App unavailable, restart/install, account/OAuth/paid actions outside explicit
413
+ permission stay blocked. Do not repeat exhausted methods on ordinary continuation.
414
+ Record only fixed action/outcome codes, numeric times and version/source facts;
415
+ never upload identities, credentials or conversation content. Unknown loaded
416
+ version permits qualified observations only, not a version-specific fix claim.
417
+ For formal upgrade acceptance, prefer the published exact-version GitHub Release
418
+ asset canonical URL, never a local source directory, build, link or worktree.
419
+ A downloaded official tgz is a verified GitHub cache, not a local build; use it
420
+ only as a documented fallback when native URL delivery is unavailable/rejected.
421
+ Record exact source URL/version, archive and Release SHA-256, numeric observation
422
+ time and fixed fallback reason separately. Matching hashes do not grant install
423
+ or restart permission or prove the resulting runtime loaded. The consistency
424
+ checker never downloads/installs or independently authenticates this provenance.
425
+ Missing/not-run/blocked/error/timeout mandatory evidence cannot pass acceptance; even a
426
+ consistent complete report is not trusted proof of execution or automatic closure.
427
+ Keep required-check completeness separate from issue disposition. Controlled
428
+ regressions can exercise timers, never-resolving requests, late results and
429
+ simulated disconnects; production Desktop fault injection is different. Do not
430
+ disconnect networking, alter proxies/accounts or trigger paid requests to fill
431
+ coverage without specific permission. After a specific defect is fixed, relevant
432
+ controlled regressions/exact CI pass, release/install/load premises are met and
433
+ normal live checks do not reproduce it, explicit user risk acceptance may close
434
+ with "fixed/not reproduced; untested faults listed; reopen on recurrence".
435
+ Do not claim the original root cause or production fault coverage was proven.
436
+ Lack of safe/non-destructive production injection alone is not an indefinite
437
+ closure blocker. Known failures/reproduction, critical safety gaps and mandatory
438
+ requirements remain blockers; residual-risk disposition cannot relabel them
439
+ passed or authorize automatic issue closure.
440
+
320
441
  For the opt-in task acceptance pilot, define observable requirements before
321
442
  implementation and validate the clean candidate with
322
443
  `node scripts/agent.mjs accept --contract CONTRACT_FILE --report REPORT_FILE`.
@@ -327,10 +448,20 @@ live diagnostics automatically. Failed, blocked and not-run requirements cannot
327
448
  pass; new commits require new evidence. Existing review/CI/release gates remain
328
449
  authoritative. This tooling does not activate agents or access live profiles.
329
450
 
330
- Run from the repository root:
451
+ Choose a bounded local auxiliary check or authoritative remote evidence explicitly
452
+ with `node scripts/agent.mjs guard --task TASK_ID --environment local-auxiliary
453
+ --operation scripts-test` or `--environment github-actions-evidence
454
+ --operation ci-evidence --head FULL_COMMIT_SHA`. The dependency-free scripts
455
+ tests are the only guarded local verification here. Do not run dependency
456
+ installation/recovery locally; full install, build, types, integration and
457
+ package verification use the existing GitHub Actions workflow. See
458
+ [environment and CI evidence guardrails](./docs/environment-evidence-guardrails.md).
459
+ The guard covers only operations invoked through this entry point and is not a
460
+ shell sandbox.
461
+
462
+ The full gate and package commands, run by the existing CI workflow, are:
331
463
 
332
464
  ```sh
333
- pnpm install --frozen-lockfile
334
465
  pnpm verify
335
466
  pnpm pack --pack-destination artifacts
336
467
  ```
@@ -339,7 +470,7 @@ Then run `pnpm verify:tarball -- artifacts/dsh-github-copilot-<package-version>.
339
470
 
340
471
  `pnpm verify` checks the Agent contract, source and local test types, baseline markers, a clean build, Vitest tests, Node tooling tests, and real built Host import/Client-loader/Remote smoke. `tests/fixtures` are intentionally excluded from local test typecheck because they import source from a separate pinned Core checkout. The checked-in code must pass; never suppress compiler errors or weaken a test to get a green report.
341
472
 
342
- If the exact frozen install is blocked solely by an enterprise registry or network policy while the repository's GitHub Actions can obtain the unchanged pinned packages from an authorized official registry, record the attempted command and exact environmental failure as **local validation blocked**, not passed. A PR may proceed with that limitation disclosed; the complete required GitHub CI matrix, including its install, tests, build and package checks, is then the authoritative gate before merge. Never weaken or skip CI, substitute dependencies, bypass organizational restrictions, claim unrun local gates succeeded, or tag/release a revision whose required CI is not green. If CI has the same failure, resolve it through approved infrastructure rather than bypassing it.
473
+ If a historical/approved local installation attempt is blocked solely by an enterprise registry or network policy while GitHub Actions can obtain unchanged pinned packages from an authorized official registry, record it as **local validation blocked**, not passed. Do not repeat dependency recovery, switch sources, or expand permissions. A PR may proceed with that limitation disclosed; the complete required GitHub CI matrix, including install, tests, build and package checks, is authoritative before merge. Never weaken or skip CI, substitute dependencies, bypass organizational restrictions, claim unrun local gates succeeded, or tag/release a revision whose required CI is not green. If CI has the same failure, resolve it through approved infrastructure rather than bypassing it.
343
474
 
344
475
  The release CI matrix targets only exact official `0.2.1-rc.3` on Windows and Linux; earlier pins are not support gates. It runs the unchanged tagged-source runtime fixture, optional native Chat fixture, exact published-artifact adapter fixture and all 28 native reviewer regressions without skips. This is a required gate, not evidence that an unexecuted qualification passed. `verify:upstream` is static seam-marker evidence. `verify:controlled-core` exclusively installs a temporary config fixture, refuses an existing target, and removes only its own file; it is not full plugin activation. Published-artifact synthetic adapter fixtures do not prove live provider transport. The release job must wait for the complete reusable CI matrix on the tagged revision, then verify its own packed bytes before publishing.
345
476
 
@@ -361,7 +492,7 @@ The release CI matrix targets only exact official `0.2.1-rc.3` on Windows and Li
361
492
  | Last-success timestamp (alpha.7, #97) | Show `snapshot.discoveredAt` once beside count outside Manage: English relative text, full LOCAL date/time/zone tooltip and accessible semantic `time`; missing/invalid/no account hides it, future uses absolute text. Pending/error retains last success, successful refresh replaces it and sign-out clears it. One mounted 60s display-only timer makes no RPC/status/discovery calls and is disposed with timestamp/unmount; cache/discovery lifecycle unchanged |
362
493
  | Definitive `UNKNOWN_MODEL` | One bounded metadata refresh, never message replay or automatic model switching; generic HTTP/network errors are not guessed to be unknown models |
363
494
  | README screenshot | `copilot-search-routing.png` shows the current built plugin-detail routing card with synthetic providers in an isolated browser fixture. It proves only the current presentation surface, not live credentials, provider availability, search success or Desktop activation. |
364
- | Host attach/restart | Reconciles the stored profile; search proofs stay lazy and do not start at attach |
495
+ | Host attach/restart | Does not repair or rewrite the stored native profile; search proofs stay lazy and do not start at attach |
365
496
  | Background credential/reset notifications | Invalidate evidence and clear Client state with read-only status; no forced discovery on every token event; next Models open/use ensures metadata |
366
497
  | Eligible model/search request | May resolve/refresh credentials and run bounded capability proof; changes during proof must fail closed rather than reuse another account's proof |
367
498
  | Release install | Writes a named user profile; installed on disk is not loaded in the running Host |
package/CHANGELOG.md CHANGED
@@ -1,5 +1,43 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.1.0-alpha.3.dsh.0.2.2.rc.3 (prepared)
4
+
5
+ - Extend reviewer-only temperature omission to qualified DSH native `github-copilot` Responses calls, preserving ordinary Chat and native verdict/permission ownership (#460).
6
+ - Add optional canonical-account Copilot hosted search through the existing native Web registry, with one bounded proof and one final query, cancellation and configuration/credential invalidation (#461).
7
+ - Preserve native settings, selected backends, accounts and histories. No live installation, restart or supplier acceptance is implied.
8
+
9
+ ## 0.1.0-alpha.2.dsh.0.2.2.rc.3 (prepared)
10
+
11
+ - Explain the native provider's canonical OAuth binding and the existing additional-account coexistence limit, while retaining the visible account panel outside the native Add draft (#458).
12
+ - Bind native-route quota to the canonical OAuth record rather than the plugin-selected account, and show an explicit unavailable state when native credential or endpoint attribution cannot be proven.
13
+ - Keep native quota and context-incident diagnostics available without optional managed-route Remotes, and stop automatically modifying native provider settings at startup or sign-in.
14
+ - Exercise native Copilot subagent selection and synthetic concurrent requests with the plugin absent, enabled and disposed.
15
+ - The native route still uses its own catalog; account-discovered models apply to `github-copilot-preview`. Copilot-hosted search, native Auto-review sampling compatibility and native per-Session multi-account routing remain incomplete.
16
+ - Live OAuth, provider calls, billing attribution and Desktop activation remain unverified.
17
+
18
+ ## 0.1.0-alpha.1.dsh.0.2.2.rc.3 (prepared)
19
+
20
+ - Begin narrowing the product to account-authorized Copilot models through DSH's published native adapter. Plugin-owned Auto and parent-follow routing and hosted-search composition are retired in the candidate; preserve account quota and review other enhancements before removing only demonstrably unnecessary functionality.
21
+ - Hide inactive Auto and parent-follow settings and remove the obsolete Auto high-cost marking control without changing saved preferences; retain legacy settings and Remote for compatibility.
22
+ - Preserve historical account, model and incomplete-Usage evidence separately from retired Auto selection UI; never reconstruct account history or replace native Usage.
23
+ - Label retired Auto and parent-follow documentation as historical and omit the obsolete Auto UI mockup from the package.
24
+ - Require account-metadata-driven native subagent model selection and actual child invocation, including supported Thinking and concurrent/account-bound request checks; synthetic exact-source fixtures passed on Windows and Linux, but do not establish live supplier or Desktop behavior.
25
+ - Target DSH ownership of parent/child relationships, inheritance and scheduling; legacy dedicated-role orchestration still requires safe retirement.
26
+ - Remove HydraFusion/Max from scope. No additional login, Core changes, model-name routing rules, silent provider substitution, publication, profile installation, or Desktop restart is included.
27
+ - Target official DSH 0.2.2-rc.3. Required Windows/Linux CI, pnpm-lock alignment, publication, profile installation, and loaded-runtime compatibility remain unverified.
28
+
29
+ ## 0.1.0-alpha.5.dsh.0.2.1.rc.3 (prepared)
30
+
31
+ - Replace the stale rc.2 Desktop lifecycle heading with version-neutral guidance. Recommend a full exit and restart only when the native plugin manager reports `restart-required`; do not repeatedly toggle an Off plugin when the manager reports only pending service dependencies.
32
+ - Keep historical rc.2 Desktop observations distinct from current rc.3 synthetic Loader evidence, and synchronize the English/Chinese README and user-visible copy regressions (#453).
33
+ - Prepare same-Core alpha.5 metadata only. The rc.3 release mapping remains pending; no tag, GitHub Release, npm publication, profile installation or Desktop restart is included.
34
+
35
+ ## 0.1.0-alpha.4.dsh.0.2.1.rc.3 (prepared)
36
+
37
+ - Carry forward bounded Responses replay refusal diagnostics from retired draft #218 under #446: fixed reasons, zero-based input positions, allowlisted type/status and field-presence booleans through the existing native `INVALID_REQUEST` surface. No IDs, summaries, tool data, unknown values or encrypted bytes enter diagnostics.
38
+ - Exercise current pinned pi-ai 1.1.0 synthetic two-turn summary-only rejection and terminal encryption backfill, preserving original history, exact opaque bytes and `call_id` pairing. Retain existing replay acceptance, account isolation, consent and cancellation ownership; no new retry, history deletion or model switch.
39
+ - Prepare the next same-Core candidate metadata for required PR validation only. No tag, merge, publication, profile installation, restart or live model call is authorized.
40
+
3
41
  ## 0.1.0-alpha.3.dsh.0.2.1.rc.3 (prepared)
4
42
 
5
43
  - Explain projected-image admission failures through the standard native error path with bounded model, projected/allowed MIME, projected role/position and current build details (#426). Retain the existing fail-closed gate, explicit account restrictions and native projection ownership.
package/CONTRIBUTING.md CHANGED
@@ -33,6 +33,10 @@ Core inspection is read-only. Isolated tests may use unchanged pinned Core artif
33
33
 
34
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
35
 
36
+ The project disables pnpm's minimum package publication age. Newly published
37
+ dependencies can therefore be installed immediately; lockfile integrity and
38
+ the required CI and release checks still apply.
39
+
36
40
  ## Task acceptance pilot
37
41
 
38
42
  Define requirement IDs, expected behavior, verification methods and non-goals