Date: 2026-10-01 Status: Accepted

Package identity moves from rocky-hq to erid-tech

Context

The GitHub org was renamed rocky-hq → erid-tech (2026-09-25). Repo URLs were repointed (#131), but package identity was deliberately left alone pending a decision: the npm scope @rocky-hq/* and the Go module paths github.com/rocky-hq/contracts/go and github.com/rocky-hq/hearth.

Measured on 2026-10-01:

npm is already broken. GitHub Packages only serves a scope that matches the owning account. Since the rename, console's smoke workflow has failed on every run (first red 2026-09-29) with npm package "contracts" does not exist under owner "rocky-hq". A new @rocky-hq/* version cannot be published from erid-tech either.
The old name is unclaimed. gh api orgs/rocky-hq and users/rocky-hq both return 404. Everything that still resolves through GitHub's rename redirect (Go module fetches, the insteadOf auth rewrite in CI, submodule URLs) can be taken over by whoever registers the name, and the redirect stops the moment anyone does.
Our own rule points the same way. 2026-05-03-phase-5-go-conventions.md makes the GitHub URL the canonical Go import path, with no vanity path.
The blast radius is small. Every consumer found is inside this superproject and its submodules; all packages are private (GitHub Packages / GOPRIVATE), so nothing outside the org pins the old names.

Decision

Package identity follows the org:

was	now	landed
`@rocky-hq/contracts`	`@erid-tech/contracts` 0.5.0	erid-tech/contracts#8, tag `v0.5.0`
`github.com/rocky-hq/contracts/go`	`github.com/erid-tech/contracts/go`	same commit, tag `go/v0.5.0`
`github.com/rocky-hq/hearth`	`github.com/erid-tech/hearth`	erid-tech/hearth#9
console dependency + `.npmrc` scope	`@erid-tech/contracts@^0.5.0`	erid-tech/console#54
`@rocky-hq/design-tokens` (draft, unpublished)	`@erid-tech/design-tokens`	this PR
`GOPRIVATE` / `insteadOf` in CI	`github.com/erid-tech/*`	hearth#9, this PR (`e2e.yml`)

Not renamed:

Runtime label keys rocky-hq.io/* on hearth-managed containers. They are wire identifiers on running workloads; renaming them orphans existing containers and needs a migration of its own.
The CI secret name ROCKY_HQ_RO_TOKEN. The fine-grained PAT is bound to repositories, which survived the rename.
Historical specs, plans, decisions and MILESTONES rows.

Consequences

No placeholder rocky-hq org (operator ruling, 2026-10-02): after this change nothing in the build resolves through the rename redirect, so the old name carries no dependency. Residual exposure is only stale references (old clones' remotes, historical docs).
@rocky-hq/contracts@0.4.0 and Go v0.3.0 stay where they are; nothing consumes them after console#54 and hearth#9.
2026-05-02-rocky-consolidation-policy.md (0003) and 2026-05-03-phase-5-go-conventions.md (0004) carry amendments pointing here.

Sign-off

Directed by the operator (alex@devarno.com) on 2026-10-01 after review of the evidence above.