docs(repo): make GitLab the forge in the rules, ADRs and agent docs #507

2026-10-13T11:16:35Z

root commented

2026-10-13 11:16:35 +00:00

(Migrated from gitlab.core-project.space)

Summary

The rule files catch up with the switch: GitLab is the forge, GitHub a push mirror. The owner asked for this dedicated merge request.

 docs/adr/
-  0029  production and PR previews on the VPS, pulled from GHCR          accepted
+  0029  …                                                                superseded by 0036
+  0036  production and MR previews on the VPS, pulled from the GitLab registry
+  0037  a self-hosted GitLab is the forge; GitHub is a push mirror
 docs/agents/issue-tracker.md   gh → glab / glab api; hierarchy and blocking live in ## Parent / ## Blocked by
 CLAUDE.md, CONTRIBUTING.md, README.md   GitHub Actions, GHCR, PR wording → GitLab CI, registry, merge requests
 forked skills (to-spec, to-tickets, code-review, ADR-FORMAT)   gh → glab

Vocabulary: the vendored skills (implement, implement-spec, pr, wayfinder, …) keep saying "PR"; issue-tracker.md and CLAUDE.md define a PR as a GitLab merge request, so upstream updates stay clean.
No native sub-issues or blocking links on GitLab CE: the ## Parent and ## Blocked by body sections become the source of truth, mirrored by a relates_to link per pair, as the issue import already did.

Evidence

Before: issue-tracker.md sends agents to gh issue create on a repository that is now a mirror; CLAUDE.md names GitHub Issues as the tracker.
After: every command in issue-tracker.md is a glab subcommand or a glab api call on an endpoint checked against this instance (issue links on #354, MR discussions and diffs on !505).
The five commands pass locally; lint:adr reports 37 ADRs, each numbered once and indexed.

Merge Danger

Door: two-way

A revert restores the GitHub wording; the ADRs only record the switch already made by !505.

Blast Radius: agents

Every agent session reads these files: until glab is installed and logged in (glab auth login --hostname gitlab.core-project.space), tracker operations fail loudly rather than writing to GitHub. ADR 0037's "Why" states only the forces observed during the migration; the owner may add the original motivation.

## Summary The rule files catch up with the switch: GitLab is the forge, GitHub a push mirror. The owner asked for this dedicated merge request. ```diff docs/adr/ - 0029 production and PR previews on the VPS, pulled from GHCR accepted + 0029 … superseded by 0036 + 0036 production and MR previews on the VPS, pulled from the GitLab registry + 0037 a self-hosted GitLab is the forge; GitHub is a push mirror docs/agents/issue-tracker.md gh → glab / glab api; hierarchy and blocking live in ## Parent / ## Blocked by CLAUDE.md, CONTRIBUTING.md, README.md GitHub Actions, GHCR, PR wording → GitLab CI, registry, merge requests forked skills (to-spec, to-tickets, code-review, ADR-FORMAT) gh → glab ``` - **Vocabulary:** the vendored skills (`implement`, `implement-spec`, `pr`, `wayfinder`, …) keep saying "PR"; `issue-tracker.md` and `CLAUDE.md` define a PR as a GitLab merge request, so upstream updates stay clean. - **No native sub-issues or blocking links on GitLab CE:** the `## Parent` and `## Blocked by` body sections become the source of truth, mirrored by a `relates_to` link per pair, as the issue import already did. ## Evidence - **Before:** `issue-tracker.md` sends agents to `gh issue create` on a repository that is now a mirror; `CLAUDE.md` names GitHub Issues as the tracker. **After:** every command in `issue-tracker.md` is a `glab` subcommand or a `glab api` call on an endpoint checked against this instance (issue links on #354, MR discussions and diffs on !505). - The five commands pass locally; `lint:adr` reports 37 ADRs, each numbered once and indexed. ## Merge Danger **Door:** two-way A revert restores the GitHub wording; the ADRs only record the switch already made by !505. **Blast Radius:** agents Every agent session reads these files: until `glab` is installed and logged in (`glab auth login --hostname gitlab.core-project.space`), tracker operations fail loudly rather than writing to GitHub. ADR 0037's "Why" states only the forces observed during the migration; the owner may add the original motivation.