generated from coulomb/repo-seed
Transfered deep scope functionality from the custodian
This commit is contained in:
@@ -4,7 +4,7 @@ type: workplan
|
||||
title: "SCOPE.md Generation Feature"
|
||||
domain: capabilities
|
||||
repo: repo-registry
|
||||
status: todo
|
||||
status: done
|
||||
owner: codex
|
||||
topic_slug: foerster-capabilities
|
||||
created: "2026-04-30"
|
||||
@@ -37,7 +37,7 @@ Unblocks: RREG-WP-0006
|
||||
|
||||
```task
|
||||
id: RREG-WP-0005-T01
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "83154aae-dd06-4329-8df6-3906b2bf0f14"
|
||||
```
|
||||
@@ -73,11 +73,17 @@ Acceptance: `docs/scope-md-spec.md` exists, covers all 11 sections with
|
||||
explicit characteristic-to-section mappings, and is consistent with the
|
||||
existing template at `state-hub/scripts/project_rules/scope.template`.
|
||||
|
||||
Implementation note 2026-04-30: `docs/scope-md-spec.md` now owns the reference
|
||||
specification. It maps the current Custodian template headings to the
|
||||
Scope/Ability/Capability/Feature/Evidence/Facts model, documents generated vs.
|
||||
curator-owned sections, preserves the existing capability block format, and
|
||||
cross-references the characteristic/evidence and classification strategy docs.
|
||||
|
||||
## T02: Build SCOPE.md generator
|
||||
|
||||
```task
|
||||
id: RREG-WP-0005-T02
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "39feb7ea-72ca-4d99-8094-b006df605dbe"
|
||||
```
|
||||
@@ -109,11 +115,17 @@ valid SCOPE.md; all 11 sections are present; the `## Provided Capabilities`
|
||||
section contains parseable capability blocks; the output passes the C5b/C5c
|
||||
checks defined in CUST-WP-0034-T01.
|
||||
|
||||
Implementation note 2026-04-30: `repo_registry.scope.ScopeGenerator` now renders
|
||||
SCOPE.md from approved repository scope, abilities, capabilities, features, facts,
|
||||
support evidence, and classification metadata. It preserves the current template
|
||||
headings, emits curator-input stubs for missing data, and renders approved
|
||||
capabilities as parseable `capability` blocks.
|
||||
|
||||
## T03: Build SCOPE.md validator and differ
|
||||
|
||||
```task
|
||||
id: RREG-WP-0005-T03
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "0c9c1347-368a-4657-a039-ae143a6500bd"
|
||||
```
|
||||
@@ -137,11 +149,15 @@ Acceptance: `ScopeValidator.diff("repo-registry", Path("SCOPE.md"))` returns
|
||||
a diff with at least some `ok` sections and surfaces any real gaps; the
|
||||
validator catches a missing `## Provided Capabilities` section as a `warn`.
|
||||
|
||||
Implementation note 2026-04-30: `repo_registry.scope.ScopeValidator` now validates
|
||||
C5a/C5b/C5c-style SCOPE.md structure, parses capability blocks, and produces
|
||||
section-aware diffs against freshly generated content.
|
||||
|
||||
## T04: API endpoints
|
||||
|
||||
```task
|
||||
id: RREG-WP-0005-T04
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "a2d1937b-f9e2-480e-8e28-1c12837e1b23"
|
||||
```
|
||||
@@ -164,11 +180,17 @@ Acceptance: `GET /repos/repo-registry/scope` returns valid Markdown; `GET
|
||||
/repos/repo-registry/scope/diff` returns a diff JSON; a `POST` write succeeds
|
||||
and the written file passes the validator.
|
||||
|
||||
Implementation note 2026-04-30: Added `/repos/{repo_slug}/scope`,
|
||||
`/repos/{repo_slug}/scope/diff`, and `/repos/{repo_slug}/scope/write` API
|
||||
endpoints. The endpoints resolve registered repositories by slug, require
|
||||
approved characteristics, use a local repository path or cached checkout for
|
||||
diff/write operations, and return 409 when no local path is available.
|
||||
|
||||
## T05: Register capabilities in custodian
|
||||
|
||||
```task
|
||||
id: RREG-WP-0005-T05
|
||||
status: todo
|
||||
status: done
|
||||
priority: medium
|
||||
state_hub_task_id: "e1bd4a4f-3d9a-4384-a254-ef75bd9905b9"
|
||||
```
|
||||
@@ -200,3 +222,9 @@ CUST-WP-0034-T03 will then resolve correctly.
|
||||
Acceptance: `list_capabilities()` in the state-hub MCP returns `scope.generate`
|
||||
and `scope.update` with `provider_repo: repo-registry`; `request_capability`
|
||||
with either key resolves without routing error.
|
||||
|
||||
Implementation note 2026-04-30: Added `scope.generate` and `scope.update`
|
||||
capability blocks to `SCOPE.md`, then ingested them with the State Hub
|
||||
capability ingestion script using `/home/worsch/repo-registry` as the explicit
|
||||
repo path. The State Hub catalog created `api/scope.generate` and
|
||||
`api/scope.update` entries for `repo-registry`.
|
||||
|
||||
Reference in New Issue
Block a user