Cargo.toml license field is invalid SPDX #1

Closed
opened 2026-05-23 20:54:20 +00:00 by coilysiren · 2 comments
Owner

Originally filed by @coilysiren on 2026-05-21T08:19:26Z - https://github.com/coilysiren/galaxy-gen/issues/73

Bug - Cargo.toml declares license = "AGPL", which is not a valid SPDX license identifier. Tooling that parses the license field (crates.io, cargo-deny, license scanners) will reject or misclassify it.

Fix: set license = "AGPL-3.0-or-later" (or AGPL-3.0-only if pinning strictly to v3). The repo already ships a top-level LICENSE file, so this is metadata-only.

Surfaced while writing the coding-licenses skill in agentic-os-kai - galaxy-gen is the canonical AGPL-3.0 / deployment-of-one example.

_Originally filed by @coilysiren on 2026-05-21T08:19:26Z - [https://github.com/coilysiren/galaxy-gen/issues/73](https://github.com/coilysiren/galaxy-gen/issues/73)_ **Bug** - `Cargo.toml` declares `license = "AGPL"`, which is not a valid SPDX license identifier. Tooling that parses the `license` field (crates.io, cargo-deny, license scanners) will reject or misclassify it. Fix: set `license = "AGPL-3.0-or-later"` (or `AGPL-3.0-only` if pinning strictly to v3). The repo already ships a top-level `LICENSE` file, so this is metadata-only. Surfaced while writing the `coding-licenses` skill in agentic-os-kai - galaxy-gen is the canonical AGPL-3.0 / deployment-of-one example.
coilysiren added
P3
and removed
P2
labels 2026-06-17 08:40:35 +00:00
Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-galaxy-gen-1 on host KAI-DESKTOP-TOWER.

Reserved by ward agent --harness codex (reserved 2026-07-10T22:15:01Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL). --force overrides.

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)
  • Resolved: coilyco-flight-deck/galaxy-gen#1 · branch issue-1 · harness codex · workflow direct-main
  • Run: engineer-codex-galaxy-gen-1 · ward v0.605.0 · dispatched 2026-07-10T22:15:01Z
  • Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.605.0).

— Codex, via ward agent

<!-- ward-agent-reservation --> WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-galaxy-gen-1` on host `KAI-DESKTOP-TOWER`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T22:15:01Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL). `--force` overrides. **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). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/galaxy-gen#1` · branch `issue-1` · harness `codex` · workflow `direct-main` - **Run:** `engineer-codex-galaxy-gen-1` · ward `v0.605.0` · dispatched `2026-07-10T22:15:01Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.605.0). </details> </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
Member

WARD-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.
WARD-OUTCOME: done <details><summary>details</summary> 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. </details>
Sign in to join this conversation.
No description provided.