FM-4-followup operator-side GitLab e2e + dashboard evidence #694

Open
opened 2026-05-01 21:49:13 +00:00 by code-lead · 0 comments
Collaborator

Tracks the operator-side leg of FM-4 (#655) deferred from PR #693.

#693 landed CI-side coverage (gitlab-fm4-smoke.test.ts, 360 lines) plus the manual procedure in docs/multi-forge.md#fm-4-end-to-end-smoke-procedure. The remaining work needs a real GitLab project + a human at the dashboard, so it is split out here.

Acceptance criteria

  • Wire a throw-away GitLab project per docs/multi-forge.md §FM-4 manual procedure.
  • Run one issue → MR → review → merge → close loop end-to-end.
  • Capture artefacts on this issue:
    • GitLab issue + MR URLs
    • journalctl --user -u claude-hooks excerpt for each loop step
    • Dashboard screenshot showing the GitLab card under the correct column with the CI pill rendered
    • Side-panel screenshot deep-linking to the GitLab MR diff
  • If the dashboard does not render the GitLab card / pill / diff link correctly, file separate area:dashboard bugs.

Out of scope

  • Anything CI-runnable (covered by gitlab-fm4-smoke.test.ts).
  • Re-validating the Forgejo loop.

References

  • #655 (parent user story — kept open until artefacts land here)
  • #693 (CI-side coverage + procedure doc)
  • docs/multi-forge.md §FM-4 end-to-end smoke procedure
Tracks the operator-side leg of FM-4 (#655) deferred from PR #693. #693 landed CI-side coverage (`gitlab-fm4-smoke.test.ts`, 360 lines) plus the manual procedure in `docs/multi-forge.md#fm-4-end-to-end-smoke-procedure`. The remaining work needs a real GitLab project + a human at the dashboard, so it is split out here. ## Acceptance criteria - [ ] Wire a throw-away GitLab project per `docs/multi-forge.md` §FM-4 manual procedure. - [ ] Run one issue → MR → review → merge → close loop end-to-end. - [ ] Capture artefacts on this issue: - GitLab issue + MR URLs - `journalctl --user -u claude-hooks` excerpt for each loop step - Dashboard screenshot showing the GitLab card under the correct column with the CI pill rendered - Side-panel screenshot deep-linking to the GitLab MR diff - [ ] If the dashboard does not render the GitLab card / pill / diff link correctly, file separate `area:dashboard` bugs. ## Out of scope - Anything CI-runnable (covered by `gitlab-fm4-smoke.test.ts`). - Re-validating the Forgejo loop. ## References - #655 (parent user story — kept open until artefacts land here) - #693 (CI-side coverage + procedure doc) - `docs/multi-forge.md` §FM-4 end-to-end smoke procedure
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
charles/claude-hooks#694
No description provided.