Repository navigation
Closed
Description
DSH 0.1.0-rc.8 refuses to load the credentials plugin: the installed dsh-credentials-local expects a flat mapping of references to non-empty strings, and the observed document has the top-level keys records, refs and version. The reader and the rotation writer disagree. This issue asks the key master to agree one contract between them. Refs #13046.
No secret value is in this issue. Only key names and file shapes are quoted.
Observation (2026-11-01, T27 OS shell cell)
dsh --profile headless "<read-only errand>"stops at plugin load withcredentials-local: the value for "records" in <DSH home>/.credentials.yaml must be a string. Authorization at the model provider was never reached, so no key is shown to be wrong or expired. Status: T27 OS launched DSH (checked); credentials plugin load (refused on format); model access (not checked); expected answer (not received); ACP (not checked).- Reader contract, read from the installed plugin (README and
lib/index.js, rc.8 in the global install and in the profile-localnode_modules): the document is a YAML mapping of credential reference to value "and nothing else"; a non-mapping root, a non-string value or an empty value is a rejection. Config fields:path,dshHome(default$DSH_HOMEor~/.dsh),watch,debounceMs. The inherited process environment wins over the file. - Observed document (names only): top-level keys
records,refs,version;refsholds five references;recordsholds three entries withkindandpayload; mode 0600, 933 bytes. - Known writer: the launchd rotation job (every 60 s) patches
refs.<REF>as text, createsversion: 1andrefs:on an empty file, keeps every other line, and finds the current key with a regex that assumes the two-space nested layout. It has no code forrecords. The writer ofrecordsis not identified; the rc.8 packages contain norecordshandling. - Why the document must not simply be flattened (derived from reading the rotation script, not run): its next write finds no two-space line, finds no
refs:and appends arefs:block, which restores the nested layout within one tick. - Consumers: the five references are the names that the
webprofile patch uses. Theheadlessprofile patch is empty and names none of them. Whether theheadlessprofile needs any reference is not established. Thewebprofile includes the same plugin, so a web restart would fail the same way; the web service is not running at the time of writing and nobody restarted it.
Boundary
- specs/t27os/keys.t27
User Scenarios
- Given the credentials document has the top-level keys
records,refsandversion, whendsh --profile headlessstarts, then the credentials plugin must load instead of exiting 1. - Given a compatible store is in place, when the rotation job rewrites its key, then the plugin must still load on the next start.
- Given the change was wrong, when the key master rolls it back, then no secret value appears in any log or report.
Requirements
- FR-001: The key master MUST confirm the schema the installed plugin expects against the installed version before any change.
- FR-002: The key master MUST identify the process that writes
recordsand every process that reads or writes the current layout, and MUST name the references DSH needs for theheadlessandwebprofiles. - FR-003: The change MUST choose one compatible route and justify it: a separate store for the rotation state, the plugin
pathsetting, or a verified conversion. - FR-004: The change MUST include a rollback that does not print a secret value.
- FR-005: The change MUST show, by observing one rotation cycle, that the next rotation does not restore the incompatible layout.
- FR-006: The key master MUST signal readiness for one repeat headless run; the signal MUST NOT carry a secret.
Success Criteria
- One headless run of a read-only errand ends with
exit 0and prints the expected answer token. - One rotation cycle of 60 s after the change leaves the document loadable (the repeat run still ends with
exit 0). - 0 secret values appear in this issue, its comments or the readiness signal.
Metadata
Metadata
Assignees
Labels
No labels
Activity
gHashTag commentedon Nov 1, 2026
Update after reading the sources and one headless attempt (2026-11-02). No credential value, token or raw run output is included here.
The premise of this issue changes. The store layout is not what blocks the source launcher.
~/.dsh. The globally installed CLIdshis@deepseek-ai/dsh0.1.0-rc.8; its credentials plugin accepts only a flat ref-to-string map, so it rejects the nestedversion/refs/recordslayout with therecordserror. The source tree~/deepseek-harness(0.2.2-alpha.2), which the web launchd job runs, reads the nested layout. The rotator~/bin/dsh-zai-rotate.mjspatchesrefs.DSH_ZAI_KEYin that nested layout and is compatible with it. So the store is correct for 0.2.x and the rc.8 CLI is the odd one out.--profile headless) passed plugin load and the store read: norecordserror.DSH_T27OS_OKwas not received, and the exit line was withheld because a secret-screen matched it. The likely stage is the provider/model route:~/.dsh/profiles/headless/cordis.patch.ymlis an empty array and the headless profile bundles onlydsh-baseanddsh-headless, while the web profile patch carries thezai-poolroute. This is read from the profile files; the exit line itself was not read.workspace-changesplugin (mounted only by the web-app bundle) wrote about 4.8 GiB ofdsh-workspace-changes-*temp trees in about 2.5 minutes with no model turn; a graceful stop disposed them. No config knob in that plugin bounds the size.What is needed from whoever accepts this issue (nothing here was changed by me):
workspace-changes, or restrict session working directories).Assignees: none. Acceptance by a named executor is still pending.
gHashTag commentedon Nov 17, 2026
Spec created: specs/t27os/dsh_rc8_credentials.t27 (typecheck OK, 2 tests pass).
gHashTag commentedon Nov 17, 2026
Reopened: closed as spec-only. A .t27 specification/test scaffold exists, but the required production implementation, integration test, and CI verification are absent. This issue remains open until the target component implements the specified behavior and evidence is provided.
gHashTag commentedon Nov 17, 2026
Specs created for M10 milestone. Typecheck OK.
gHashTag commentedon Nov 18, 2026
Reopened: closed as spec-only. A .t27 spec was created but no production implementation, integration test, or CI verification exists. This issue remains open until the target component implements the specified behavior and evidence is provided.