[hyperpolymath]

What changed

Comment-only correction in .machine_readable/CLADE.a2ml. The [status] comment, written by clade-status-backfill (gv-clade-index ADR 0006), said "uuid is immortal". gv-clade-index ADR 0007, accepted 2026-11-10, says the uuid follows the forge path: a move or rename mints a new one, and a phase change never does. "A rename is NOT a phase change" now reads "A prefixed-name (clade code) change is NOT a phase change", the rename it means. One file, +6/−4, re-wrapped at 80 columns; no data value changes.

Type of change

• Bug fix (fix:)
• New feature (feat:)
• Documentation (docs:)
• CI / workflow / lockfile (ci:)
• Refactor, no behaviour change (refactor:)
• Chore (chore:)

Local verification

$ cargo fmt    --manifest-path rust/pdftool_core/Cargo.toml -- --check
(no output; exit 0)
$ cargo test   --manifest-path rust/pdftool_core/Cargo.toml --locked
test result: ok. 22 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
$ cargo clippy --manifest-path rust/pdftool_core/Cargo.toml --locked --all-targets -- -D warnings
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 7.10s

Checklist

• I ran the three commands above (or explained why I could not).
• If I changed a uses: line, actions.lock is updated in this same commit and I ran scripts/check-lock-sync.sh. (No uses: line changed.)
• If I removed or retired a CI check, there is a matching row in docs/ci/CHECK-DETERMINATIONS.adoc. (None removed.)
• I have not added continue-on-error, if: false, or weakened any gate.
• If I changed a component's state, TOPOLOGY.adoc is updated. (No state change.)
• If I changed something the wiki asserts, the matching wiki/ page is updated. (Not applicable.)
• Documentation that this PR makes stale has been updated in the same PR.

Notes for the reviewer

Part of an estate-wide comment correction after gv-clade-index ADR 0007. Signed commit.

---

Generated by Claude Code

[coderabbitai]

No actionable comments were generated in the recent review.

Summary

Summary by CodeRabbit

• Documentation
  • Clarified that moving or renaming a forge creates a new UUID, while changing its phase does not.
  • Explained that changing a prefixed name preserves the UUID and phase, and records the previous name as an alias.

The lifecycle comment now states how forge moves, renames, phase changes, and prefixed-name changes affect UUIDs, phases, and aliases.

Changes: Lifecycle wording

Layer / File(s)	Summary
Clarify lifecycle rules .machine_readable/CLADE.a2ml	The comment states that a forge move or rename mints a new UUID, while a phase change does not. It states that a prefixed-name change adds the old name to aliases[] without changing the UUID or phase.

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

Change: Other

Merge Risk: Minimal · up to ba15e

The change clarifies lifecycle wording, with no identified merge-blocking risk.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title clearly describes the main documentation change: UUID identity follows the forge path.
Description check		The description explains the UUID wording correction and the distinction between prefixed-name changes and phase changes.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

• Autofix · 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

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 3428ca5a-0ca9-4f15-9285-4fbe51b47fdc

Commits

Reviewing files that changed from the base of the PR and between 834f77b and ba15e6e.

Files selected for processing: 1

• .machine_readable/CLADE.a2ml

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: 7

• GitHub Check: CodeRabbit
• GitHub Check: Analyze (actions)
• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: Hypatia Neurosymbolic Analysis
• GitHub Check: actions.lock is in sync with the workflow YAML
• GitHub Check: Rust core (tests, formatting, lint)
• GitHub Check: semgrep-cloud-platform/scan

Additional comments: 1

.machine_readable/CLADE.a2ml: 1

29-34: LGTM!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud