Skip to content

Rootloom Personal Core 3.0.0

Choose a tag to compare

View all tags
@qingye-lab qingye-lab released this 15 Jul 05:07
v3.0.0
61c1d82
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Rootloom Personal Core 3.0.0 separates privacy quarantine from security-domain review and completes aggregate capture resource bounds.

Highlights:

  • Secret material and security-domain source now use separate classifiers. Files such as src/auth/token.py remain patch-readable and raise risk, while .env*, private keys, credential material, and explicit sensitive roots remain metadata-only.
  • CamelCase secret material such as clientSecret.json, apiToken.json, and serviceAccountKey.json is classified consistently after targeted Git discovery.
  • Stable repository capture now has one finite 90-second default monotonic deadline across both consistency passes, in addition to the independent per-Git-command ceiling.
  • Summary revision 5 adds stable evidence_complete, capture-limit/duration evidence, and identity-neutral intake-sealed / workflow-sealed provenance.
  • Baseline v3 is now produced; valid baseline v2 evidence remains readable and sealable.
  • Public JSON/CLI SemVer rules are now explicit. This is a Major release because provenance enum values and the newly produced persisted baseline format intentionally change public contracts.

Verification:

  • Local make check passed 164 tests with one environment-only non-UTF-8 filename skip on the current macOS volume.
  • make compatibility-smoke, make validate, and git diff --check passed.
  • A clean governed replay returned REVIEW_EVIDENCE_COMPLETE, evidence_complete: true, complete claim binding, and a valid hash chain for the exact release patch.
  • Release PR CI and merged-main CI both passed Linux Python 3.11–3.14, macOS, Windows, and Codex CLI compatibility contracts.

See CHANGELOG.md and docs/decisions/2026-07-15-sensitive-material-and-capture-bounds.md for the complete contract and migration details.

Assets 2
Loading