coulomb/issue-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
issue-core/registry
History
Exact
tegwick f88e9a28fe
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details
Build and Publish Container Image / build-and-push (push) Successful in 1m22s
Details
feat: implement ISSUE-WP-0005 connector mapping and scope alignment 
Add MappingService (work_record_uuid ↔ external id), project/map CLI with
outward push-status, optional TaskSpec work_record fields, boundary-sync
policy, and packaging/capability framing cleanup. Mark WP-0005 finished.
2026-07-22 00:25:06 +02:00
..
capabilities feat: implement ISSUE-WP-0005 connector mapping and scope alignment 2026-07-22 00:25:06 +02:00
indexes T05 entry 4: wire consumer relations and refresh issue-core evidence. 2026-07-07 16:22:14 +02:00
README.md Add capability registry scaffold (REUSE-WP-0014-T05 B03) 2026-06-16 01:53:53 +02:00

README.md

Capability Registry

Markdown-first capability index for federation and reuse planning.

Authoring

  1. Copy a capability entry template (see reuse-surface templates/capability-entry.template.md).
  2. Add the row to indexes/capabilities.yaml.
  3. Run reuse-surface validate from a checkout with the CLI installed.
  4. Merge to main and verify publish with reuse-surface establish --publish-check.

Federation contract: reuse-surface docs/RegistryFederation.md.