v0.9.3 — Project Entry Points

What's Changed

• v0.9.3: refresh project entry points by @jameswei in #50

Full Changelog: v0.9.2...v0.9.3

v0.9.2 — Bilingual Learning Docsite

What's Changed

• Document v0.9.1 release milestone by @jameswei in #48
• docs: add bilingual learning docsite by @jameswei in #49

Full Changelog: v0.9.1...v0.9.2

v0.9.1 — v0.9 Workbench UI/UX Corrective Completion

v0.9 Workbench UI/UX corrective completion

v0.9.1 completes the v0.9 Workbench UI/UX delivery after the initial v0.9.0
release did not meet the intended interaction and presentation quality.

What changed

• Reworked the local Workbench around learner questions for Observe, Diagnose,
  Refine, and Revision.
• Made stage results, next steps, proposal decisions, comparisons, revision
  history, and stage-scoped inspection data clearer and more consistent.
• Improved corpus inspection with compact totals, a member coverage matrix, and
  grouped aggregate evidence.
• Added a concise Workbench UI/UX verdict as a stable reference for later work.

Included review fixes

• Indexed corpus coverage cells before rendering.
• Corrected and localized corpus evidence labels.

Validation

• PR Fast validation and Full extraction passed.
• Exact-merge Main smoke passed on main.
• GitHub Pages deployment passed.

v0.9.0 — Workbench UI/UX Redesign

v0.9.0 — Workbench UI/UX Redesign

Status: This note describes the v0.9.0 source change. Use
GitHub Releases
for current publication availability.

v0.9.0 redesigns the bundled Local Visual Workbench around one document and
its preparation journey. It keeps the existing application services,
immutable records, CLI behavior, and trusted-local boundary.

Workbench changes

• Use one coherent shell with Documents and Corpora navigation.
• Add guided sources or one supported upload from one Add modal.
• Group immutable records by source and numbered preparation round.
• Follow learner-question stages for Observe, Diagnosis, Refine, and Revision.
• Keep Summary, Evidence, and Artifacts scoped to the selected stage.
• Explain finding meaning, canonical severity, and the available next step.
• Separate proposal creation, decision choice, and decision recording.
• Reuse readable comparisons for proposed and applied changes.
• Open JSON, Markdown, and verified project-generated HTML in focused readers.
• Show compact visible hashes while preserving full SHA-256 values in records,
  identity checks, payloads, and copied data.
• Switch Workbench-owned UI between English and Simplified Chinese without
  resetting the current task.
• Open a canonical rule reference derived from the Python rule and refiner
  registries.
• Preserve the last accepted workspace view across refresh failures and avoid
  automatic mutation replay.

Interface roles

The browser can complete the supported single-document lifecycle. It does not
generate CLI continuation commands. The CLI remains the full interface for
all lifecycle, corpus, and verification commands and can use the same
published workspace records.

Corpus creation and execution remain CLI-only. The Workbench can inspect a
verified corpus through the same Summary, Evidence, and Artifacts composition.

Compatibility and boundaries

v0.9.0 changes the bundled human interface and its private internal payload.
It adds no public API, persisted schema, migration, new diagnosis rule,
refiner, producer, or CLI behavior.

The Workbench remains source-only, loopback-only, and intended for one trusted
local user. It does not render or serve an uploaded original. It provides no
hosted processing service, authentication, remote access, or multi-user model.

The project boundary still starts with a raw document and ends with an
immutable prepared revision. Chunking, embeddings, indexing, retrieval,
generation, RAG evaluation, and downstream integration remain outside the
project.

Read the Local Visual Workbench guide for the
current workflow and the
approved plan for the milestone
scope and acceptance criteria.

v0.8.1 — Learning Curriculum Refresh

v0.8.1 is a documentation-focused patch. It keeps the v0.8 Interactive
Document Lifecycle behavior unchanged.

Changes

• Replace eight milestone-named lessons with five lifecycle-topic lessons.
• Keep setup, shared terms, and the learning map in one learning hub.
• Teach the CLI and Local Visual Workbench as complementary interfaces over shared application behavior.
• Clarify complete and missing-model corpus outcomes.
• Keep publication wording tied to GitHub Releases.

Compatibility and boundaries

This patch changes no dependency, schema, fixture, CLI behavior, Workbench
behavior, site, deployment model, security posture, or public API. It remains
source-only and trusted-local.

Start with the learning hub. See the release note for full details.

v0.8.0 — Interactive Document Lifecycle

v0.8.0 completes the single-document preparation lifecycle in the Local Visual Workbench.

Highlights

