Repository navigation
docs: correct stale v0.2.0 current-version statements to v0.4.0 - #364
Merged
Merged
Conversation
pyproject.toml, CITATION.cff, the v0.4.0 tag (2026-08-16) and PyPI all
say 0.4.0. Four docs still stated v0.2.0 as the current version:
ROADMAP.md (opening status line), docs/ARCHITECTURE.md (status note),
docs/funding-impact-brief.md ("habitable is at ..."), and
docs/recruitment/audit-funding.md (two "Currently/About the project"
lines). Historical references ("since v0.2.0", the v0.2 milestone row,
the v0.2.0 release link in evidence-pack.md) are left as written.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GqtiAsmkmDmpynCN35XTzg
Signed-off-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
Four docs still state v0.2.0 as the current version. The package is 0.4.0 (
pyproject.toml,CITATION.cff, tagv0.4.0dated 2026-08-16, PyPI latest 0.4.0). Five single-token edits, nothing else:ROADMAP.mddocs/ARCHITECTURE.mddocs/funding-impact-brief.mddocs/recruitment/audit-funding.mdDeliberately left alone (historical or not a current-version claim): "since v0.2.0" in
ROADMAP.md(provenance/SBOM), the v0.2 milestone row, the v0.2.0 release link indocs/evidence-pack.md,docs/releasing.md, the audit scorecard.docs/sustainability.mdhad no stale version string, so it is untouched. No strategy, claims, pricing or new content were added.Noticed but not changed:
docs/accessibility/ACR.md:45says version 0.3.0. That is an accessibility conformance report, so its version line should be updated when the ACR is re-verified, not in a drive-by edit.Threat-model baseline B1: NOT changed here (needs a human)
docs/threat-model.mdno longer matches the SHA-256 pinned indocs/audits/threat-model-baseline.md(pinned809e0a43...fcb71f, currente5eda2c5...3f8f). I did not touch the pin. The drift is substantive, not cosmetic: 80 insertions / 28 deletions across 11 commits since the freeze commit256a54d, including changed protection claims (case-bound pairing for sync; plaintext working copies moved outside the vault; encrypted timestamp-token sidecars; relay logging and/healthzretained-state counts; opt-inPaddingTransport), new residual risks (sidecar filename linkability, temp-file cleanup is not secure erasure), a new status banner, and the duress-safe state reclassified from implemented to planned. The baseline file says B1 is immutable once tagged and that substantive changes cut a new baseline (B2) with a fresh hash, maintainer re-review, tag and ADR reference;docs/threat-model.mdis CODEOWNERS-protected. No CI check or test verifies the hash today; the only check is the manualshasumsnippet in the baseline doc. A human maintainer needs to re-review the current threat model section by section and cut B2 (or decide otherwise). Nothing was fabricated.Checks
make lint(ruff format + check): passmake type(mypy --strict): passmake i18n,make doc-links,make markers: passmake cov(pytest): 1710 passed, 49 skipped, 1 failed:tests/test_offload.py::test_a_failed_container_write_leaves_the_sealed_original_alone. It fails identically on unmodifiedmainin this sandbox because the sandbox runs as root, which ignores the test'schmod 0o500read-only directory, so noOSErroris raised. Unrelated to this change.make a11ywas not run.Checklist
make verifystages that can run here are green apart from the pre-existing root-only failure aboveGenerated by Claude Code