Review: Rename westside-app repo to westside-landing on Forgejo

review-587-2026-03-28 Doc

review ready

Project

Verdict: READY

Template Completeness

[x] Type
[x] Lineage
[x] Repo
[x] User Story
[x] Context
[x] File Targets
[x] Acceptance Criteria
[x] Test Expectations
[x] Constraints
[x] Checklist
[x] Related

All 11 sections present and complete.

Traceability

[x] story:WS-S26 label -- landing site rename
[x] arch:landing-site label -- architecture component
[x] Forgejo issue -- forgejo_admin/westside-app#147, open

File Targets

[x] Forgejo API PATCH endpoint -- valid, no code files targeted. Correct.
[x] Correctly notes .woodpecker.yaml uses CI_REPO and auto-adjusts

Repo Placement

OK -- Forgejo API rename must be issued against the current repo (westside-app). Filed on the correct repo.

Dependencies

[x] Blocker items #534 and #529 documented -- both verified as DONE on the board. Blocker is cleared.
[x] Correctly states this must complete before sub-tickets 2-4

Acceptance Criteria

4 criteria, all testable. curl command provided for site liveness check. Webhook verification via no-op push is reasonable. Agent can verify all 4.

Blast Radius

Low. This is an API rename only. Forgejo auto-redirects git remotes and webhooks. No code changes. Downstream work is explicitly scoped to sub-tickets 2-4.

Decomposition

1 API call + 2 verifications. Well under 5 minutes. No decomposition needed.

Recommendation

Minor note: blocked-by:ws-534 and blocked-by:ws-529 labels on the board item reference board items that are already done. These labels could be removed for cleanliness, but this is cosmetic and does not block the review.

No action needed.