Skip to content

sync+compliance(§4.3): invert LICENSE symlink direction — v1.38 - #18

Merged
UnbreakableMJ merged 1 commit into
mainfrom
compliance/license-inverted-v1.38
Jul 25, 2026
Merged

sync+compliance(§4.3): invert LICENSE symlink direction — v1.38#18
UnbreakableMJ merged 1 commit into
mainfrom
compliance/license-inverted-v1.38

Conversation

@UnbreakableMJ

Copy link
Copy Markdown
Contributor

Back-sync of Spacecraft-Software/Standard#17, plus the self-apply. Same version (1.38), same date (2026-07-26).

Why

GitHub's license detector reads git blobs; a symlink's blob is the target path, not the license text. The v1.36 layout left this repo reporting NOASSERTION — no identified license — where sibling repos with a regular LICENSE report GPL-3.0.

Change

  • Layout inverted. LICENSE is now a regular file with the canonical FSF GPL-3.0 text (byte-identical to what anvil/bravais/pearlite ship, which GitHub detects), replacing the reflowed REUSE-shipped variant. LICENSES/GPL-3.0-or-later.txt symlinks to it. Apache-2.0, GFDL-1.3-or-later, and MIT stay regular files — they are secondary licenses (§4.2), not this repo's primary.
  • SKILL.md — §4.3 body rewritten, §5.2 LICENSE row and §16 checklist bullet updated, masthead and frontmatter bumped to v1.38.
  • references/CHANGELOG.md — v1.38 entry.
  • Both bundles rebuilt in the same commit.

Verification

  • reuse lint → compliant, 604/604 files (it follows the symlink through the filesystem)
  • Frontmatter description935 characters (under the 1000-char working limit)
  • unzip -l → bundles carry the current SKILL.md + references/CHANGELOG.md

🤖 Generated with Claude Code

Back-sync of Spacecraft-Software/Standard#17, plus the self-apply.

GitHub's license detector reads git blobs, and a symlink's blob is the
target path rather than the license text — so the v1.36 layout left this
repo reporting NOASSERTION. §4.3 is inverted: the root LICENSE is a
regular file holding the verbatim primary license text, and
LICENSES/<SPDX-id>.txt for that license symlinks back to it. reuse
follows the link through the filesystem and lints clean; GitHub gets a
real blob. The text still exists exactly once.

Self-apply: LICENSE now carries the canonical FSF GPL-3.0 text (the same
text sibling repos ship, which GitHub detects as GPL-3.0), replacing the
reflowed REUSE-shipped variant; LICENSES/GPL-3.0-or-later.txt symlinks
to it. Apache-2.0, GFDL-1.3-or-later, and MIT stay regular files — they
are secondary licenses (§4.2), not the repo's primary.

SKILL.md §4.3 body, §5.2 LICENSE row, §16 checklist bullet, masthead,
and frontmatter description synced; references/CHANGELOG.md entry added;
both bundles rebuilt in the same commit.

Frontmatter description: 935 chars (under the 1000-char limit).
reuse lint: compliant, 604/604 files.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@UnbreakableMJ
UnbreakableMJ merged commit 48f14b1 into main Jul 25, 2026
1 check passed
@UnbreakableMJ
UnbreakableMJ deleted the compliance/license-inverted-v1.38 branch July 25, 2026 23:53

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ccb09ef9ad

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

# The Steelbore Standard — Compliance Reference

**Version:** 1.37 | **Date:** 2026-07-26 | **Author:** Mohamed Hammad
**Version:** 1.38 | **Date:** 2026-07-26 | **Author:** Mohamed Hammad

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Sign the commit and add the assistant attribution trailer

The reviewed commit object has no gpgsig header (git verify-commit e599e12bc91050f01d9866aa4f37350956832847 exits with status 1), and its assistant-generated message lacks the required Co-Authored-By: Claude … trailer. Recreate the proposed commit with configured signing and the attribution trailer before merging so its provenance satisfies the repository requirements.

AGENTS.md reference: AGENTS.md:L25-L26

Useful? React with 👍 / 👎.

```sh
ln -s LICENSES/GPL-3.0-or-later.txt LICENSE
git add LICENSE
cp <canonical license text> LICENSE

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Replace the non-runnable license copy placeholder

When an agent follows this fenced sh recipe literally, the shell parses <canonical and text> as input/output redirections and executes cp license text, rather than copying a canonical license into LICENSE; if a file named canonical exists, it can also truncate the existing LICENSE. Use a concrete one-argument source-path placeholder or an explicit download command so the authoritative migration procedure is safe to execute.

Useful? React with 👍 / 👎.

Comment on lines +282 to +284
`LICENSE` is a **regular file** carrying the verbatim text of the project's primary
license, and `LICENSES/<SPDX-id>.txt` for that same license is a **symbolic link**
to it. Every project MUST ship both.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Correct the Grok README after reversing the symlink

This new layout makes the existing license text in grok-skills/README.md:93-94 false: it still says the root LICENSE is a symlink to LICENSES/GPL-3.0-or-later.txt, while this commit makes the root file regular and the LICENSES/ entry the symlink. Update that consumer-facing documentation in the same change so the repository does not publish mutually contradictory §4.3 instructions.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant