chore: point MSD at git.golem15.com/golem15/msd-core

The fork lives on the golem15 Gitea forge, not GitHub. Package identity now
parses either host and derives in-place raw URLs for Gitea; the identity-drift
lint accepts the new host; README drops GitHub-only badges and the npm
quickstart in favour of the checkout installer.

docs/adr/0011-review-default-reviewers.md

@@ -19,7 +19,7 @@ Ratified by explicit maintainer directive; the Status field had sat stale at "Pr
 - Four test files are present and current: `tests/review-default-reviewers-config.test.cjs`, `tests/review-default-reviewers-resolution.test.cjs`, `tests/review-default-reviewers-workflow.test.cjs`, `tests/review-reviewer-instances.test.cjs`.
 - `.changeset/archived/daring-badgers-munch.md` (type: Added, pr: 3464) is archived, confirming release tooling already processed it.
 
-Governance state: the owning issue (`#3079`, referenced above) and its landing PR (`#3464`) both 404 against the current `golem15com/msd-core` tracker — their numbering belongs to a predecessor repo whose issue space predates this repo's 2026-05 range (which topped out near `#540`), consistent with known predecessor-repo numbering rather than a fabricated reference. No in-tracker close event is directly checkable; the shipped-code evidence above substitutes for it.
+Governance state: the owning issue (`#3079`, referenced above) and its landing PR (`#3464`) both 404 against the current `golem15/msd-core` tracker — their numbering belongs to a predecessor repo whose issue space predates this repo's 2026-05 range (which topped out near `#540`), consistent with known predecessor-repo numbering rather than a fabricated reference. No in-tracker close event is directly checkable; the shipped-code evidence above substitutes for it.
 
 **Known gaps at ratification:** two of the ADR's own non-blocking open questions remain genuinely unresolved — Q-2 (`--no-default` flag) and Q-3 (`review.profiles.*` namespace) — exactly as the ADR itself scoped them as future/non-blocking, so this is expected rather than a regression.
 

docs/adr/22-plan-drift-guard.md

@@ -2,7 +2,7 @@
 
 - **Status:** Accepted — ratified 2026-07-17 (originally Proposed 2026-05-29); see "Ratification" below
 - **Date:** 2026-05-29
-- **Issue:** golem15com/msd-core#22
+- **Issue:** golem15/msd-core#22
 
 ## Ratification (2026-07-17): Proposed → Accepted
 
@@ -16,7 +16,7 @@ Ratified by explicit maintainer directive; the Status field sat at Proposed for
 - `msd-core/workflows/plan-phase.md` §7.9 ("Regenerate API-SURFACE.md (intel gate)") regenerates the surface only when the intel step hook is active and injects it into the planner prompt labeled "HINT ONLY... MAY BE INCOMPLETE... Never treat the surface as exhaustive" — matching Part 1 point 2 verbatim.
 - `msd-core/workflows/settings.md` and `msd-core/workflows/new-project.md` surface `plan_review.source_grounding` as a "Drift Guard" toggle/setup question; `docs/CONFIGURATION.md` documents both config keys, explicitly marking authority rungs 2-4 (treesitter/lsp/scip) as reserved with no effect in the current release.
 
-Governance: owning issue golem15com/msd-core#22 — CLOSED, stateReason COMPLETED, closed 2026-05-30T21:08:13Z, labeled `enhancement` + `approved-feature`.
+Governance: owning issue golem15/msd-core#22 — CLOSED, stateReason COMPLETED, closed 2026-05-30T21:08:13Z, labeled `enhancement` + `approved-feature`.
 
 ## Context
 
@@ -88,7 +88,7 @@ Locked sub-decisions:
 - **Hard-block on any MISSING (as originally proposed).** Rejected for rung 0–1: false positives from dynamic/re-exported/generated symbols would block valid plans and get the default-on guard switched off. Retained only for rung >=3.
 
 ## References
-- Issue: golem15com/msd-core#22 (migrated from golem15com/msd-core#3813)
+- Issue: golem15/msd-core#22 (migrated from golem15/msd-core#3813)
 - Relates to #3802 (GitNexus first-class code intelligence) — rung 4 backend
 - arXiv:2409.20550 — hallucination taxonomy + RAG mitigation (modest gains)
 - arXiv:2502.05111 — grammar-constrained decoding (soft vs hard constraints)

docs/adr/230-introduce-next-integration-branch.md

@@ -11,7 +11,7 @@
 ## Why this is still `Proposed` (audited 2026-07-17)
 
 The architectural shift is real and operating: the live default branch is
-`next` (`gh api repos/golem15com/msd-core --jq .default_branch`), `.github/workflows/auto-backmerge.yml`
+`next` (`gh api repos/golem15/msd-core --jq .default_branch`), `.github/workflows/auto-backmerge.yml`
 runs unconditionally (`if: true`, not the Phase-1 `if: false` stub) and has
 produced real, merged `main → next` back-merge PRs across multiple releases
 (#671, #1337, #1673, and others), `release.yml` cherry-picks from
@@ -23,7 +23,7 @@ produced real, merged `main → next` back-merge PRs across multiple releases
 protection: `main` — "strict: 2 reviewer approvals, all CI green, ...
 restrict push to maintainers via PR only"; `next` — "loose: ... 'require
 branches up to date' OFF." Live settings invert this. `main`'s classic
-branch protection (verified via `gh api repos/golem15com/msd-core/branches/main/protection`
+branch protection (verified via `gh api repos/golem15/msd-core/branches/main/protection`
 and its `required_pull_request_reviews` / `required_status_checks`
 sub-resources) shows `required_approving_review_count: 1` (spec: 2),
 `required_status_checks` returns 404 "not enabled" (spec: all CI green
@@ -65,9 +65,9 @@ corrected `ref_name` conditions or removed as redundant with classic
 protection. Verify with:
 
 ```
-gh api repos/golem15com/msd-core/branches/main/protection/required_pull_request_reviews --jq .required_approving_review_count   # expect 2
-gh api repos/golem15com/msd-core/branches/main/protection/required_status_checks                                                # expect 200, not 404
-gh api repos/golem15com/msd-core/branches/main/protection --jq .allow_force_pushes.enabled                                      # expect false
+gh api repos/golem15/msd-core/branches/main/protection/required_pull_request_reviews --jq .required_approving_review_count   # expect 2
+gh api repos/golem15/msd-core/branches/main/protection/required_status_checks                                                # expect 200, not 404
+gh api repos/golem15/msd-core/branches/main/protection --jq .allow_force_pushes.enabled                                      # expect false
 ```
 
 Until then, either bring `main`'s protection into line with the Decision