LitAnchor Notes v1.0.0-rc1

LitAnchor Notes v1.0.0-rc1

v1.0.0-rc1 is the first public release candidate of the evidence-grounded paper-reading product. The public product name is LitAnchor Notes · 文锚笔记; the compatible repository URL, installer receipt and Skill slug remain litanchor-paper-reading.

What this candidate supports

• one user-supplied local PDF to a new standalone Chinese Markdown note;
• one exact Zotero paper to a contained, non-overwriting Obsidian note;
• skim, deep and internalize reading modes under Paper Template v1.0;
• PyMuPDF-authoritative pages, quotations and original-PDF figure crops;
• consent-aware MinerU structure enhancement without making MinerU evidence;
• separate fidelity and important-content recall review;
• install, doctor, setup, repair, upgrade, rollback and uninstall through a local-capable Windows Agent.

The natural-language examples are illustrative. Equivalent wording should route by user intent rather than literal phrase matching.

Reliability evidence

• 180 local repository tests passed on the candidate worktree;
• Skill validation, Python compilation, 51 local Markdown links, privacy, anti-leak and compaction audits passed;
• three frozen checklist papers completed under the frozen content contract;
• a separate unseen paper completed after a generic split-caption/figure-plate crop fix, with no paper-specific rule in the distributable Skill;
• three isolated Windows application profiles passed install, setup, direct-PDF run-plan, upgrade, rollback and uninstall;
• two builds of the 57-file package were byte-identical;
• the final unseen note and both split-page figure crops were accepted by the user before version freeze.

These same-account profiles validate lifecycle isolation, not independent-user usability. Public RC feedback is therefore part of the route to stable v1.0.

Current boundaries

• Windows 10/11 x64 and a local-capable Agent;
• Python 3.10 or newer; untested newer versions are capability-probed;
• one paper per run;
• Markdown is the sole formal note output; no separate PDF note is generated;
• Zotero 7+ and Obsidian are optional for the integrated route, not required for direct PDF-to-Markdown;
• no Zotero write-back, bidirectional sync, batch review or silent overwrite;
• scanned and pathological PDFs may warn or block;
• user review of key visuals, core numbers and source locators remains recommended before long-term use.

Upgrade and rollback

Ask a local-capable Agent to upgrade from the tagged GitHub Release. The installer preserves local configuration and archives the previous version for rollback. Uninstall requires confirmation and preserves user configuration by default. Existing Vault notes are never lifecycle targets.

Privacy

Do not attach paper PDFs, private notes, Zotero data, runtime ledgers or raw configuration to public issues. The optional doctor support bundle is built from a redacted allowlist and should still be reviewed before sharing.

LitAnchor v0.6.0-beta.3 — Note Experience & Paper Template v1.0 Freeze

LitAnchor v0.6.0-beta.3

v0.6.0-beta.3 freezes the reader-facing note experience as Paper Template
v1.0. It is the final content-contract beta before the stable-release
candidate; it does not broaden LitAnchor into batch review, Zotero write-back,
or unattended publication.

What changed

• Split the public Paper Template.md content contract from the private,
  slot-driven Paper Template - Runtime.md renderer.
• Defined mode-specific output: skim renders Section 1, deep Sections 1–6,
  and internalize Sections 1–8. Excluded sections are omitted.
• Froze the 16-field note-frontmatter contract. Reading mode appears only as
  one mode tag alongside LitAnchor; user-added tags remain preservable.
• Replaced reader-facing Evidence IDs and repeated excerpts with compact linked
  p.x locators. Exact evidence and Claim mappings remain in private sidecars.
• Added argument-aware analytical lenses, structured experiment evidence
  chains, explicit conclusion boundaries, and visible provenance labels for
  Agent analysis, hypotheses, and user content.
• Added source-grounded research-idea gates for internalize, including a
  falsifiable hypothesis, delta, validation design, failure modes, and novelty
  status.
• Embedded selected key visuals directly with their source subsection,
  selection reason, and a two-to-four-sentence interpretation.
• Kept skim-mode visual inventories private without requiring or exporting
  image assets that the Section 1-only reader note does not embed.
• Removed the duplicate note H1 and added readable, stable filename handling
  for long or filesystem-unsafe titles.
• Removed internal HTML comments from generated note source and removed the
  reader-facing Section 6.5; validation state remains available in sidecars and
  frontmatter.
• Distinguished supporting reproducibility records from core comparison
  experiments, preventing internal completion guidance from appearing in a
  reader note.
• Separated vertically adjacent figures using the preceding caption as a hard
  crop boundary, including vector-heavy figures that require a bounded-region
  fallback.
• Applied standard Markdown left alignment to text-heavy tables without adding
  a CSS dependency.

Reliability boundaries

• PyMuPDF remains authoritative for physical pages, quotations, coordinates,
  and original-PDF crops.
• MinerU remains an optional, consent-aware structure enhancer and never becomes
  the formal Evidence source.
• Formal deep and internalize export requires full-paper coverage with
  page-grounded locators.
• Zotero remains read-only. Obsidian export remains contained, hash-verified,
  collision-checked, and non-overwriting.
