Rename the kdlspecs Go package to specgen #244

Closed
opened 2026-07-23 18:18:43 +00:00 by coilyco-ops · 2 comments
Member

Follow-up to #243. The product binary is becoming specgen, while the public driver package still uses the http/kdlspecs import path and kdlspecs identifier.

Current audit finds no external Go imports in the coilyco-flight-deck or coilyco-bridge checkouts. The path is still public v0 API, so the rename should land as an explicit breaking change rather than being hidden inside the binary rename.

Acceptance:

  • Rename http/kdlspecs to http/specgen and package kdlspecs to package specgen.
  • Keep the nested renderer boundary explicit, likely http/specgen/codegen, unless repository evidence supports flattening it.
  • Update internal imports, release ldflags, tests, godoc-current.txt, and package documentation.
  • Verify all known consumer repositories for imports before landing.
  • State the v0 API break in the commit body and coordinate sequencing with the cli-guard to agent-guard module rename in #200.
  • Full tests and repository hooks pass.

History: #164 introduced the specgen family and #174 renamed it to kdl-specs. #243 changes only the product binary and deliberately leaves this import-path change separate.

Follow-up to #243. The product binary is becoming specgen, while the public driver package still uses the http/kdlspecs import path and kdlspecs identifier. Current audit finds no external Go imports in the coilyco-flight-deck or coilyco-bridge checkouts. The path is still public v0 API, so the rename should land as an explicit breaking change rather than being hidden inside the binary rename. Acceptance: - Rename http/kdlspecs to http/specgen and package kdlspecs to package specgen. - Keep the nested renderer boundary explicit, likely http/specgen/codegen, unless repository evidence supports flattening it. - Update internal imports, release ldflags, tests, godoc-current.txt, and package documentation. - Verify all known consumer repositories for imports before landing. - State the v0 API break in the commit body and coordinate sequencing with the cli-guard to agent-guard module rename in #200. - Full tests and repository hooks pass. History: #164 introduced the specgen family and #174 renamed it to kdl-specs. #243 changes only the product binary and deliberately leaves this import-path change separate.
Author
Member

WARD-WORKFLOW: done

details

Review: In-container review gate intentionally skipped because implementation and QA are role-separated. QA is a separate, opt-in exact-commit verification role bound to candidate commit 4329ee7.

workflow: merge-remote-main; review summary: skipped — role-separated exact-commit QA not requested

Summary: Renamed http/kdlspecs/package kdlspecs to http/specgen/package specgen; retained http/specgen/codegen; updated imports, tests, ldflags, and godoc. Known consumers are clear.

Felt: Clean mechanical v0 break; godoc relocation was noisy.
Confidence: High — local checks, hooks, release matrix, and Forgejo CI/promotion/release are green.
Surprises: Container PYTHONPATH shadowed one pinned hook; clearing it fixed the environment.
Follow-ups: Sequence #200 after this package-path break.

— Codex

WARD-WORKFLOW: done ✅ <details><summary>details</summary> Review: In-container review gate intentionally skipped because implementation and QA are role-separated. QA is a separate, opt-in exact-commit verification role bound to candidate commit `4329ee7`. workflow: merge-remote-main; review summary: skipped — role-separated exact-commit QA not requested Summary: Renamed `http/kdlspecs`/`package kdlspecs` to `http/specgen`/`package specgen`; retained `http/specgen/codegen`; updated imports, tests, ldflags, and godoc. Known consumers are clear. Felt: Clean mechanical v0 break; godoc relocation was noisy. Confidence: High — local checks, hooks, release matrix, and Forgejo CI/promotion/release are green. Surprises: Container `PYTHONPATH` shadowed one pinned hook; clearing it fixed the environment. Follow-ups: Sequence #200 after this package-path break. — Codex </details>
Author
Member

WARD-WORKFLOW: reservation-released

release details

Run finished with WARD-WORKFLOW: done ✅.

ward container reap released container engineer-codex-cli-guard-244 (--harness codex): the terminal outcome supersedes the reservation, so a later redispatch no longer needs --override-reservation.

— Codex, via ward agent

<!-- ward-agent-reservation-released --> WARD-WORKFLOW: reservation-released <details><summary>release details</summary> Run finished with `WARD-WORKFLOW: done ✅`. `ward container reap` released container `engineer-codex-cli-guard-244` (`--harness codex`): the terminal outcome supersedes the reservation, so a later redispatch no longer needs `--override-reservation`. </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/umbra#244
No description provided.