Route profiles.OverridePath through the app-dir (follow-up from #50) #73

New issue

Closed

opened 2026-06-04 11:02:48 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-06-04 11:02:48 +00:00

Owner

Problem (follow-up from #50)

#50 made the app-dir configurable and routed config/paths.go, the four ttl-cache packages, and the dispatch queue dir through config.SetAppDir. It deliberately left profiles.OverridePath alone because that path couples a second consumer-name axis the app-dir change does not cover.

profiles/profiles.go hardcodes the global profile config at ~/.coily/coily.yaml:

return filepath.Join(home, ".coily", "coily.yaml"), nil

This is the same consumer-collision class #50 fixed: a second consumer (ward) would read coily's ~/.coily/coily.yaml.

Ask

Route the directory through config.GlobalDir() (so it becomes ~/<app-dir>/coily.yaml) to close the collision. Decide separately what to do with the coily.yaml filename, which is its own consumer-name axis (it also appears in repocfg.Filename and repocfg.LocalDirName, which are meant to be consumer-supplied). Either:

thread a configurable global-config filename alongside the app-dir, or
accept <app-dir>/coily.yaml as the convention and scrub only the dir.

Update profiles tests (they assert ~/.coily/coily.yaml).

Cross-ref

Follow-up from #50. Same generic-library contract: no consumer name as a default in the package.

## Problem (follow-up from #50) #50 made the app-dir configurable and routed `config/paths.go`, the four ttl-cache packages, and the dispatch queue dir through `config.SetAppDir`. It deliberately left `profiles.OverridePath` alone because that path couples a second consumer-name axis the app-dir change does not cover. `profiles/profiles.go` hardcodes the global profile config at `~/.coily/coily.yaml`: ```go return filepath.Join(home, ".coily", "coily.yaml"), nil ``` This is the same consumer-collision class #50 fixed: a second consumer (ward) would read coily's `~/.coily/coily.yaml`. ## Ask Route the **directory** through `config.GlobalDir()` (so it becomes `~/<app-dir>/coily.yaml`) to close the collision. Decide separately what to do with the `coily.yaml` **filename**, which is its own consumer-name axis (it also appears in `repocfg.Filename` and `repocfg.LocalDirName`, which are meant to be consumer-supplied). Either: - thread a configurable global-config filename alongside the app-dir, or - accept `<app-dir>/coily.yaml` as the convention and scrub only the dir. Update `profiles` tests (they assert `~/.coily/coily.yaml`). ## Cross-ref Follow-up from #50. Same generic-library contract: no consumer name as a default in the package.

coilysiren added this to the sunday-sprint milestone

2026-06-05 03:41:15 +00:00

coilysiren added the

sunday-sprint

label

2026-06-05 03:41:15 +00:00

coilysiren added the

label

2026-06-06 04:27:08 +00:00

coilysiren added

and removed

labels

2026-06-17 08:39:56 +00:00

coilysiren added

headless

and removed

labels

2026-06-18 06:16:32 +00:00

coilysiren commented

2026-06-18 07:30:51 +00:00

Author

Owner

🔒 Reserved by ward agent claude — container ward-cli-guard-issue-73-claude-3ff320a2 on host kais-macbook-pro.local is carrying this issue (reserved 2026-06-18T07:30:50Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

— Claude (she/her), via ward agent

🔒 Reserved by `ward agent claude` — container `ward-cli-guard-issue-73-claude-3ff320a2` on host `kais-macbook-pro.local` is carrying this issue (reserved 2026-06-18T07:30:50Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides.  — Claude (she/her), via `ward agent`

coilysiren referenced this issue from a commit

2026-06-18 07:50:01 +00:00

feat(profiles): route OverridePath through the app-dir + configurable registry file

coilysiren closed this issue

2026-06-18 07:50:01 +00:00