obsidian-plugin/lllin000_PaperForge
1
0
Fork 0
mirror of https://github.com/lllin000/PaperForge.git synced 2026-07-22 06:50:53 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
lllin000_PaperForge/project/current/ocr-v2-active-queue.md
LLLin000 b97e82ab7c docs: close #71/#72 prototypes, set #73 as active frontier 
Record the completed six-module control-center and maintenance-inbox
prototype wave. Both prototype pairs passed independent Critical/Important
PASS review and direct browser verification at 768px without production
code changes. Update executive summary, active queue, decision log,
session timeline, and milestone checkpoint.

- #71 resolved: six-module control-center HTML prototype
  (5 scenarios x 6 modules, plain-button switcher, responsive 768px)
- #72 resolved: actionable-only maintenance inbox prototype
  (single-action rows, inline issue-draft, confirmation-first report)
- #73 promoted to active frontier: integrate accepted model into
  production control-center plugin
2026-07-15 00:41:28 +08:00

5.6 KiB
Raw Blame History

OCR-v2 Active Queue

Status: OCR-v2 is stable; OCR maintenance streaming with canonical per-row actions is implemented; the capability vocabulary, managed-runtime architecture, control-center prototype (#71), and maintenance inbox prototype (#72) are all resolved. Last updated: 2026-07-15

Current checkpoint

  • Retrieval recovery is merged to master; the real Literature-hub vault has a healthy 2560-dimensional vec0 index and working M / @ search paths.

  • OCR rebuild: streaming progress + maintenance UI redesign is implemented and reviewed.

  • Multi-key ocr rebuild and full ocr redo emit separate, flushed progress streams and accept a cross-platform cooperative stop request between papers.

  • The maintenance tab now exposes all papers plus the canonical _needs_derived_rebuild() recommendation set, selected batch actions, an above-table progress state, and full refresh on completion.

  • Per-row maintenance actions now route through maintenanceActionForRow() — rebuild/redo follow the canonical backend display_action rather than raw booleans.

  • Destructive redo requires user confirmation via maintenanceActionRequiresConfirmation().

  • Cache refresh preserves the backend manifest (was overwriting it with empty on each refresh).

  • Source Corpus data remains authoritative and was not modified during verification. Only the deployed plugin bundle and disposable maintenance cache were refreshed.

  • Current-contract audit identified the migration boundary: preserve durable OCR/SQLite truth and recovery actions; replace global setup state, duplicate runtime/config resolution, and freshness-free snapshots.

  • Obsidian-native research preserves the six-module IA, progressive setup, capability-gated commands, and minimal transient status chrome.

  • Desktop runtime/recovery research establishes module-scoped repair, compatibility-gated updates, local redacted diagnostics, and user-reviewed issue drafts.

  • #69 resolved at issuecomment-4971161072: orthogonal availability/activity/attention axes, 6-state capability ordinal, 12 canonical verbs, backend-owned severity and primary actions, maintenance projection.

  • #70 resolved at issuecomment-4971239398: plugin-managed immutable runtime slots, system-Python bootstrap with validated-triplet fallback, single active-runtime.json pointer, ManagedRuntime class with current()/status()/ensure(), fail-closed command resolution.

  • #71 resolved: six-module control-center HTML prototype with 5 scenarios, plain-button switcher, primary attention zone, responsive layout (768px breakpoint), and capability-gated actions. Independent Critical/Important PASS review. Design decisions recorded in docs/prototypes/2026-07-14-six-module-control-center.{html,md}.

  • #72 resolved: actionable-only maintenance inbox prototype with single-action rows, inline issue-draft review, local redacted export, and confirmation-first report flow. Independent Critical/Important PASS review. Design decisions recorded in docs/prototypes/2026-07-14-maintenance-issue-reporting.{html,md}.

Verification status

  • Focused Python OCR paths: 99 passed, 1 Windows SIGINT test skipped, 1 unrelated empty-result regression deselected.
  • Plugin: 93 passed; TypeScript check and production build passed.
  • Maintenance regression tests: 19/19 passed (canonical action routing, confirmation gate, cache manifest preservation).
  • Live Obsidian verification: PaperForge 1.5.15 loaded without captured errors; maintenance rendered 734 All rows and 700 Recommended rows from the canonical backend flag.
  • Live progress-state harness showed the floating progress bar, current key, Stop control, and disabled row actions.
  • Prototype #71 (control center): Critical PASS (5/5), Important PASS (11/11) — independent reviewer dimensions confirmed.
  • Prototype #72 (maintenance inbox): Critical PASS (4/4), Important PASS (6/6) — independent reviewer dimensions confirmed.
  • Both prototypes browser-verified at 768px viewport with scenario-switching, action-button interactions, expand/collapse diagnostics, and issue-draft flow.
  • No production plugin code was modified during prototype work.
  • The repository-wide Python suite remains blocked during collection by the pre-existing test_pr9a_resume_rebuild.py import of removed _assert_collections_healthy.

Frontier

  • Prototype the six-module control center (#71) — design information hierarchy and interaction model for 安装 / 文献库 / OCR / 记忆 / 维护 / 帮助.
  • Design actionable-only maintenance inbox with user-reviewed GitHub Issue draft reporting (#72).
  • Integrate the accepted prototype model into a production control-center plugin (#73).
  • Keep routine OCR quality outside maintenance; successful updates leave the queue, while unacceptable results use a user-reviewed GitHub Issue draft.

Deferred

  • Vector rebuild UX (PRD Slice 1): deferred.
  • Memory/global maintenance cleanup (PRD Slice 3): deferred.
  • OCR ETA and real-time per-row mutation: out of scope for the completed OCR slice.