chore!: rename the Go module path to umbra #285
No reviewers
coilysiren
Labels
No labels
burndown-2026-06
sunday-sprint
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/umbra!285
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/rename-module-path"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The repo has been
coilyco-flight-deck/umbraon Forgejo for a while; the module path had not caught up. It is nowforgejo.coilysiren.me/coilyco-flight-deck/umbra, and the product name in prose follows it.151 files, 463 lines, purely mechanical. Full gate green (
build,vet,tidy,test,lint0 issues).BREAKING, but not disruptive: consumers requiring the old path must bump. They pin specific commits per the v0.x contract, so nothing breaks until each chooses to.
Deliberately NOT renamed
Four things carry the old name on purpose. Each would be a silent breakage, not a compile error.
CLIGUARD_JAILED/CLIGUARD_NO_SANDBOX/CLIGUARD_REALBIN_*A runtime env contract, set in 10+ live places across two other repos: agentic-os (
ci.yml,promote.yml,docker/dev-base/verify-common.sh,tests/test_aosguard.py) and coilyco-bridge/deploy (six deploy workflows). Renaming these stops those opt-outs from being honoured with no error at all - the sandbox posture in CI changes silently. Wants a release that accepts both spellings before the old one drops.pkg/config.FallbackAppDir = ".cli-guard"A live on-disk path.
~/.cli-guard/audit/<repo-slug>.jsonlholds real audit logs and is documented in the kai-linux-env skill. Changing it orphans existing history - that is a migration, not a rename.DepLock.CLIGuardand itsjson:"cliGuard"tagSerialized into every consumer's
specverb.lock. AOS's committed lock currently reads"cliGuard": "v0.132.0". Renaming the tag turns an old lock into a silently empty ref rather than a loud mismatch. Belongs with a deliberate lock-format change, alongside the exportedCLIGuardRef/CLIGuardReplace/DefaultCLIGuardRefidentifiers.github.com/coilysiren/cli-guardURLs - 23 refs across 6 filesThe GitHub mirror still carries the old name and answers 200;
github.com/coilysiren/umbra404s. Renaming these now points the README badges, docs links andmkdocs.ymlrepo_urlat dead pages. Unblocks as soon as the mirror is renamed. (Bothcoilysiren.github.ioPages URLs already 404 independently of this, so the docs site is not currently published either way.)Follow-up required in AOS
.specgen/guardfiles/specverb.lockstill pins the old module path (3 occurrences).specgen genwas verified working against the renamed tree and emits the new path, but AOS needs aspecgen lockre-run after this ships, plus itsDockerfile,scripts/aos-release-build.sh,scripts/ci/repo-test-gate.shandaos-cli/repositories/sealed-repos.gitignoreupdated - 5 files carrying the path.ward (104 files) and mcp-beaver (7 files) each need their own bump when convenient; both keep building on their current pins until then.
Refs #282.
The repo has been coilyco-flight-deck/umbra on Forgejo for a while; the module path had not caught up. It now reads `forgejo.coilysiren.me/coilyco-flight-deck/umbra`, and the product name in prose follows it. BREAKING: consumers requiring the old path must bump. They pin specific commits per the v0.x contract, so nothing breaks until they choose to. Deliberately NOT renamed, each for a reason: CLIGUARD_JAILED / CLIGUARD_NO_SANDBOX / CLIGUARD_REALBIN_* Runtime env contract, set in 10+ live places across agentic-os and coilyco-bridge/deploy (ci.yml, promote.yml, verify-common.sh, test_aosguard.py, six deploy workflows). Renaming silently stops those opt-outs and changes sandbox posture in CI with no error. Wants a release that accepts both names before the old one drops. pkg/config.FallbackAppDir = ".cli-guard" A live on-disk path. ~/.cli-guard/audit/<repo-slug>.jsonl holds real audit logs and is documented in kai-linux-env. Changing it orphans history; wants a migration, not a rename. DepLock.CLIGuard `json:"cliGuard"` and the CLIGuard* identifiers The json tag is serialized into every consumer's specverb.lock. Renaming it turns an old lock into a silently empty ref instead of a loud mismatch. Belongs with a lock-format change. github.com/coilysiren/cli-guard URLs (23 refs, 6 files) The GitHub mirror still carries the old name and answers 200; umbra 404s. Renaming these now would point the README badges, docs links and mkdocs repo_url at dead pages. Unblocks once the mirror is renamed. Verified: full gate green, and specgen renders AOS guardfiles emitting the new module path. AOS's committed specverb.lock still pins the old path and needs a `specgen lock` re-run after this ships. Co-authored-by: Kai Siren <coilysiren@gmail.com> Co-authored-by: Claude <noreply@anthropic.com>