• Paper facts still use the supplied paper only. External novelty search is a
  separate, explicitly authorized activity.

Upgrade notes

• Existing notes are not rewritten automatically.
• New notes use template_version: "1.0" and the fixed frontmatter properties.
• Runtime Evidence/Claim/review sidecars remain private and are not copied into
  the reader note.
• Upgrade through the normal LitAnchor lifecycle so rollback remains available.

Verification before publication

The release candidate must pass the complete repository suite, Skill/package
validation, Markdown-link and anti-leak/privacy audits, exact-version package
build, GitHub Actions matrix, and representative Obsidian note review. Release
results belong in docs/release-checklist.md; this file describes the intended
release contract rather than claiming unpublished results.

LitAnchor v0.6.0-beta.2 — Zero-Config Public Beta

LitAnchor v0.6.0-beta.2

Zero-Config Public Beta — 2026-08-01.

What changed

• Added separate privacy-aware issue forms for installation, runtime/PDF and
  note-quality failures.
• Added doctor --support-bundle, which builds a redacted diagnostic ZIP from
  an explicit allowlist instead of copying local reports or configuration.
• Added semantic intent regression for equivalent installation, lifecycle and
  one-paper reading requests without turning examples into literal commands.
• Added interrupted-update repair, configuration preservation, Vault
  non-interference and isolated Windows lifecycle coverage.
• Added a release-time Skill compaction audit for entry length, duplicate
  long-form rules and missing referenced resources.
• Unified local PDF preparation on PyMuPDF and removed the redundant pypdf
  dependency. PyMuPDF remains the physical-page, text, coordinate, rendering,
  crop and formal-evidence authority.
• Added shared coordinate-aware ordering for multi-column PyMuPDF text blocks,
  including a regression that verifies both manual and autonomous paths.
• Kept optional MinerU and development dependencies outside the core install.
  All dependency files now specify minimum versions without artificial upper
  bounds; newer versions are checked by CI and capability probes.
• Replaced the wide one-line Mermaid pipeline with staged, centered diagrams
  that keep the complete Section Synthesis label visible.

Compatibility

• Windows 10 or newer, x64.
• CPython 3.10 or newer; the release CI matrix covers 3.10 through 3.14.
• Zotero 7 or newer through the loopback Local API.
• Obsidian Desktop with a local filesystem Vault.
• MinerU remains optional, consent-controlled and non-authoritative.

Newer Python, Zotero and dependency versions are not rejected solely because
they are newer. doctor, runtime probes and CI determine whether the required
capabilities are available; untested versions receive a warning rather than a
false compatibility claim.

Upgrade

Agents should use the repository lifecycle interface:

.\install.ps1 -Action Upgrade
.\litanchor.ps1 doctor

The installer archives the previous receipt-owned version for rollback and
does not modify Zotero data or user notes. Existing Obsidian notes are never
silently overwritten.

Known boundaries

• One paper per run; no batch review or Zotero write-back.
• Native-text PDFs are the stable path. Scans and pathological layouts may
  warn, fall back or block.
• MinerU requires a local consent choice and network availability. Failure
  falls back to the PyMuPDF baseline without weakening evidence provenance.
• This is a Public Beta rather than the final v1.0 stable release; supported
  environments and failure boundaries remain explicit.

LitAnchor v0.6.0-beta.1 — Zero-Config Public Beta

LitAnchor v0.6.0-beta.1

LitAnchor v0.6.0-beta.1 is the first Agent-installed, Windows-first public
beta. It keeps the v0.5 autonomous deep-reading pipeline and adds a lightweight
installation, setup, diagnosis and release layer.

Highlights

• Intent-based Agent entry: users may express installation and single-paper
  deep-reading requests naturally; example sentences are not literal commands.
• Python >=3.10 and Zotero >=7 are minimums, not maximums. Tested versions
  are preferred, while newer versions run capability probes and emit warnings
  instead of being rejected by version number alone.
• Receipt-tracked install, repair, upgrade, rollback and uninstall operations
  touch only LitAnchor-owned paths.
• First-run setup resolves an Obsidian Vault by name, constrains the Inbox and
  stores one of three local MinerU consent modes.
• Machine-readable doctor checks Python, dependencies, Zotero Local API,
  Vault containment, path handling, MinerU readiness and collision risk.
• GitHub Actions validates Python 3.10 through 3.14 on Windows and builds a
  versioned ZIP, checksum and package manifest.
• MinerU runs automatically for eligible documents under persistent consent
  and uses page-preserving subsets for long/oversize papers. PyMuPDF remains
  the authority for evidence and pages.

Validation

• 3 release-eligible frozen holdouts passed the published rubric.
• 39 physical pages produced 102 EvidenceUnits and 78 ClaimRecords.
• Page accuracy, numeric fidelity, evidence coverage and template completeness
  were all 100% for the deterministic holdout gates.
• 6 pathological PDF/failure fixtures passed.
• 150 repository tests, Skill validation, compilation, Markdown-link and
  anti-leak/privacy checks passed locally.
• MinerU added 2 section candidates and 12 figure candidates across the
  holdouts while creating zero authoritative EvidenceUnits.

