@stofone/dsh-agent-roster 0.6.2 → 0.8.0

package/CHANGELOG.md

@@ -2,6 +2,101 @@
 
 遵循 [Keep a Changelog](https://keepachangelog.com/zh-CN/1.1.0/) 与 [SemVer](https://semver.org/lang/zh-CN/)。
 
+## [Unreleased]
+
+## [0.8.0] - 2026-11-02
+
+### Library organization (new root file)
+
+- **`organization.yaml`** — an optional file at the library root, beside the roster directories.
+  It declares which rosters belong to the library, their status (`active` | `archived`) and where
+  they came from. It is the only file allowed to sit at the root, and it still cannot create
+  anything: no teams, no members, no `agent_teams_add_member` arguments.
+- **Three-way cross-check against the disk**, surfaced as diagnostics the panel already renders:
+  declared but missing → **error**, present but undeclared → **warn**, declared `archived` but
+  still in the library → **info**. Archiving is a declaration, not a deletion.
+- **`roster_list` and `dsh-agent-roster validate` show it** (`organization=<id>`, the counts, and
+  per-file `organization` / `organizationCheck` in `--json`);
+  `schema/organization.v1.schema.json` covers the file for editor-side validation.
+- **`orgs/agent-roster-collective/`** ships as a worked example: 21 self-authored rosters
+  (63 members) covering review, incident response, data, docs, release, research and more.
+- **`security-audit/capabilities.yaml`** in that example shows the two-file library: a roster plus
+  its declared requirements, with `onMissing: degraded` so a deployment without the policy still
+  builds the team but reports the gap instead of pretending it passed.
+
+### Registry schema (new file)
+
+- **`schema/registry.v1.schema.json`** — the shipped `index/registry.json` pointed at a schema that
+  did not exist, so editors had nothing to lint against. The file now exists, mirrors
+  `lib/remote.js#validateRegistry`, and `test/registry-schema.test.js` keeps the two aligned
+  (field sets, id/repo/ref/path patterns, collection and roster limits).
+
+### Removed
+
+- **`INDEX_KIND`** (`dsh-agent-roster-index/v1`). Nothing ever produced that document: a registry
+  collection already carries its `rosters` list, and `registry sync` recomputes it from the
+  repository. Keeping a second manifest format would have been a second source of truth.
+
+## [0.7.0] - 2026-11-02
+
+### Honest verification (issue #2)
+
+- **`omitted` is split in two.** "The roster did not declare this field" and "the roster declared
+  a value, the runtime never persisted it" used to collapse into one status that the summary
+  counted as "not degraded". They are now `omitted` (nothing to check, expected) and
+  `not-persisted` (sent, no receipt, counted as degraded). `systemPrompt` lands in the second
+  bucket because `team.json` members have no `executionPrompt` key at all — the persona was
+  never actually verified before.
+- **One predicate instead of three.** `isBindingFaithful` now delegates to
+  `summarizeBinding(...).faithful`, so the note and the implementation cannot drift apart again.
+- **Four mutually exclusive buckets** in `roster_verify`: `faithful` / `unverified` / `drift` /
+  `missing`. `ok` requires `drift === 0 && missing === 0`, and `unverified` is printed on the
+  status line and the summary instead of hiding inside "degraded".
+- **Materialised tool filters are visible.** Each member shows `deny`/`allow` counts and a
+  digest of the normalised list; the same `toolPolicy` materialising into two different deny
+  lists inside one team is reported as policy drift.
+- **Provenance.** `roster_create` emits `roster:<id>@<version>#<sha8>` for the created team's
+  description; `roster_verify` parses it back and reports `absent` / `id-only` / `match` /
+  `differ` / `unknown-roster`. The plugin still never writes team state.
+- **New tool `roster_diff`** — roster-to-roster diff for generation hand-over: members matched
+  by name (`aliases` are a hint, never auto-merged), effective values compared with their
+  origin, persona compared by length and hash only.
+
+### Capability requirements (new sibling file)
+
+- **`capabilities.yaml`** — an optional file next to `roster.yaml` that declares what the
+  deployment must provide: `requires.skills`, `requires.toolPolicies`, `onMissing`
+  (`refuse` | `degraded`), `asOf` (date only) and `notes`. Unknown keys and unknown requirement
+  categories are errors: model routing, plugin versions, credential pointers and business
+  preconditions have no evidence source, so declaring them would only manufacture a new kind of
+  false green.
+- **Three states, not two.** `checkCapabilities` answers `present` / `missing` / `unknown`;
+  only `missing` (the evidence source explicitly says no) trips the gate. `unknown` is neither a
+  pass nor a failure and is always printed.
+- **`roster_create` refuses instead of warning.** With a `missing` requirement under
+  `onMissing: refuse` it emits no `agent_teams_add_member` argument at all and prints where each
+  requirement has to be installed. `onMissing: degraded` hands over the arguments and records
+  the debt.
+- **`roster_verify`** gains `requires=<missing>missing/<declared>` and `capabilityBlocked` in its
+  status line, a capability section in the body, `ok` includes `capabilityBlocked === 0`, and a
+  structured `capabilities` field.
+- **`roster_show`** prints the declaration block.
+- New `schema/capabilities.v1.schema.json`, pinned to `lib/capabilities.js` by
+  `test/capabilities.test.js`.
+
+- **The panel sees it.** Capability requirements surface as roster diagnostics: a missing
+  `toolPolicies` requirement is `error` under `refuse` (the sidebar badge turns red) and `warn`
+  under `degraded`; skill requirements are `capability-skills-unverified` / `info` because the
+  panel snapshot is synchronous and cannot enumerate the catalogue; an unset `knownToolPolicies`
+  yields one `capability-cross-check-skipped` entry naming the affected rosters.
+
+### Docs
+
+- README (both languages): six tools, the new verification buckets, `roster_diff`, a
+  "one roster per directory, two generations per machine" section answering how to keep both
+  generations side by side, and a "capability requirements" section covering the three-state
+  check and the gate.
+
 ## [0.6.2] - 2026-10-30
 
 ### Packaging
@@ -201,5 +296,7 @@
 - 工具返回值含 `undefined` 键，运行时按 `value is not lossless JSON` 整次拒绝；缺失值统一写 `null`，
   且所有返回值先过 `lib/json.js#lossless`。
 
-[Unreleased]: https://github.com/STofone/dsh-agent-roster/compare/v0.2.0...main
+[Unreleased]: https://github.com/STofone/dsh-agent-roster/compare/v0.8.0...main
+[0.8.0]: https://github.com/STofone/dsh-agent-roster/releases/tag/v0.8.0
+[0.7.0]: https://github.com/STofone/dsh-agent-roster/releases/tag/v0.7.0
 [0.2.0]: https://github.com/STofone/dsh-agent-roster/releases/tag/v0.2.0

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 STofone
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 STofone
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.