R-Dash Rename (R-Same → R-Dash) + GitHub Transfer (ARJ-TECH → ARJ999)

Decision

Codename finalized as R-Dash; GitHub repo transferred from ARJ-TECH organization to ARJ999 personal account. Commit 678121f (2026-04-17). 73 files touched, 346 insertions, 265 deletions. History preserved via GitHub rename + transfer (no new-repo creation). Migration sequence: gh repo rename r-same→r-dashn→r-dash, gh api transfer ARJ-TECH/r-dash → ARJ999/r-dash, local mv /opt/infra/r-same → /opt/infra/r-dash, git remote set-url to https://github.com/ARJ999/r-dash.git, sed cascade across 69 files with 7 patterns (r-same→r-dash, R-Same→R-Dash, rsame→rdash, RSAME→RDASH, r_same→r_dash, RSame→RDash, ARJ-TECH/r-dash→ARJ999/r-dash), rename packages/query-runner/r_same_query_runner → r_dash_query_runner, memory cascade (project_r_same.md → project_r_dash.md with same 7 patterns + MEMORY.md pointer update). ADR-0008 written superseding ADR-0001’s codename section. All verifications pass: grep returns 0 matches, all Python AST parse-clean, all TOML parse-clean, docker compose config valid.

Rationale

User directives explicit: “Repo Name i am changing as R-Dash” (second message after “R-Dashn” typo) and “i want github repo under https://github.com/ARJ999, not sure why ARJ Tech is used”. Law 2 Zero Ambiguity requires the codename, repo slug, Python modules, DB name, env prefix, error codes, cookie name, container names — every surface — to share one name. Sed cascade across all text files plus renaming the Python package directory ensures zero stale references. ADR-0008 written rather than editing ADR-0001 in place avoids false history (ADR-0001 retains its original record with updated current-state text via sed; ADR-0008 documents the rename itself as a first-class decision). Ownership transfer via gh api —method POST repos/…/transfer is the only non-destructive path; fresh-repo creation was rejected because it would lose 7 commits of working code. Personal account (ARJ999) fits the “VPS is AJ’s personal R&D bedrock; perfect here → transfer to Runwal Corp later” frame from user_identity_enterprise.md better than ARJ-TECH org (which was my incorrect default when I first couldn’t find runwal-ai). Create fresh empty repo at ARJ999/r-dash and push existing commits to it (rejected: transfer preserves history cleaner than re-push + redirects any external bookmark). Keep under ARJ-TECH org (rejected: user explicitly directed ARJ999). Write ADR-0008 but leave prior ADRs with “R-Same” text (rejected: Law 2 violation to have ADRs say R-Same while code says R-Dash). Edit ADR-0001 in place without ADR-0008 (rejected: rename itself deserves a first-class decision record for future-session clarity). Leave env var prefix RSAME_ to avoid breaking .env files (rejected: we have no deployed environments yet; pre-prod is the cheapest time to rename). Skip renaming the Python package directory and just rename the slug (rejected: Python imports would break — the r_same_query_runner dir had to move to r_dash_query_runner to match pyproject packages = [...]).

Alternatives Rejected

Outcome

Pending