Repository navigation
docs: prioritize product improvements from implementation evidence - #96
Merged
Merged
Conversation
mazzasaverio
marked this pull request as ready for review
October 2, 2026 06:37
# Conflicts: # CHANGELOG.md # HANDOVER.md # tests/integration/test_release_verifier.py
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
2 participants
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.
The roadmap mixes historical release inventory with current priorities and names extras that are not declared by the package. Add a source-backed product review, link it from VISION/ROADMAP and documentation navigation, and align the current extra list with pyproject.toml.
The review connects five implemented PRs (#91 through #95) to their product value, then prioritizes remaining contract, resource, integration and measurement work with explicit acceptance conditions. It retains the local-first dependency-free vision and distinguishes source-grounded privacy proposals from dynamically validated findings. It makes no new model-quality, certification or release-publication claim.
Validation: pre-commit, strict mypy, strict docs build, package build, release verifier and git diff --check passed. Full CI, including the Linux/Windows test matrix, property tests and installed-wheel checks, passed: https://github.com/ma2za/pseudonymize/actions/runs/36974122837 . Documentation and performance workflows also passed. The additional isolated privacy harness could not start because namespace setup was denied, which is recorded as a validation limit. No production service was probed or changed.
Current review status
Review priority: 7 of 9; PR #100 is the packaging prerequisite. Updated against main
17e8fccwhile preserving development version 1.37.0 and the hosted-service changes. Includes the shared service-extra audit correction from #100. No PR has been merged.Current branch validation: 11 focused tests passed; Ruff formatting/lint, mypy, wheel/sdist builds and release verification passed. Strict documentation build passed. Fresh CI on the current head completed with 18 successful checks, one skipped check, and no failures.