Prefer Forgejo as the self-hosted forge product. Keep Gitea only as the
Gitea-compatible API identifier (module backends/gitea, type string
gitea). FORGEJO_TOKEN is preferred; GITEA_* remains a deprecated alias.
INTENT/SCOPE quote ACT-ADR-005: issue-core is not the fleet ops claim
queue. Connector docs describe repo work record → hub index → optional
Forgejo projection, not activity-core → issue-core → harness.
Assistant: grok
Assistant-Session: 01a09dc6-3f0d-7c93-8b11-8e83c0623d49
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
Retarget INTENT, SCOPE, README, ROADMAP, and agent docs from "task landing
zone" to external-tracker connector per work-record canon and architecture
draft §4.2. Add UUID↔external-id mapping design; mark ISSUE-WP-0004 finished
and cross-file activity-core ACTIVITY-WP-0022 for IssueSink policy.
INTENT.md currently claims to be 'a single, observable place where tasks
land' -- exactly the landing-zone role CUST-WP-0060's founder-reviewed
architecture draft (WorkOrchestrationArchitectureDraft.md v0.2, section
4.2) assigned away from issue-core, decided while reviewing the live
incident this repo caused: activity-core's daily-todo-md-stale-review
routed through IssueSink -> issue-core -> Forgejo, producing 5 issues
nobody was meant to see (now paused).
5 tasks: rewrite INTENT.md/SCOPE.md/README/ROADMAP for the connector
framing (work records originate as repo files per ADR-001; issue-core
is the optional external-tracker projection), design (not implement)
the UUID<->external-id mapping surface, and file the activity-core-side
follow-up to fix the IssueSink default. Docs-only scope; stage-3
implementation work stays in the-custodian.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
