apply-agentic-os-hooks OWNER='coilysiren' is stale post org-migration #115

New issue

Closed

opened 2026-05-31 01:54:48 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-05-31 01:54:48 +00:00

Owner

scripts/apply-agentic-os-hooks.py hardcoded OWNER = "coilysiren" and built its repo list from gh repo list coilysiren. After the org migration to coilyco-bridge / coilyco-flight-deck, only 3 source repos remain under coilysiren (algo-zone, coilysiren, website), so the pre-commit hook-block rollout was silently skipping every migrated repo.

This is a local-fleet tool (it runs pre-commit install inside each checkout) and apply_to_repo() was already disk-gated, so the gh list only ever supplied candidate names. Fix: drive directly off the on-disk checkout set (every git working tree under ~/projects/coilysiren) instead. Owner-agnostic, migration-proof, no network dependency.

Mirror of the cross-org tracker coilysiren/agentic-os-kai#553; this issue exists so the same-repo closes-issue hook can bind the fix commit here.

`scripts/apply-agentic-os-hooks.py` hardcoded `OWNER = "coilysiren"` and built its repo list from `gh repo list coilysiren`. After the org migration to `coilyco-bridge` / `coilyco-flight-deck`, only 3 source repos remain under `coilysiren` (`algo-zone`, `coilysiren`, `website`), so the pre-commit hook-block rollout was silently skipping every migrated repo. This is a local-fleet tool (it runs `pre-commit install` inside each checkout) and `apply_to_repo()` was already disk-gated, so the `gh` list only ever supplied candidate names. Fix: drive directly off the on-disk checkout set (every git working tree under `~/projects/coilysiren`) instead. Owner-agnostic, migration-proof, no network dependency. Mirror of the cross-org tracker [coilysiren/agentic-os-kai#553](https://forgejo.coilysiren.me/coilyco-bridge/agentic-os-kai/issues/553); this issue exists so the same-repo `closes-issue` hook can bind the fix commit here.

coilysiren referenced this issue from a commit

2026-05-31 01:55:15 +00:00

fix: drive hook rollout off on-disk checkout set post org-migration

coilysiren closed this issue

2026-05-31 01:55:15 +00:00

coilysiren commented

2026-06-01 10:47:36 +00:00

Author

Owner

Adjacent gap: the injected hook-SOURCE URL is still `coilysiren/agentic-os`

This issue fixed OWNER / the consumer repo-list (which repos to roll out to), driving off the on-disk checkout set. That part is done and correctly closed.

But a distinct stale ref survived, in the same files, because it's a different axis - the hook-source URL that gets injected into each consumer's .pre-commit-config.yaml:

scripts/apply-agentic-os-hooks.py:120 - - repo: https://github.com/coilysiren/agentic-os (the literal block stamped into every consumer)
scripts/apply-agentic-os-hooks.py:4 - same URL in the module docstring
scripts/audit-pre-commit-coverage.py:45 - AGENTIC_OS_URL = "https://github.com/coilysiren/agentic-os"

agentic-os's own GitHub home is now coilyco-flight-deck/agentic-os. GitHub's transfer-redirect keeps the old URL resolving for now, so consumers' pre-commit still works - but it's latent: a fresh pre-commit install/autoupdate against a re-created repo at the old path, or the redirect being dropped, breaks the fleet hook block.

This is load-bearing and fleet-coupled (changing it means re-rolling the managed block to every consumer via apply-agentic-os-hooks), so it was deliberately NOT swept in the 2026-06-01 Bucket B org-prefix pass. Flagging here rather than reopening, since this issue's own scope (OWNER/list) is genuinely complete. Suggest a dedicated follow-up (or fold into the agentic-os#534 Bucket A rollout).

## Adjacent gap: the injected hook-SOURCE URL is still `coilysiren/agentic-os` This issue fixed `OWNER` / the consumer repo-**list** (which repos to roll out *to*), driving off the on-disk checkout set. That part is done and correctly closed. But a **distinct** stale ref survived, in the same files, because it's a different axis - the hook-**source** URL that gets injected into each consumer's `.pre-commit-config.yaml`: - `scripts/apply-agentic-os-hooks.py:120` - ` - repo: https://github.com/coilysiren/agentic-os` (the literal block stamped into every consumer) - `scripts/apply-agentic-os-hooks.py:4` - same URL in the module docstring - `scripts/audit-pre-commit-coverage.py:45` - `AGENTIC_OS_URL = "https://github.com/coilysiren/agentic-os"` agentic-os's own GitHub home is now `coilyco-flight-deck/agentic-os`. GitHub's transfer-redirect keeps the old URL resolving for now, so consumers' pre-commit still works - but it's latent: a fresh `pre-commit install`/`autoupdate` against a re-created repo at the old path, or the redirect being dropped, breaks the fleet hook block. This is load-bearing and fleet-coupled (changing it means re-rolling the managed block to every consumer via `apply-agentic-os-hooks`), so it was deliberately NOT swept in the 2026-06-01 Bucket B org-prefix pass. Flagging here rather than reopening, since this issue's own scope (OWNER/list) is genuinely complete. Suggest a dedicated follow-up (or fold into the agentic-os#534 Bucket A rollout).

coilysiren referenced this issue

2026-06-01 10:56:06 +00:00

Repoint coilysiren/ org-prefix references in agentic-os (Bucket B), mirror of agentic-os-kai#534 #123