License inconsistency: package.json AGPL-3.0-or-later vs LICENSE MPL-2.0

[hyperpolymath]

Gap

Root LICENSE is Mozilla Public License 2.0 but package.json:5 declares "license": "AGPL-3.0-or-later". Same shape as verisimdb#82, fixed manually in verisimdb#101.

Specifics

• package.json:5: "license": "AGPL-3.0-or-later"
• Root LICENSE: Mozilla Public License Version 2.0

Owner action

Per estate license-policy umbrella: sole-owner repos default to MPL-2.0. Single-line fix. Filed as issue (not PR) per feedback_no_automated_licence_edits.

Related

• verisimdb#82, verisimdb#101 (precedent)
• Estate memory: feedback_estate_license_policy_umbrella

🤖 Generated with Claude Code

[hyperpolymath]

Status update post-hardening landed today (2026-06-02):

This auto-filed inconsistency is now flag-only — see umbrella hypatia#416 (now CLOSED). The 3-layer guard prevents any auto-PR:

• hypatia#414+#415 — SC-010 flipped to auto_fixable: false; license_finding_strategy/0 caps severity to :warn/:review; Manual-Only policy header at the top of lib/rules/cicd_rules.ex
• gitbot-fleet#247 — dispatch-runner.sh refuses any recipe_id or category matching license|spdx|pmpl|mpl-2|agpl|palimpsest; the 3 fix-scripts (fix-license-hygiene.sh/fix-license-file.sh/fix-missing-spdx.sh) exit 1 with refusal banners
• standards#339 — .claude/CLAUDE.md top-of-file 'License Policy — Manual Only' section + 5-way classification

Resolution requires manual owner classification per the 5-way directive (estate-license-policy-umbrella):

Category	License	Applies to
Sole owner repos (default)	MPL-2.0	most of hyperpolymath/*
007 only	All Rights Reserved	hyperpolymath/007
Shared with son	AGPL-3.0-or-later	idaptik, burble, etc.
Third-party / forks	DO NOT TOUCH	upstream forks
Palimpsest carve-out	PMPL-1.0-or-later	palimpsest-license, palimpsest-plasma, consent-aware-http

Until classified manually by owner, this issue stays open as a tracked-but-not-auto-actionable record.

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

[hyperpolymath]

FYI from the 2026-06-02 licence campaign: this issue says LICENSE is MPL-2.0 but the current LICENSE file is AGPL-3.0-or-later. The manifest declaration of AGPL-3.0-or-later is now CONSISTENT with LICENSE, not inconsistent. The issue is stale — either close as resolved, or re-triage if boj-server should actually be MPL-2.0 (sole-owner default) vs AGPL (son-shared category 3). cc owner for direction.