Scope

The beta supports a single local Zotero paper and a contained Obsidian export
on Windows with a local-capable Agent. It does not promise pure-web execution,
batch review, Zotero write-back, bidirectional synchronization or automatic
acceptance of notes without the existing review boundaries.

LitAnchor v0.5.0 — Autonomous Deep Reading

LitAnchor v0.5.0 — Autonomous Deep Reading

LitAnchor v0.5.0 promotes the release-candidate workflow to the first stable
autonomous deep-reading release.

What is stable

• Zotero Local API lookup with unique-item and unique-PDF resolution.
• PyMuPDF-authoritative physical pages, quotations, coordinates, links and
  original-PDF figure crops.
• Six-pass, paper-type-aware full-text reading before Final-template rendering.
• Evidence-first semantic materialization: EvidenceUnits precede ClaimRecords.
• Full SectionSynthesis plus independent fidelity and recall reviews.
• Complete figure inventory, 1–3 selected method/result visuals and crop
  provenance gates.
• Persistent local MinerU consent modes and automatic Flash routing for
  eligible files; MinerU content remains non-authoritative until aligned to the
  original PDF.
• Hash-verified, path-contained, no-overwrite Obsidian candidate/final export.

Release evidence

• Six official autonomous papers: 81 physical pages, 182 EvidenceUnits,
  155 ClaimRecords and 15 selected visuals.
• Three additional unseen cross-domain papers passed structured regeneration
  and user review without paper-specific Skill rules.
• One separate fully unseen, source-closed final smoke test passed the frozen
  rubric at 98/100 with zero predefined severe-failure signals.
• 116 repository tests, Skill validation, compilation and privacy/anti-leak
  checks passed locally.

The final smoke paper, its PDF, generated note and runtime ledgers are not
committed. Stable code promotion does not convert pending user visual review of
that private candidate note into an accepted review.

Boundaries

v0.5.0 does not add Zotero MCP, Zotero write-back, bidirectional synchronization,
paid MinerU APIs, local full MinerU, multi-paper reviews or unattended Skill
publication. External MinerU upload still follows the user’s local consent
mode, and PyMuPDF remains the evidence authority.

LitAnchor v0.5.0-rc1 — Autonomous Deep Reading

LitAnchor v0.5.0-rc1 — Autonomous Deep Reading Pre-release

LitAnchor v0.5.0-rc1 is the first release candidate that runs the complete
single-paper deep-reading pipeline from a Zotero PDF to a reviewed
Paper Template - Final Obsidian note.

Highlights

• PyMuPDF-authoritative physical pages, quotations, coordinates, Zotero links
  and original-PDF figure crops.
• Conditional MinerU Flash structure enhancement with three persistent local
  consent modes; MinerU output never becomes evidence without page alignment.
• Six explicit full-text reading passes followed by Evidence/Claim ledgers,
  cohesive section synthesis and independent fidelity/recall review.
• Paper-type-aware depth gates, including primary and secondary profiles.
• Complete all-figure inventory, 1–3 key visual selections, crop provenance and
  user visual/link acceptance before final promotion.
• Separate equation, metric and parameter claims; numeric, unit, modality,
  symbol and original-page verification gates.
• No-overwrite Obsidian export and local-only runtime/audit artifacts.

Validation

• Official autonomous set: 6 papers, 81 physical pages, 182 EvidenceUnits,
  155 ClaimRecords and 15 selected visuals.
• Additional cross-domain generalization smoke test: 3 previously unseen
  papers, all regenerated from structured artifacts and accepted by the user.
• Extended renderer/quality regression: ResNet, LOVECLIM and climate U-Net.
• Automated suite: 116 passed, 0 failed.
• Skill validation, Python compilation, repository privacy and anti-leak
  audits: passed.

Boundaries

• MinerU Flash is optional, token-free and subject to service limits. PyMuPDF
  remains authoritative.
• No Zotero MCP, Zotero write-back, bidirectional sync, paid MinerU API,
  multi-paper review or unattended release.
• Stable v0.5.0 is intentionally withheld until a separate final unseen-paper
  smoke test passes without a blocker or severe fidelity error.

LitAnchor v0.4.1 — Deterministic Deep-Reading Preview

LitAnchor v0.4.1 is a pre-release that closes the deterministic v0.4 evidence and rendering work.

Included

• reviewed ResNet, LOVECLIM, and U-Net notes using Paper Template - Final
• page-verified evidence and Zotero links
• paper-type-aware content gates
• sentence-complete evidence validation
• numeric and unit rendering checks
• cross-section consistency, metric/experiment recall, and visual result coverage
• PyMuPDF baseline plus optional MinerU Flash structure-enhancement adapter

Validation

• 60 unit tests passed
• official Skill validation passed
• three reviewed example notes passed final content gates

Important scope boundary

Automatic multi-pass full-text close reading, automatic Evidence/Claim Ledger construction, independent semantic review, and unattended note generation are not complete in v0.4.1. Those capabilities remain the explicit target of v0.5.

This release is marked pre-release and should not be presented as autonomous full-text paper reading.