Skip to content

feat: add offline public-document daily-use commands - #59

Merged
moruku36 merged 1 commit into
mainfrom
feat/public-document-daily-use-20261115
Nov 14, 2026
Merged

moruku36 merged 1 commit into
mainfrom
feat/public-document-daily-use-20261115

Conversation

@moruku36

@moruku36 moruku36 commented Nov 14, 2026 •

Copy link
Copy Markdown
Owner

Summary / 概要

Adds an explicit offline agent-sleep-lab public-document <action> namespace for one persistent public-document store, plus English/Japanese daily-use guidance. No model/provider call, network dispatch, scheduler or automatic adoption is added.

  • Only init creates a store; other actions require an existing store.
  • status and cleanup-preview use metadata-only, read-only SQLite access within one coherent transaction. Stored state, effective access and cleanup state remain distinct; integrity is not assessed by preview.
  • Approval registration, mechanical verification/evaluation, proposal, guarded adoption and different-task/same-scope retrieval remain separate. Configured identity strings are not authentication or proof of independent humans.
  • Explicit expiry/integrity cleanup and withdrawal retain no-retry operation metadata and external exports.
  • Optional content-free metrics reserve a new private file before the action, refuse existing destinations and never justify replay after a late write error. Cost remains unavailable, not zero.

永続storeの日常操作を明示的なoffline CLIへまとめ、日英手順を追加します。status/previewは本文を読まず、読取りtransaction内でmetadataを確認します。許可・機械的検証・採用・別task利用の境界を維持し、model呼出し・自動採用・定期実行は追加しません。

Verification and bounded allocation / 検証状況

Independent static re-review accepted the bounded trial with the limitations below; this is not behavioral verification, human approval or merge authorization.

  • The sole local invocation exited 2 during module loading on Python 3.15: ModuleNotFoundError: No module named 'jsonschema'. Zero test bodies ran; no passing result is claimed. Four local slots / one invocation remain charged. No local retry or install was performed.
  • The existing remaining PR CI allocation is exactly four selectors / one invocation on Python 3.13, after installing the repository's pinned direct requirements. Transitive dependencies are not locked. The same trial maximum is eight charged slots / two invocations including the failed local load, not an extra allocation.
  • CI verified SUCCESS: run 43653126748, associated with exact PR head d225b051a191aca1905046c23bb8d7b15be3cd82. The checkout was synthetic PR merge b1491320561de4197e32b68a6ebcad4ce939d3e5 against base 73af93896632d460689fa9b6e6846d607dd40c2b, not a landed main merge. The log confirms 4 unique cases / 1 invocation, all PASS (0.315s). AST parsing 117 Python files and documentation checks 793 relative file links / 107 Markdown files also passed (anchors not checked). No full suite, version matrix, build, live-model acceptance or retry was run. The bilingual status pages preserve the explicitly dated prepublication checkpoint; this paragraph records the later CI result without a new code push or another CI invocation.
  • Parent prepublication checks passed: git diff --check; documentation checker 793 relative file links / 107 Markdown files (anchors not checked). These are static checks, not regression or live acceptance.

Selected cases (prefix test_public_document_daily.DailyUseTests.):

  1. test_open_and_preview_are_nonmutating
  2. test_independent_offline_lifecycle_and_scoped_retrieval
  3. test_exact_expiry_preview_and_explicit_sweep
  4. test_purge_recovery_preserves_unknown_and_private_metrics

localは依存不足で読込み失敗し、本体実行0件・合格0件でした。その後、既存の残りCI枠4件/1起動で**4件すべてPASS(0.315秒)**を確認しました。対象は上記exact PR headに対応する合成mergeで、mainへは未マージです。日英status文書は日付付き公開前checkpointとして残し、後のCI結果は本PRへ追記しています。過去のUNKNOWN操作やmodel呼出しは再実行していません。

Known limitations / 既知の制約

  • P3: conservative purge recovery output. A withdrawal purge exception can report purge_pending even if deletion already committed or another client finished it. This is not authoritative persisted-state readback. Obtain fresh status after a nonzero exit before deciding any further action; do not blindly repeat withdrawal or a paid operation. The bilingual implementation-status pages disclose this limitation.
  • P3: snapshot-probe precision. The synthetic locking probe accepts a SQLite OperationalError without establishing the exact failing stage. Source review establishes the explicit read transaction; no concurrency stress-test claim is made.
  • Mechanical receipts establish quotation/snapshot checks, not factual truth, usefulness, performance, savings or real-agent acceptance. Metrics parent-directory stability is a documented trust assumption. Production authentication and remote-copy deletion are outside this change.

purge例外時のpurge_pendingは保守的な診断で、保存状態の再確認ではありません。新しいstatusを確認してから次の操作を判断してください。構成上のidentityや機械的な受領を、認証・意味判断・実運用受入の証拠にはしません。

Review scope

Nine files only: one existing workflow, four bilingual documentation pages, CLI dispatch, the read-only runtime seam, one new daily-use module and its four-case test module. Please review the lifecycle/role boundaries and nonmutating status/preview contract. This PR is left unmerged.

@moruku36
moruku36 merged commit b076263 into main Nov 14, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant