base-layer/releasekit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 5 Wiki Activity

Align completed forge roadmap status records

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-01 19:26:52 +00:00
parent 6bed1cd691
commit 9376bafaa2
3 changed files with 20 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/roadmap/forge-boundary.md
View File

@@ -1,6 +1,7 @@
# Roadmap: forge delivery boundary and credential preflight # Roadmap: forge delivery boundary and credential preflight
Status: accepted; implementation has not started. Status: implementation complete; review corrections are tracked in
[remediation](remediation.md).
The [implementation plan](implementation.md) owns stages, concrete design The [implementation plan](implementation.md) owns stages, concrete design
choices, task sequencing, and verification. choices, task sequencing, and verification.
@@ -23,10 +24,11 @@ backends remain future implementation work. The boundary should express the
operations used by the current delivery workflow and allow refinement when a operations used by the current delivery workflow and allow refinement when a
second backend supplies concrete requirements. second backend supplies concrete requirements.
## Current baseline ## Historical planning baseline
The source baseline is `ac78e7d`, following the published v0.5.0 module migration The original source baseline was `ac78e7d`, following the published v0.5.0
and the subsequent token-file and forbidden-file changes. module migration and the subsequent token-file and forbidden-file changes.
The following describes that revision, before implementation of this roadmap.
- [delivery.go](../../delivery.go) exposes `GiteaDestination` through - [delivery.go](../../delivery.go) exposes `GiteaDestination` through
`DeliveryRequest.Destination` and converts it into `gitea.Destination`. `DeliveryRequest.Destination` and converts it into `gitea.Destination`.
@@ -50,8 +52,8 @@ and the subsequent token-file and forbidden-file changes.
request boundary. There is no dedicated authenticated credential preflight. request boundary. There is no dedicated authenticated credential preflight.
The [Gitea integration guide](../integrations/gitea.md) and public Go declarations The [Gitea integration guide](../integrations/gitea.md) and public Go declarations
document the baseline contracts. Current behavioral tests provide regression now describe the implemented contracts. Behavioral tests provide regression
coverage to assess against those contracts. The coverage for the selected behavior. The
[architecture policy](../policy/architecture.md) governs facade ownership and [architecture policy](../policy/architecture.md) governs facade ownership and
dependency direction. dependency direction.

9
docs/roadmap/implementation.md
View File

@@ -1,14 +1,17 @@
# Implementation plan: neutral forge delivery and credential preflight # Implementation plan: neutral forge delivery and credential preflight
Status: implementation complete; Stages 1–10 are complete. Status: implementation complete; Stages 1–10 are complete.
Follow-up review corrections are tracked in [remediation](remediation.md).
## Purpose and execution ## Purpose and execution
Implement the target in the [feature roadmap](forge-boundary.md). That document Implement the target in the [feature roadmap](forge-boundary.md). That document
owns scope and user choices; this plan owns concrete design and ordered work. owns scope and user choices; this plan owns concrete design and ordered work.
The planning baseline is `44823ce`; source implementation remains unchanged The historical planning baseline was `44823ce`, whose source implementation
from `ac78e7d`. Gitea delivery, token files, and `forbidden_files` work today. was unchanged from `ac78e7d`. It included Gitea delivery, token files, and
The neutral destination and credential preflight are planned. `forbidden_files`. The neutral destination and credential preflight were the
planned additions. The sections below retain the original implementation plan;
the completed stages record its execution.
Execute Stage 1 through Stage 10 in order as one end-to-end sprint. Each stage Execute Stage 1 through Stage 10 in order as one end-to-end sprint. Each stage
is a focused Luna implementation task. Intermediate stages may leave callers is a focused Luna implementation task. Intermediate stages may leave callers

7
docs/roadmap/remediation.md
View File

@@ -174,7 +174,12 @@ guarantee that authorization will remain valid during later operations.
## 4. Align roadmap completion records — P3 ## 4. Align roadmap completion records — P3
Status: open. Status: complete.
**Completed:** Marked the feature roadmap's implementation complete, labeled
both planning baselines as historical, and linked both plans to this
remediation record. Reviewed the status wording against the completed stages
and retained the plans for release-preparation cleanup.
**Evidence:** [feature roadmap](forge-boundary.md) and **Evidence:** [feature roadmap](forge-boundary.md) and
[implementation plan](implementation.md). [implementation plan](implementation.md).