docs(specs): Forji mobile PAT v0 prebuild + execution prompt (#133) #334

Merged

pdurlej merged 1 commit from claude/forji-mobile-pat-prebuild into main

2026-05-23 10:31:14 +02:00

claude commented

2026-05-17 17:58:21 +02:00

Collaborator

Summary

Batch E (mobile/Forji) prebuild. Pre-implementation Spec Kit for 3 outstanding upstream PR drafts identified in 2026-05-09 three-model synthesis (Opus + GPT-5.5 Pro + Iskra) after operator's PR#1 (secana/ForgejoKit#3) + PR#2 (secana/Forji#31) landed in flight.

What's prepared

Slice	Upstream target	Goal	Tier
(a)	`secana/Forji` PR0	Fix multi-instance duplicate server crash	Lite
(b)	`secana/ForgejoKit` + `secana/Forji` PR3	PAT capability checker	Full
(c)	`secana/Forji` PR4	Keychain v2 / stable account identity	Full

Codex prepares branches in pdurlej/Forji + pdurlej/ForgejoKit forks on codeberg (both exist). Operator submits upstream via codeberg UI when ready (Constitution P3 — operator gates upstream maintainer relationship).

Files

docs/specs/forji-mobile-pat-v0/README.md — summary + read order + cross-references
docs/specs/forji-mobile-pat-v0/00-constitution.md — 8 hard principles (P1 no PAT leakage sacred, P3 operator submits, P7 stable user.id identity, P8 error class distinguishability) + sacred boundary + D1-D7 decisions queue
docs/specs/forji-mobile-pat-v0/03-tasks.md — per-slice tasks with bash commands, acceptance, stop conditions, reporting format
prompts/codex-forji-mobile-pat.md — companion execution prompt (cross-repo nature highlighted, codeberg PAT pre-flight, upstream relationship tone)

Why this prebuild matters (product framing)

Mobile triage is operator-on-duty in pocket. F-series cutover ops, Iskra status checks during family time, agent-created issue triage during demos — all depend on reliable mobile Forgejo access. Forji is the only viable iOS Forgejo client; if it's unreliable, operator is chained to laptop.

Pattern

Mirrors #323-#325 (Agent Access Plane, Wake Bus, Scheduler Observability) Spec Kit pattern, with Batch E variant for cross-repo upstream contribution work.

Slices 01-specify / 02-plan / 04-implement-notes deferred — constitution + tasks + execution prompt are minimum viable for codex pickup. Codex can read 2026-05-09 synthesis in #133 body for fuller context.

Tier

Trivial per ADR-0007 (docs-only, no code / schema / runtime / sacred-path mutation).

Refs #133; companion to upstream secana/ForgejoKit#3 + secana/Forji#31

## Summary Batch E (mobile/Forji) prebuild. Pre-implementation Spec Kit for 3 outstanding upstream PR drafts identified in 2026-05-09 three-model synthesis (Opus + GPT-5.5 Pro + Iskra) after operator's PR#1 (`secana/ForgejoKit#3`) + PR#2 (`secana/Forji#31`) landed in flight. ## What's prepared | Slice | Upstream target | Goal | Tier | |---|---|---|---| | (a) | `secana/Forji` PR0 | Fix multi-instance duplicate server crash | Lite | | (b) | `secana/ForgejoKit` + `secana/Forji` PR3 | PAT capability checker | Full | | (c) | `secana/Forji` PR4 | Keychain v2 / stable account identity | Full | Codex prepares branches in `pdurlej/Forji` + `pdurlej/ForgejoKit` forks on codeberg (both exist). Operator submits upstream via codeberg UI when ready (Constitution P3 — operator gates upstream maintainer relationship). ## Files - `docs/specs/forji-mobile-pat-v0/README.md` — summary + read order + cross-references - `docs/specs/forji-mobile-pat-v0/00-constitution.md` — 8 hard principles (P1 no PAT leakage sacred, P3 operator submits, P7 stable user.id identity, P8 error class distinguishability) + sacred boundary + D1-D7 decisions queue - `docs/specs/forji-mobile-pat-v0/03-tasks.md` — per-slice tasks with bash commands, acceptance, stop conditions, reporting format - `prompts/codex-forji-mobile-pat.md` — companion execution prompt (cross-repo nature highlighted, codeberg PAT pre-flight, upstream relationship tone) ## Why this prebuild matters (product framing) Mobile triage is **operator-on-duty in pocket**. F-series cutover ops, Iskra status checks during family time, agent-created issue triage during demos — all depend on reliable mobile Forgejo access. Forji is the only viable iOS Forgejo client; if it's unreliable, operator is chained to laptop. ## Pattern Mirrors #323-#325 (Agent Access Plane, Wake Bus, Scheduler Observability) Spec Kit pattern, with Batch E variant for cross-repo upstream contribution work. Slices 01-specify / 02-plan / 04-implement-notes deferred — constitution + tasks + execution prompt are minimum viable for codex pickup. Codex can read 2026-05-09 synthesis in #133 body for fuller context. ## Tier Trivial per ADR-0007 (docs-only, no code / schema / runtime / sacred-path mutation). Refs #133; companion to upstream `secana/ForgejoKit#3` + `secana/Forji#31`

claude added 1 commit

2026-05-17 17:58:21 +02:00

docs(specs): Forji mobile PAT v0 prebuild + execution prompt (#133 )

base-is-main / guard (pull_request) Successful in 1s

Details

canary-required / collect-diff (pull_request) Successful in 4s

Details

patchwarden-pr-sanity / collect-diff (pull_request) Successful in 3s

Details

canary-required / canary (pull_request) Successful in 12s

Details

patchwarden-pr-sanity / sanity (pull_request) Successful in 20s

Details

49f2ea783a

Pre-implementation Spec Kit for outstanding upstream Forji + ForgejoKit
contributions after operator's PR#1 (secana/ForgejoKit#3) + PR#2
(secana/Forji#31) landed in flight upstream.

Three remaining upstream PR drafts from 2026-05-09 three-model synthesis
(Opus + GPT-5.5 Pro + Iskra):

- PR0 (Forji): multi-instance duplicate server crash (Lite tier)
- PR3 (ForgejoKit + Forji): PAT capability checker (Full tier)
- PR4 (Forji): Keychain v2 / stable account ID via Forgejo user.id
  with atomic per-entry migration (Full tier)

Spec Kit pattern from #323-#325 (Batch E variant — cross-repo):
- README.md: summary + read order + cross-references
- 00-constitution.md: 8 hard principles (P1 no PAT leakage sacred,
  P2 upstream-friendly diffs, P3 operator submits final upstream,
  P4 reproducible without real PAT, P5 Issues+labels primary surface,
  P6 repo-scoped PAT future mode, P7 stable user.id identity,
  P8 error class distinguishability) + sacred boundary + D1-D7
- 03-tasks.md: per-slice tasks with bash commands, acceptance,
  stop conditions, reporting format

Companion execution prompt at prompts/codex-forji-mobile-pat.md:
- Safety / production boundary explicit (no upstream submit by codex,
  no PAT/iOS/server-config modification, no real PAT in output)
- Pre-flight identity + codeberg PAT check
- Per-slice instructions with pre-conditions
- Stop conditions per ADR-0018 + Constitution P1
- Cross-repo nature highlighted

Slices 01-specify, 02-plan, 04-implement-notes deferred to slice-(b)
start; codex can read 2026-05-09 synthesis in #133 body for fuller
context. Constitution + tasks + execution prompt are minimum viable
for codex pickup.

Tier: Trivial per ADR-0007 (docs-only, no code/schema/runtime mutation).

Refs #133; companion to upstream secana/ForgejoKit#3 + secana/Forji#31

claude referenced this pull request

2026-05-17 17:58:37 +02:00

investigate(mobile): fix Forji iOS Forgejo PAT auth and prepare upstream PRs #133