Record Gitea publication blocker
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Implementation Plan 0022: Coordinated Suite Upgrade
|
||||
|
||||
Status: ready
|
||||
Status: blocked — reviewed role publication requires Gitea Git authentication
|
||||
|
||||
Target executor: GPT-5.6-Terra
|
||||
|
||||
@@ -379,7 +379,14 @@ mark F0022 done, begin another feature, or push unrelated workspace history.
|
||||
|
||||
## Progress Notes
|
||||
|
||||
Plan approved; implementation has not started.
|
||||
Plan approved. Stage 1 publication is blocked. On 2026-09-29, all four exact
|
||||
reviewed revisions were present locally; clean worktrees and expected Gitea
|
||||
origins were confirmed. After fetching, each `origin/main` was three reviewed
|
||||
feature commits behind the selected revision and could fast-forward. The first
|
||||
normal push, for Scriptorium, failed because HTTPS Git could not read a
|
||||
username. No role revision was published, no downstream stage was started, and
|
||||
no stage is marked complete. Resume with authenticated access to the existing
|
||||
Gitea origins, then re-fetch and recheck outgoing history before pushing.
|
||||
|
||||
## Open Questions
|
||||
|
||||
|
||||
@@ -4,8 +4,10 @@ Last updated: 2026-09-29
|
||||
|
||||
Current milestone: Operational D&D pipeline deployment
|
||||
|
||||
Current focus: Implement Feature 0022's coordinated suite upgrade. The roadmap,
|
||||
default-inheritance policy, and staged plan are approved; implementation has not started.
|
||||
Current focus: Feature 0022's coordinated suite upgrade is blocked at reviewed
|
||||
role publication: the existing Gitea HTTPS origins have no usable Git write
|
||||
credential in this environment. The approved implementation has not advanced
|
||||
beyond its first stage.
|
||||
Features 0018 through 0021 are complete after independent review with no
|
||||
remediation findings. Follow the agreed
|
||||
[application upgrade sequence](roadmap/application-upgrade-sequence.md):
|
||||
@@ -45,7 +47,7 @@ is complete.
|
||||
| F0019 | Adopt Audita v2.0.1 | Audita role and workspace | done | Role `c3dd59f`, following `6137ff2` and `52f67fe`, passed independent review with no findings; [roadmap](roadmap/features/0019-audita-v2-adoption.md) records validation; suite pins unchanged |
|
||||
| F0020 | Adopt Notarius v0.8.1 | Notarius role and workspace | done | Role `6aef48b`, following `b1b922c` and `380b6a3`, passed independent review with no findings; [feature roadmap](roadmap/features/0020-notarius-v0-8-adoption.md) records evidence; suite pins unchanged |
|
||||
| F0021 | Adopt Narratio v3.0.0 | Narratio role and workspace | done | Role `3c0700b`, following `a28f22c` and `45f6836`, passed independent review with no findings; [feature roadmap](roadmap/features/0021-narratio-v3-adoption.md) records evidence; suite pins unchanged |
|
||||
| F0022 | Integrate the reviewed application upgrades | Pipeline role, collection, consumer, and workspace | ready | [Feature roadmap](roadmap/features/0022-coordinated-suite-upgrade.md) and [staged plan](roadmap/implementation.md) approved; ready for implementation |
|
||||
| F0022 | Integrate the reviewed application upgrades | Pipeline role, collection, consumer, and workspace | blocked | [Feature roadmap](roadmap/features/0022-coordinated-suite-upgrade.md) and [staged plan](roadmap/implementation.md) approved; reviewed role commits are ready locally but HTTPS push requires an authenticated Gitea Git credential |
|
||||
| A0001 | Audit completed standalone-role test suites | workspace and standalone roles | done | Findings recorded in `docs/roadmap/test-suite-audit-findings.md` |
|
||||
| R0001 | Simplify completed standalone-role test suites | workspace and standalone roles | done | Role commits `e08c63c`, `d2d0b9d`, and `cfecf37` passed implementation and independent review |
|
||||
|
||||
|
||||
Reference in New Issue
Block a user