Commit graph

5 commits

Author SHA1 Message Date
27ac54b32d Enforce private-by-default enablement templates
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa
2026-08-22 12:34:25 +02:00
a2525a404c Inherit the forge layer responsibility (S4)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Decision d151d817 placed railiance-forge: the Forgejo workload becomes
rapp-forgejo, and the layer responsibility - runner placement and labels,
registry retention, artifact lifecycle, package credentials - folds into S4,
which already declared a handoff contract with forge for exactly those concerns.

Also states plainly what the 2026-08-11 architecture assessment found about this
layer: it is almost entirely aspiration, with a rich Direction of Evolution and
25 commits and no workplans behind it. The gap should be read as open debt
rather than as a description of the present. The forge responsibility is S4's
first concrete owned accountability.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-11 23:19:34 +02:00
b34d08c358 Reference forge runner contract 2026-06-05 16:16:42 +02:00
b6712300c6 Clarify enablement forge handoffs 2026-06-05 15:43:13 +02:00
a9301a009c Add enablement intent 2026-06-05 00:56:34 +02:00