Skip to content

docs: reconcile CLAUDE.md + FAQ.md with AGPL migration (#112 follow-up)#149

Closed
hyperpolymath wants to merge 2 commits into
mainfrom
fix/license-drift-claude-md-faq
Closed

docs: reconcile CLAUDE.md + FAQ.md with AGPL migration (#112 follow-up)#149
hyperpolymath wants to merge 2 commits into
mainfrom
fix/license-drift-claude-md-faq

Conversation

@hyperpolymath
Copy link
Copy Markdown
Owner

Summary

PR #112 (2026-05-27) migrated this repo from MPL-2.0 to AGPL-3.0-or-laterLICENSE and the package manifests (Cargo.toml, deno.json, etc.) were updated, but several human-facing docs still cached the pre-migration state. This PR reconciles them.

Changes

  • CLAUDE.md line 12License: MPL-2.0License: AGPL-3.0-or-later
  • CLAUDE.md line 218 (Critical Constraints) — was License: MPL-2.0 (not AGPL, ...) (actively wrong!) → License: AGPL-3.0-or-later (migrated from MPL-2.0 in #112, 2026-05-27)
  • CLAUDE.md line 223Last Updated: 2026-03-232026-05-30
  • docs/wiki/FAQ.md §licence — Q was Why MPL-2.0 and not MIT or AGPL? with the wrong A cached → rewritten to reflect current AGPL state and the chore(license): migrate to AGPL-3.0-or-later #112 migration history.

Out of scope (tracker follow-up)

~331 source files in src/ still carry // SPDX-License-Identifier: MPL-2.0 headers from before #112 (which only swept LICENSE + package manifests, not source-file headers). Tracker issue to follow — that's an owner-decision sized sweep.

Test plan

  • git log confirms chore(license): migrate to AGPL-3.0-or-later #112 is the canonical AGPL migration commit
  • LICENSE file head matches SPDX-License-Identifier: AGPL-3.0-or-later
  • No MPL-2.0 strings left in CLAUDE.md or docs/wiki/FAQ.md (verified post-edit)

hyperpolymath and others added 2 commits May 30, 2026 20:34
Wave-2 follow-on to PR #146. Documents the procedure for replacing the
apt-shipped Chapel runtime (which ships only the `lib_pic-none`
variant) with a `lib_pic-pic` build so the metalayer can be linked as
a shared library instead of a static archive.

- `docs/decisions/2026-05-30-chapel-pic-rebuild.md` — ADR addendum to
  the rehabilitation ADR. Documents the source-build procedure, the
  ~30 min / ~5 GB cost, the tradeoffs vs `--library --static`, and
  why the CI flip is deferred (registry-pushed container image is the
  L2.5 prerequisite).
- `Justfile :: chapel-pic-from-source` — runnable recipe that
  downloads chapel-2.8.0, sets `CHPL_LIB_PIC=pic`, builds, and
  verifies the `lib_pic-pic/` runtime variant landed. Cache dir
  configurable via `ECHIDNA_CHAPEL_PIC_CACHE`; version via
  `CHPL_VERSION`. **Not** invoked from CI.
- Cross-link from the rehabilitation ADR's Wave-2 plan to the new ADR.

Verification path is local-only by design — the recipe will be exercised
on-demand when L2.5 multi-locale work needs the shared-library form.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
… AGPL-3.0-or-later

CLAUDE.md still claimed `License: MPL-2.0` (twice, including in
Critical Constraints with "not AGPL") and `Last Updated: 2026-03-23`,
all of which predate the 2026-05-27 license migration in #112.
docs/wiki/FAQ.md still framed the licence Q as "Why MPL-2.0 and not
AGPL?" with the wrong answer cached.

LICENSE file + package metadata (Cargo.toml, deno.json, etc.)
correctly carry AGPL-3.0-or-later since #112; this PR just
reconciles the human-facing docs.

Source-file SPDX headers (~331 files in src/) still tagged MPL-2.0
remain — tracked separately as a larger sweep.
@hyperpolymath
Copy link
Copy Markdown
Owner Author

Closing — docs reverted locally; MPL-2.0 in CLAUDE.md/FAQ.md is intentional. The LICENSE-file vs docs state will be reconciled separately.

@hyperpolymath hyperpolymath deleted the fix/license-drift-claude-md-faq branch May 30, 2026 19:35
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