Repository navigation
fix: readable daily-use results and accurate purge recovery state - #60
Merged
Merged
Conversation
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.
Summary
Builds on merged PR #59 without duplicating the daily-use lifecycle.
public-document <action> --format text: labeled state, expiry/scope, inventory, receipts and references, plus fixed safe next-step guidance. Default/explicit JSON remains compatible. Dynamic values are ASCII JSON escaped; rendering never dispatches twice.Verification and budget
ef53c85229306d5ee146b051740b43333959808fexactly matches the tested local tree (only documentation changed after behavioral tests).Selected cases in
test_public_document_daily.DailyUseTests:test_readable_status_and_preview_do_not_mutatetest_readable_retrieval_and_default_json_compatibilitytest_withdraw_late_failure_and_unavailable_readbacktest_purge_recovery_preserves_unknown_and_private_metricsLimitations
Text labels are English; Japanese usage documentation is included. Configured roles are not authentication. Metadata status does not assess content integrity. Observed deletion does not prove which client completed it, forensic erasure, or removal of external copies. No long-term usability, performance or cost benefit is claimed.
Owner requested implementation through merge; exact-head CI will be checked before merging.
Exact-head CI verified
Run 43756820633 succeeded for PR head
cc4d3536d4573c7e2c7ff28cc8bb8ba56d16b7c0. Checkout was synthetic mergea82afec3458e725c4f7270bf61acb9017262c9e8against baseb07626309b39ec1aaae56b0195abc8f5129851d0. Log confirms 4 unique cases / 1 invocation PASS (0.469s) on Python 3.13.18 with pinned direct requirements, plus 117-file AST and 795-link static checks. Total trial: 8 case executions / 2 invocations, no retries. Source review and mergeability checks passed; proceeding with owner-authorized merge. The documentation checkpoint remains explicitly prepublication rather than triggering another code push.