mirror of
https://github.com/deepseek-ai/deepseek-harness.git
synced 2026-09-14 04:01:35 +00:00
Yichen Jiang
6428b844ef
- dsh-authorization's manifest becomes a release member on current master's terms: version matches the root 0.1.0-rc.6 and publishConfig.access is public, which the constraints gate and the tarball pack's version verify both enforce after the master merge. - Regenerate docs/module-graph (zh mirror included) for the authorization package and the llm-pi-ai -> authorization edge; the graph gate lives outside doc-sync and was never regenerated when the package was added. - The built-bin smoke seeds the versioned credentials document; this branch's provider refuses the pre-release flat layout by design, and the master-side test still wrote the old shape.
credentials/ — credentials and authorization
English | 中文
The credential capability family separates reference resolution from its provider, and separates both from obtaining a credential that has to be asked for:
| Package | Role | ctx key |
|---|---|---|
credentials/ |
Credential-reference and credential-record seam | ctx.credentials |
credentials-local/ |
Environment and local-file provider | registers ctx.credentials |
authorization/ |
Plugin-owned flows that obtain a credential by asking a human | ctx.authorization |
Configuration carries references, not secret values. Consumers resolve those references at their operation boundary; the child READMEs own mutation, precedence, and storage semantics. An authorization flow writes a credential record and is keyed by it, so the two seams meet at the record and nowhere else.
The subsystem reference — CredentialRef, per-operation resolution, UI-safe CredentialInfo, provider layers — is docs/subsystems/credentials.md.