Cargo.toml license field is invalid SPDX #1
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/galaxy-gen#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Originally filed by @coilysiren on 2026-05-21T08:19:26Z - https://github.com/coilysiren/galaxy-gen/issues/73
Bug -
Cargo.tomldeclareslicense = "AGPL", which is not a valid SPDX license identifier. Tooling that parses thelicensefield (crates.io, cargo-deny, license scanners) will reject or misclassify it.Fix: set
license = "AGPL-3.0-or-later"(orAGPL-3.0-onlyif pinning strictly to v3). The repo already ships a top-levelLICENSEfile, so this is metadata-only.Surfaced while writing the
coding-licensesskill in agentic-os-kai - galaxy-gen is the canonical AGPL-3.0 / deployment-of-one example.WARD-RESERVATION: held 🔒
reservation details
Holder: container
engineer-codex-galaxy-gen-1on hostKAI-DESKTOP-TOWER.Reserved by
ward agent --harness codex(reserved 2026-07-10T22:15:01Z). Concurrentward agentruns are blocked until it finishes or the reservation goes stale (1h TTL).--forceoverrides.Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).
run seed context — what this run is carrying (ward#609)
coilyco-flight-deck/galaxy-gen#1· branchissue-1· harnesscodex· workflowdirect-mainengineer-codex-galaxy-gen-1· wardv0.605.0· dispatched2026-07-10T22:15:01ZStatic container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.605.0).
— Codex, via
ward agentWARD-OUTCOME: done
details
workflow: direct-main; review summary: skipped (temporary ward default pending brokered QA) The implementation was a one-line SPDX metadata fix. Confidence is high. No surprises beyond the existing pre-commit and cargo warnings. Follow-up: none.