codex
1abac4274b
These workplans exist only in the retired local hub. Their random pre-ADR-007 identifiers are refused by C-06 as stale references, so they cannot be registered. Deriving from the canonical record id takes no identity from anything: central does not hold them and the old ids die with the cache. Records central already holds were deliberately left untouched. Refs CUST-WP-0068-T06 Assistant: claude-code Assistant-Model: opus Assistant-Process: 2583210@bnt-lap001 Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
3.6 KiB
| id | type | title | domain | repo | status | owner | topic_slug | priority | created | updated | depends_on | related | state_hub_workstream_id | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ISSUE-WP-0006 | workplan | Forgejo-only forge + projection boundary (not ops queue) | infotech | issue-core | ready | grok | issue-core | medium | 2026-08-03 | 2026-08-03 |
|
4d465264-cbe1-56ba-84ed-bd580b649b76 |
ISSUE-WP-0006 — Forgejo-only projection boundary
Origin
ACT-ADR-005 and founder direction (2026-08-03):
- Gitea is no longer relevant — self-hosted forge is Forgejo only.
- issue-core must not be used as the ops claim queue for activity-core.
- issue-core remains the multi-tracker facade (project/link external issues).
Goal
Align code, docs, and env names so operators and agents never plan on Gitea, and so rein-aharness stops treating issue-core as the primary automation queue (handoff language to ops_run in ACTIVITY-WP-0026 / REIN-A-0002).
Tasks
T01 — Terminology sweep: Gitea → Forgejo (product language)
id: ISSUE-WP-0006-T01
status: todo
priority: high
state_hub_task_id: "927eee42-e22d-5c0d-a4f8-dcd36c53c8e9"
Sweep INTENT, SCOPE, README, ROADMAP, workplans, comments:
- Prefer Forgejo for the self-hosted forge product.
- Where code talks to the Forgejo HTTP API that is Gitea-compatible, say “Forgejo (Gitea-compatible API)” once — do not present Gitea as a supported second product or migration target.
- Rename operator-facing env docs that say
GITEA_*for forge access toFORGEJO_*or document aliases:FORGEJO_TOKENpreferred; legacyGITEA_*only as deprecated alias if code still requires it.
Done when: rg -i gitea in docs is zero for “we use Gitea”, or only
compatibility notes remain.
T02 — INTENT/SCOPE: ops queue non-goal
id: ISSUE-WP-0006-T02
status: todo
priority: high
state_hub_task_id: "a1d69a48-833b-5e5e-8286-14f5aba627f3"
Explicit section:
- Internal scheduled automation claim/execute → activity-core ops_run (ACT-ADR-005).
- issue-core does not provide the fleet ops claim queue.
POST /issues/= external tracker create/link only.- Default activity-core sink remains state-hub progress + ops_run; not rest to issue-core for Binky/FI.
Done when: INTENT/SCOPE quote ACT-ADR-005; no contradiction with “poll us for automation.”
T03 — Connector docs: projection path only
id: ISSUE-WP-0006-T03
status: todo
priority: medium
state_hub_task_id: "75eef8a3-abd7-50dd-9171-3488fda84da5"
Update AGENT_INTEGRATION / connector docs:
- Author work record in repo → hub index.
- Optional: project/link via issue-core to Forgejo (or GitHub/Jira later).
- Mapping UUID ↔
(backend=forgejo, external_id).
Done when: happy path diagram has no “activity-core → issue-core → harness” as the primary automation loop.
T04 — Coordinate rein-aharness intake docs
id: ISSUE-WP-0006-T04
status: todo
priority: low
state_hub_task_id: "5be0bce4-1816-599f-a98b-4fa1565a8b0e"
Message or PR note for REIN-A-0002-T06: issue-core poll = legacy/external only. No code change required in issue-core if rein owns the doc cut.
Done when: cross-link in ISSUE-WP-0006 and REIN-A-0002.
Acceptance
- No Gitea-as-product planning
- Projection boundary clear
- Ops claim queue explicitly out of scope for issue-core
Out of scope
- Implementing ops_run (ACTIVITY-WP-0026)
- Fixing Forgejo PAT for rest sink (only if projection needs it later)
- GitHub/Jira connectors