fix(pkg)!: re-mint UUID as v8, bump to 0.2.1

[hyperpolymath]

Summary

Re-mints the package UUID as a v8 so the package can be re-registered in julia-professional-registry (JPR) at 0.2.1.

• uuid: c4a8b6d2-f9e3-4c1a-b8d7-9f2e3c4d5e6f (patterned placeholder) → 01a11d29-d897-8383-92d8-041d500f9c95 (ADR-008 profile T, minted with standards/scripts/uuid-v8.js t). Owner ruling 2026-10-08, which extends D320.
• version: 0.2.0 → 0.2.1 (owner ruling: patch bump under the new UUID).
• Manifest.toml: the committed [[deps.Causals]] path = "." self-entry gets the same uuid and version, keeping the manifest consistent with the project. (A library committing a Manifest is a separate, pre-existing matter, not changed here.)

⚠ Registration drift: the JPR entry will register this PR's merged tree. That tree carries every change on main since the 0.2.0 registration (registered tree 7e3213b54e, main tree fc149f4c56), not only these lines.

Type of change

• 🐛 Bug fix: n/a
• ✨ New feature: n/a
• 💥 Breaking change: the package identity changes, so existing installs must Pkg.rm("Causals") then Pkg.add again. InvestigativeJournalism.jl and Hyperpolymath.jl depend on this package and move to the new UUID in their own PRs.
• 🕳️ Soundness fix: n/a
• 📖 Documentation: n/a
• 🧹 Refactor: n/a
• ⚡ Performance: n/a
• 🔧 Build/CI: n/a

📌 New pins

• Head SHA: 278d8951cf48ecc340f0788eb985fd257712e846 (tree 0267c0294d687907c186b7a0442235f3170b9c1f)
• No action, lockfile or container pins are added or changed.

How has this been verified?

• Pkg.Types.read_project("Project.toml") returns name Causals, uuid 01a11d29-d897-8383-92d8-041d500f9c95, version 0.2.1.
• Import-vs-deps pre-check: every using in src is declared. The two AcceleratorGate hits are in src/backends/abstract.jl, which is no longer included (src/Causals.jl:26), and in a comment.
• julia --project=. -e 'using Pkg; Pkg.test()' (Julia 1.12.6): 870/870 passed (Causals.jl 170, E2E 20, Property-Based 680), Causals tests passed.
• cmp of Manifest.toml before and after Pkg.test(): byte-identical, so Pkg accepts the edited self-entry.

Checklist

• Commits are signed (G) and signed off
• Checks run locally (as above)
• SPDX headers on new files: no new files
• Docs updated: no doc names the UUID or version
• No soundness hole introduced

Notes for reviewers

Merge this PR before the JPR PR that re-registers the package. The JPR PR needs BDFL review plus an ADR, per docs/REGISTRY-POLICY.adoc. After the squash merge, tag the merge commit v0.2.1 (signed).

🤖 Generated with Claude Code

https://claude.ai/code/session_01WPSJ7fBhVAMcpSffCBWUDo

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 741dfe64-c178-48b9-be01-eb9ab19aeb5b

📥 Commits

Reviewing files that changed from the base of the PR and between bc752bf and 278d895.

📒 Files selected for processing (2)

• Manifest.toml
• Project.toml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details

⏰ Context from checks skipped due to timeout. (16)

• GitHub Check: governance / Licence consistency
• GitHub Check: governance / Trusted-base reduction policy
• GitHub Check: governance / Language / package anti-pattern policy
• GitHub Check: hypatia / Hypatia Neurosymbolic Analysis
• GitHub Check: Empty-linter (invisible characters)
• GitHub Check: test (nightly, windows-latest)
• GitHub Check: test (nightly, ubuntu-latest)
• GitHub Check: test (1.10, windows-latest)
• GitHub Check: test (nightly, macos-latest)
• GitHub Check: test (1.11, ubuntu-latest)
• GitHub Check: test (1.10, ubuntu-latest)
• GitHub Check: test (1.11, macos-latest)
• GitHub Check: test (1.10, macos-latest)
• GitHub Check: test (1.11, windows-latest)
• GitHub Check: analyze (actions, none)
• GitHub Check: semgrep-cloud-platform/scan

🔇 Additional comments (2)

Project.toml (1)

3-3: LGTM!

Also applies to: 5-5

Manifest.toml (1)

32-33: LGTM!

---

📝 Summary

Summary by CodeRabbit

• Chores
  • Updated the package release version to 0.2.1 in its project and dependency records. The package’s public interface remains unchanged; no new user-facing features or behaviour changes are included in this update.

Walkthrough

The package UUID changes to 01a11d29-d897-8383-92d8-041d500f9c95. The version changes from 0.2.0 to 0.2.1 in Project.toml and the Causals entry in Manifest.toml.

Changes

Package metadata

Layer / File(s)	Summary
Package identity and version Project.toml, Manifest.toml	The package UUID and version change in the project declaration. The manifest entry uses the same updated UUID and version.

Priority: ➖ Normal

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 278d8

The package metadata is consistent, and no stale in-repository UUID references were found. Existing dependents must adopt the new UUID as planned; no actionable merge-blocking risk remains in this change.

Architecture Summary

Architecture risk: 🔵 Low · up to 278d8

The change affects 2 systems.

Changed systems: Manifest.toml, Project.toml

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — Manifest.toml (service) was modified; 1 changed file maps to changed impact.
• observed — Project.toml (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in Manifest.toml: The Causals manifest entry changes UUID and updates the version from 0.2.0 to 0.2.1.
• observed — Modified behavior in Project.toml: The package UUID changes from c4a8b6d2-f9e3-4c1a-b8d7-9f2e3c4d5e6f to 01a11d29-d897-8383-92d8-041d500f9c95, and the version changes from 0.2.0 to 0.2.1; the authors declaration is unchanged.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarises the main changes: re-minting the package UUID and bumping the version to 0.2.1.
Description check	✅ Passed	The description directly explains the UUID change, version bump, manifest update, breaking impact, verification steps, and registration purpose.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{I’m a rabbit with a version to cheer,
The new UUID is written clear.
Two files now match in every line,
From 0.2.0 to 0.2.1.
I hop through fields, then rest my ear.}

_{Comment @coderabbitai help to get the list of available commands.}