coulomb/issue-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
issue-core/registry
History
tegwick ee9b85215d
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 34s
Details
docs(ISSUE-WP-0006): Forgejo-only language and projection boundary 
Prefer Forgejo as the self-hosted forge product. Keep Gitea only as the
Gitea-compatible API identifier (module backends/gitea, type string
gitea). FORGEJO_TOKEN is preferred; GITEA_* remains a deprecated alias.

INTENT/SCOPE quote ACT-ADR-005: issue-core is not the fleet ops claim
queue. Connector docs describe repo work record → hub index → optional
Forgejo projection, not activity-core → issue-core → harness.

Assistant: grok
Assistant-Session: 01a09dc6-3f0d-7c93-8b11-8e83c0623d49
2026-09-14 04:52:58 +02:00
..
capabilities docs(ISSUE-WP-0006): Forgejo-only language and projection boundary 2026-09-14 04:52:58 +02:00
indexes docs(ISSUE-WP-0006): Forgejo-only language and projection boundary 2026-09-14 04:52:58 +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.