Draft capability entry (reuse-surface REUSE-WP-0017-T04, cohort 3)

Honest first-pass maturity vector grounded in README/docs/tests present
in this repo; no invented evidence. Flagged for human review before
publish. See reuse-surface history/2026-07-06-coverage-classification.md.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

registry/capabilities/capability.railiance.ci-enablement.md

@@ -0,0 +1,125 @@
+---
+id: capability.railiance.ci-enablement
+name: Railiance Developer Enablement And CI/CD Templates
+summary: S4 Developer Enablement layer of the Railiance OAS Stack — reusable CI/CD workflow templates,
+  developer portal paths, platform templates, SDKs, and buildpacks, using forge capabilities without owning
+  forge runtime.
+owner: railiance-enablement
+status: draft
+domain: financials
+tags:
+- railiance
+- ci-cd
+- developer-enablement
+- forgejo
+maturity:
+  discovery:
+    current: D3
+    target: D4
+    confidence: medium
+    rationale: SCOPE.md places this repo precisely at S4 in the Railiance OAS Stack, explicitly scoped
+      to reusable CI/CD templates and enablement tooling while using (not owning) forge capabilities.
+  availability:
+    current: A2
+    target: A3
+    confidence: high
+    rationale: Ships real, reusable Forgejo Actions workflow templates (container-build-push.yaml, container-build-push-multirepo.yaml,
+      ci-smoke.yaml) plus `tools/promote-repo-to-forgejo.sh` — directly relevant tooling for the ecosystem-wide
+      Gitea-to-Forgejo transition (REUSE-WP-0019).
+external_evidence:
+  completeness:
+    level: C2
+    confidence: low
+    basis: scope_vs_intent_and_consumer_expectations
+    satisfied_expectations:
+    - reusable Forgejo Actions CI/CD workflow templates already in production shape
+    - a repo-promotion-to-forgejo script directly usable for the platform-wide forge transition
+    broken_expectations: []
+    out_of_scope_expectations: []
+  reliability:
+    level: R1
+    confidence: low
+    basis: consumer_quality_signals
+    known_reliability_risks:
+    - templates are workflow YAML, not a packaged/versioned artifact; consumption is copy/reference rather
+      than dependency-managed
+discovery:
+  intent: Give Railiance repos reusable CI/CD templates and developer-enablement tooling (including forge-promotion
+    tooling) without each repo owning the forge runtime or runner substrate itself.
+  includes:
+  - reusable Forgejo Actions CI/CD workflow templates
+  - repo-to-forgejo promotion tooling
+  - developer portal/platform template scope (per SCOPE.md)
+  excludes:
+  - forge runtime and runner substrate ownership (see railiance-forge)
+  assumptions: []
+  use_cases: []
+  research_memos: []
+availability:
+  current_level: A2
+  target_level: A3
+  current_artifacts:
+  - workflows/container-build-push.yaml
+  - workflows/ci-smoke.yaml
+  - tools/promote-repo-to-forgejo.sh
+  target_artifacts: []
+  consumption_modes:
+  - ci workflow template (copy/reference)
+  - cli (promote-repo-to-forgejo.sh)
+relations:
+  depends_on: []
+  supports: []
+  related_to: []
+evidence:
+  documentation:
+  - SCOPE.md
+  tests:
+  - workflows/ci-smoke.yaml
+  consumer_feedback: []
+  bug_reports: []
+  incidents: []
+consumer_guidance:
+  recommended_for:
+  - Railiance repos needing reusable Forgejo Actions CI/CD templates, or any repo executing a Gitea-to-Forgejo
+    promotion
+  not_recommended_for:
+  - needs for owning forge runtime/runner infrastructure itself (see railiance-forge)
+  known_limitations:
+  - templates are consumed by copy/reference, not as a versioned dependency
+promotion_history: []
+---
+
+# Railiance Developer Enablement And CI/CD Templates
+
+## Overview
+
+`railiance-enablement` is the S4 Developer Enablement layer of the Railiance OAS Stack: reusable CI/CD workflow templates and developer-enablement tooling, including a `promote-repo-to-forgejo.sh` script directly relevant to the ecosystem-wide Gitea-to-Forgejo transition tracked in REUSE-WP-0019.
+
+## Assessment notes
+
+### Discovery
+
+SCOPE.md places this repo precisely at S4 in the Railiance OAS Stack, explicitly scoped to reusable CI/CD templates and enablement tooling while using (not owning) forge capabilities.
+
+### Availability
+
+Ships real, reusable Forgejo Actions workflow templates (container-build-push.yaml, container-build-push-multirepo.yaml, ci-smoke.yaml) plus `tools/promote-repo-to-forgejo.sh` — directly relevant tooling for the ecosystem-wide Gitea-to-Forgejo transition (REUSE-WP-0019).
+
+### Completeness
+
+First-pass honest assessment from the REUSE-WP-0017 coverage campaign
+(reuse-surface). No external consumer feedback exists yet; levels reflect
+scope-vs-intent documentation quality, not internal code quality.
+
+### Reliability
+
+No production consumer telemetry exists yet; reliability level is
+intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence.
+
+## Promotion checklist
+
+- [x] ID follows `capability.<domain>.<name>` pattern
+- [x] Maturity enums match `specs/CapabilityMaturityStandard.md`
+- [x] `external_evidence` is populated separately from `maturity`
+- [ ] Relations reference valid capability IDs (none yet)
+- [x] Index entry added in `registry/indexes/capabilities.yaml`

registry/indexes/capabilities.yaml

@@ -1,4 +1,22 @@
 version: 1
-updated: '2026-06-16'
+updated: '2026-07-06'
 domain: helix_forge
-capabilities: []
+capabilities:
+- id: capability.railiance.ci-enablement
+  name: Railiance Developer Enablement And CI/CD Templates
+  summary: S4 Developer Enablement layer of the Railiance OAS Stack — reusable CI/CD workflow templates,
+    developer portal paths, platform templates, SDKs, and buildpacks, using forge capabilities without
+    owning forge runtime.
+  vector: D3 / A2 / C2 / R1
+  domain: financials
+  status: draft
+  owner: railiance-enablement
+  path: registry/capabilities/capability.railiance.ci-enablement.md
+  tags:
+  - railiance
+  - ci-cd
+  - developer-enablement
+  - forgejo
+  consumption_modes:
+  - ci workflow template (copy/reference)
+  - cli (promote-repo-to-forgejo.sh)