docassert 1.0.2

Patch: a fresh docassert new project scaffold failed its own validation (comment-only required sections in the packaged project template). Found exercising the starter template's adopter path end to end; the regression test now runs the README's exact command sequence. Implements spec v0.8.1. See CHANGELOG.md.

docassert 1.0.1

Implements spec v0.8.1: tracker items labelled scope:exempt are excluded from bridge scope classification entirely — not matched, unverified, or orphaned, and never part of the reconciliation exit code. For operational automation (monitoring alarms, dependency bots) that must open issues in a governed repository; the bridge never applies the label itself.

Found live: the reference deployment's CI-health sentinel and its scope guard deadlocked overnight, each correctly keeping the other red. Full story in CHANGELOG.md. SemVer patch under the 1.x stability policy; 210 tests green.

docassert 1.0.0

The stability release. Functionally identical to 0.20.2 — the number is the promise: the guarantees in STABILITY.md are now in force.

What 1.x guarantees, binding from this release:

• The CLI surface — no command or flag renamed or removed except by the published deprecation process, never before a major.
• Machine-readable output shapes — the JSON report, bridge status JSON, badge payloads, and projects.yaml only gain fields in minors.
• Exit-code semantics — zero for a clean gate, non-zero for blocking failures; advisory findings never touch exit codes.
• Packaged-data semantics — schemas, criteria, profiles, and templates track the PMO as Code spec, spec-first; a repo-local copy always wins.
• The spec relationship — this release implements spec v0.8.0, with the 73-case conformance suite running in CI at that tag.

Unit testing for business documents: validate structure deterministically, trace requirements end to end, derive project status from the documents — never from self-reporting.

docassert 0.20.2

Defect-fix release from a full code/content/automation audit. No CLI surface changes.

Critical fix: the bridge marker index assumed oldest-first issue ordering while the GitHub API lists newest-first, so a converged (closed) duplicate could shadow its real open issue — bridge status reported open work as done, scaffold updated the wrong issue, and reconcile refreshed a closed scope report. The index now ranks open before closed, then lowest number.

Also fixed: renderer crash on malformed review_by dates; amber pages whose verdict tooltip claimed no recorded causes; the green verdict overclaiming on failing drafts; verdict/tooltip risk counts disagreeing about the appetite; lossy </ JSON embedding; validate guessing charter for a missing kind; cross-repo scope findings on project pages; org-owned Projects v2 boards; recursion-unsafe sequence-acyclic; isolated sub-plan state; --project-number edge crash.

Changed: config reads cached on (path, mtime); corpus loaded once per index/pages build; CI tests Python 3.14.

Full details in CHANGELOG.md. 208 tests green.

v0.20.1

Tooltips across the status pages: stat derivations, coverage gap lists, sequence-bar scope breakdowns, matrix risk descriptions, the temporal-fact rule, verdict causes. Native title attributes; pages stay self-contained.

v0.20.0

Changed

• Work charts drop the time axis (spec 0.8.0): dependency-sequence position, scope-point width (stories + acceptance criteria, no estimation), XS/S/M/L/XL buckets, execution-fact states. Un-bridged projects get the chart too.

Added

• The after sequencing relation with the always-blocking sequence-acyclic check.

v0.19.0

Changed

• Risk appetite (spec 0.7.0): open risks amber only at or above risk_amber_score (default 6; 0 = strict). Below-threshold exposure stays fully reported.

Added

• Approved charters' dates.target as an implicit 'Charter target' milestone.

v0.18.0

Changed

• Status pages redesigned as decision-grade dashboards: deterministic verdicts from real causes, stat cluster, milestone timelines as temporal facts, execution lanes from real issue lifetimes, interactive risk heat matrix, filterable views, git-history activity. Fully self-contained; the index degrades without JavaScript.

Added

• Dated charter milestone parsing (spec 0.6.0) with the advisory milestones-dated check; per-issue facts on bridge status for presentation; index coverage % and next dated marker.

v0.17.0

Added

• STABILITY.md: the 1.x stability and deprecation policy, with a CLI reference generated from the live argument parser.

Changed

• Coverage floor raised to 85% (current: 85.3%).

v0.16.0

Added

• The operations document kind (spec 0.5.0): governed service catalogs with Level/Measure fields, required review_by, svc-items-complete and advisory ops-review-fresh checks, the operations profile, and review staleness as an amber input to derived status.