• Observe the guided whitespace fixture or one supported local document.
• Diagnose verified observations and approved prepared revisions.
• Inspect named findings and D007/R002, D009/R001, and D010/R003 refiner capabilities.
• Create readable proposal previews without editing JSON.
• Approve or reject through an explicit browser action.
• Inspect immutable decision, transformation, lineage, revision, and reversal evidence.
• Continue through the unchanged CLI when preferred.

State and authority

Proposal panels belong to their exact diagnosis contexts. Pending proposals do not lock record browsing; navigation is disabled only while a lifecycle mutation is in flight. Reload and restart restore no proposal panel, and the browser never automatically replays a state-changing action.

Diagnosis does not authorize mutation. Only refinement-manifest.json.decision is persisted decision authority.

Boundaries

This release changes no project dependency, CLI argument, persisted record schema, or public API. The Workbench remains local, loopback-only, single-user, trusted-local, and source-only. This GitHub Release contains only the automatically generated source archives; no custom binary or container assets are published.

v0.7.1 — Diagnostic and Refinement Identifier Cleanup

v0.7.1 removes the redundant TCW- prefix from diagnostic rule IDs and refiner IDs.

Identifier changes

• Diagnostic rule IDs are now D001 through D010.
• Refiner IDs are now R001 through R003.
• Rule and refiner names, versions, severities, parameters, mappings, and behavior are unchanged.
• Record IDs and hashes that include these identifiers change naturally.

Breaking record change

Records generated before v0.7.1 are not supported as current inputs. Delete old build/ data and regenerate the records with v0.7.1. The project provides no migration, alias, fallback, or dual-ID compatibility.

Boundaries

This maintenance release changes identifier values only. It adds no workflow, dependency, hosted service, public API, or deployment change. The project remains a source-only, local document-preparation workbench.

v0.7.0 — Web Observation Workflow

v0.7.0 makes observation the first document workflow available in the Local
Visual Workbench.

Highlights

• Start the Workbench from a new empty workspace.
• Observe the guided policy-memo.md fixture without Docling model files.
• Upload one .docx, .md, .pdf, or .txt document up to 32 MiB.
• Follow honest ordered stage feedback without percentage estimates.
• Refresh the complete workspace after publication and select the new record.
• Keep published records immutable and uploaded source content out of the
  browser.

Boundaries

The Workbench can run observation. Diagnosis, refinement, and corpus workflows
remain CLI operations. This release changes no persisted record schema and adds
no dependency.

The internal loopback routes are not a public API or an access-control boundary.
The project remains source-only and provides no hosted document-processing
service.

Read the
Local Visual Workbench guide
for exact behavior and the
v0.7 lesson
for a model-free browser exercise.

v0.6.1 — Agent Documentation Hygiene

v0.6.1 is a source-only maintenance release. It makes repository navigation
shorter and gives each completed milestone one durable outcome-and-rationale
record.

The release consolidates the final v0.5 design, removes obsolete execution
records, and aligns package version metadata at 0.6.1.

Product behavior does not change. Records, schemas, fixtures, lessons,
Workbench behavior, the website, CI responsibilities, deployment,
compatibility, security, and roadmap direction remain unchanged.

v0.6.0 — Shared Workbench Workspace

v0.6.0 keeps the read-only Local Visual Workbench open around one shared, fixed-layout workspace.

Highlights

• Use build/ by default or select an isolated workspace with --workspace.
• Publish records with the existing CLI workflows, then accept them with manual transactional refresh.
• Keep the last good in-memory snapshot, record details, and captured artifact bytes when a complete refresh candidate fails verification.
• Repair or remove the invalid candidate and refresh again to return to READY.

The Workbench remains a foreground process. Stop it with Ctrl-C.

Breaking Workbench CLI change

The current interface is:

corpus workbench [--workspace WORKSPACE] [--port PORT] [--no-open]

The command no longer accepts positional record roots. Producer commands keep their existing defaults and --output-root options.

The Workbench discovers records only under these workspace families:

extraction-observatory/
evidence-based-diagnosis/
controlled-revisions/
corpus-inspection/

Compatibility and distribution

• Persisted records keep format_version 1.
• v0.6 changes no record JSON Schema or persisted record shape.
• Current format-version-1 records remain usable when they pass the current verifiers; no future cross-version reader promise is created.
• This is a source-only release with no custom assets, prebuilt binaries, Docker images, hosted service, or public API.

The bundled browser remains read-only and loopback-only. It does not upload documents or run lifecycle workflows. Use the CLI for workflow execution.

Start with the v0.6 lesson or read the complete release note.