docassert 1.0.0__tar.gz → 1.0.1__tar.gz

{docassert-1.0.0/docassert.egg-info → docassert-1.0.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: docassert
-Version: 1.0.0
+Version: 1.0.1
 Summary: Unit testing for business documents — validate structured Markdown docs against a configurable audit standard.
 Author: C4G Enterprises Inc.
 License: Apache-2.0
@@ -55,7 +55,7 @@ derived from the documents rather than self-reported.
 
 docassert is the reference implementation of **[PMO as Code](https://c4g-john.github.io/pmo-as-code/)** —
 a vendor-neutral standard for running a PMO from version-controlled, declarative
-files. It implements the [PMO as Code specification](https://github.com/c4g-john/pmo-as-code-spec) **v0.3** and passes its [conformance suite](https://github.com/c4g-john/pmo-as-code-spec/tree/main/conformance) in CI.
+files. It implements the [PMO as Code specification](https://github.com/c4g-john/pmo-as-code-spec) **v0.8** and passes its [conformance suite](https://github.com/c4g-john/pmo-as-code-spec/tree/main/conformance) (73 cases) in CI.
 
 ## Install
 
@@ -103,19 +103,20 @@ flagged as TODOs, never invented). The skill's source is
 | `docassert extract <file>` | Extract plain text from a source `.docx` / `.pdf` / `.md` / `.txt` (the first step of doc-to-pmo conversion). Needs the `convert` extra: `pip install "docassert[convert]"`. |
 
 Every document-reading command accepts `--documents-dir` (default `documents/`).
-The full flag-by-flag reference, and what 1.x does and does not promise to
-keep stable, live in [STABILITY.md](STABILITY.md).
+The full flag-by-flag reference, and the 1.x stability guarantees (binding
+since 1.0.0), live in [STABILITY.md](STABILITY.md).
 AI alignment grades at most `alignment_limit` links per run (default 25; set it
 in `consistency.yaml`, `0` = no cap) so API cost stays bounded on large graphs.
 
 ## Document kinds
 
-Twenty kinds, each a `templates/<kind>.template.md` + `schema/<kind>.schema.json`
+Twenty-one kinds, each a `templates/<kind>.template.md` + `schema/<kind>.schema.json`
 + `criteria/<kind>.criteria.yaml` trio: `project`, `charter`, `business-case`,
 `brd`, `prd`, `frnfr`, `user-story`, `test-cases`, `adr`, `risk-register`,
 `raci-stakeholder`, `qa-test-plan`, `data-migration-plan`,
 `release-cutover-plan`, `rollback-plan`, `hypercare-plan`, `runbook`,
-`status-report`, `post-implementation-review`, `benefits-realization`. Adding a
+`operations`, `status-report`, `post-implementation-review`,
+`benefits-realization`. Adding a
 kind is adding a trio — no code for the common cases.
 
 ## Two tiers of checks

{docassert-1.0.0 → docassert-1.0.1}/README.md

@@ -14,7 +14,7 @@ derived from the documents rather than self-reported.
 
 docassert is the reference implementation of **[PMO as Code](https://c4g-john.github.io/pmo-as-code/)** —
 a vendor-neutral standard for running a PMO from version-controlled, declarative
-files. It implements the [PMO as Code specification](https://github.com/c4g-john/pmo-as-code-spec) **v0.3** and passes its [conformance suite](https://github.com/c4g-john/pmo-as-code-spec/tree/main/conformance) in CI.
+files. It implements the [PMO as Code specification](https://github.com/c4g-john/pmo-as-code-spec) **v0.8** and passes its [conformance suite](https://github.com/c4g-john/pmo-as-code-spec/tree/main/conformance) (73 cases) in CI.
 
 ## Install
 
@@ -62,19 +62,20 @@ flagged as TODOs, never invented). The skill's source is
 | `docassert extract <file>` | Extract plain text from a source `.docx` / `.pdf` / `.md` / `.txt` (the first step of doc-to-pmo conversion). Needs the `convert` extra: `pip install "docassert[convert]"`. |
 
 Every document-reading command accepts `--documents-dir` (default `documents/`).
-The full flag-by-flag reference, and what 1.x does and does not promise to
-keep stable, live in [STABILITY.md](STABILITY.md).
+The full flag-by-flag reference, and the 1.x stability guarantees (binding
+since 1.0.0), live in [STABILITY.md](STABILITY.md).
 AI alignment grades at most `alignment_limit` links per run (default 25; set it
 in `consistency.yaml`, `0` = no cap) so API cost stays bounded on large graphs.
 
 ## Document kinds
 
-Twenty kinds, each a `templates/<kind>.template.md` + `schema/<kind>.schema.json`
+Twenty-one kinds, each a `templates/<kind>.template.md` + `schema/<kind>.schema.json`
 + `criteria/<kind>.criteria.yaml` trio: `project`, `charter`, `business-case`,
 `brd`, `prd`, `frnfr`, `user-story`, `test-cases`, `adr`, `risk-register`,
 `raci-stakeholder`, `qa-test-plan`, `data-migration-plan`,
 `release-cutover-plan`, `rollback-plan`, `hypercare-plan`, `runbook`,
-`status-report`, `post-implementation-review`, `benefits-realization`. Adding a
+`operations`, `status-report`, `post-implementation-review`,
+`benefits-realization`. Adding a
 kind is adding a trio — no code for the common cases.
 
 ## Two tiers of checks

{docassert-1.0.0 → docassert-1.0.1}/docassert/__init__.py

@@ -5,4 +5,4 @@ standard: deterministic structural checks that gate a merge, plus optional
 AI-graded semantic checks that advise.
 """
 
-__version__ = "1.0.0"
+__version__ = "1.0.1"

{docassert-1.0.0 → docassert-1.0.1}/docassert/bridge/ops.py

@@ -23,6 +23,10 @@ from .plan import (
 
 MARKER_RE = re.compile(r"<!-- docassert-bridge: ([A-Za-z0-9-]+) -->")
 SCOPE_REPORT_KEY = "scope-report"
+# Spec v0.8.1: items carrying this label are excluded from scope
+# classification entirely. The label is a human decision; the bridge never
+# applies it (it only creates its own bridge:*/scope:* labels below).
+EXEMPT_LABEL = "scope:exempt"
 LABELS = {
     "bridge:feature": ("1d76db", "Feature scaffolded from a product requirement"),
     "bridge:story": ("0e8a16", "Story scaffolded from an approved user story"),
@@ -162,6 +166,8 @@ def reconcile(plan: BridgePlan, gh: G.GhRunner, repo: str) -> tuple[list[str], i
         if key == SCOPE_REPORT_KEY:
             continue
         labels = {lb["name"] for lb in issue.get("labels", [])}
+        if EXEMPT_LABEL in labels:
+            continue
         number = issue["number"]
 
         if key is None:
@@ -221,6 +227,8 @@ def status(plan: BridgePlan, gh: G.GhRunner, repo: str) -> dict:
         key = _marker_of(issue)
         if key == SCOPE_REPORT_KEY:
             continue
+        if EXEMPT_LABEL in {lb.get("name") for lb in issue.get("labels") or []}:
+            continue
         if key is None:
             unverified.append({"number": issue["number"], "title": issue["title"]})
         elif key not in managed:

{docassert-1.0.0 → docassert-1.0.1/docassert.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: docassert
-Version: 1.0.0
+Version: 1.0.1
 Summary: Unit testing for business documents — validate structured Markdown docs against a configurable audit standard.
 Author: C4G Enterprises Inc.
 License: Apache-2.0
@@ -55,7 +55,7 @@ derived from the documents rather than self-reported.
 
 docassert is the reference implementation of **[PMO as Code](https://c4g-john.github.io/pmo-as-code/)** —
 a vendor-neutral standard for running a PMO from version-controlled, declarative
-files. It implements the [PMO as Code specification](https://github.com/c4g-john/pmo-as-code-spec) **v0.3** and passes its [conformance suite](https://github.com/c4g-john/pmo-as-code-spec/tree/main/conformance) in CI.
+files. It implements the [PMO as Code specification](https://github.com/c4g-john/pmo-as-code-spec) **v0.8** and passes its [conformance suite](https://github.com/c4g-john/pmo-as-code-spec/tree/main/conformance) (73 cases) in CI.
 
 ## Install
 
@@ -103,19 +103,20 @@ flagged as TODOs, never invented). The skill's source is
 | `docassert extract <file>` | Extract plain text from a source `.docx` / `.pdf` / `.md` / `.txt` (the first step of doc-to-pmo conversion). Needs the `convert` extra: `pip install "docassert[convert]"`. |
 
 Every document-reading command accepts `--documents-dir` (default `documents/`).
-The full flag-by-flag reference, and what 1.x does and does not promise to
-keep stable, live in [STABILITY.md](STABILITY.md).
+The full flag-by-flag reference, and the 1.x stability guarantees (binding
+since 1.0.0), live in [STABILITY.md](STABILITY.md).
 AI alignment grades at most `alignment_limit` links per run (default 25; set it
 in `consistency.yaml`, `0` = no cap) so API cost stays bounded on large graphs.
 
 ## Document kinds
 
-Twenty kinds, each a `templates/<kind>.template.md` + `schema/<kind>.schema.json`
+Twenty-one kinds, each a `templates/<kind>.template.md` + `schema/<kind>.schema.json`
 + `criteria/<kind>.criteria.yaml` trio: `project`, `charter`, `business-case`,
 `brd`, `prd`, `frnfr`, `user-story`, `test-cases`, `adr`, `risk-register`,
 `raci-stakeholder`, `qa-test-plan`, `data-migration-plan`,
 `release-cutover-plan`, `rollback-plan`, `hypercare-plan`, `runbook`,
-`status-report`, `post-implementation-review`, `benefits-realization`. Adding a
+`operations`, `status-report`, `post-implementation-review`,
+`benefits-realization`. Adding a
 kind is adding a trio — no code for the common cases.
 
 ## Two tiers of checks

{docassert-1.0.0 → docassert-1.0.1}/tests/test_audit_0_20_2.py

@@ -216,3 +216,46 @@ def test_board_get_project_falls_back_to_organization():
     project = board.get_project(OrgOnlyGh(), "acme", 3)
     assert project["id"] == "P1"
     assert project["fields"]["Type"]["options"]["Feature"] == "O1"
+
+
+# ── spec v0.8.1: scope:exempt items are invisible to the scope guard ─────────
+def test_scope_exempt_label_excluded_from_classification():
+    from docassert.bridge.plan import BridgePlan
+    exempt = {"number": 90, "state": "open", "title": "CI health: failures detected",
+              "body": "no marker here", "labels": [{"name": "scope:exempt"}]}
+    stray = {"number": 91, "state": "open", "title": "Add dark mode",
+             "body": "no marker here", "labels": []}
+    plan = BridgePlan(projects=[{"id": "P", "code": "P", "repo": "o/r", "features": []}])
+
+    class ReadOnlyGh:
+        def run(self, args, input_=None):
+            import json
+            if "issues?" in args[1]:
+                return json.dumps([exempt, stray])
+            return "{}"
+
+    data = ops.status(plan, ReadOnlyGh(), "o/r")
+    nums = [i["number"] for i in data["scope"]["unverified"]]
+    assert nums == [91], f"exempt issue leaked into scope: {nums}"
+
+    lines, code = ops.reconcile(plan, ReadOnlyGh(), "o/r")
+    assert code == 1                      # the real stray still alarms
+    assert not any("#90" in ln for ln in lines)
+    assert any("#91" in ln for ln in lines)
+
+
+def test_scope_exempt_alone_exits_zero():
+    from docassert.bridge.plan import BridgePlan
+    exempt = {"number": 90, "state": "open", "title": "CI health: failures detected",
+              "body": "no marker here", "labels": [{"name": "scope:exempt"}]}
+    plan = BridgePlan(projects=[{"id": "P", "code": "P", "repo": "o/r", "features": []}])
+
+    class ReadOnlyGh:
+        def run(self, args, input_=None):
+            import json
+            if "issues?" in args[1]:
+                return json.dumps([exempt])
+            return "{}"
+
+    lines, code = ops.reconcile(plan, ReadOnlyGh(), "o/r")
+    assert code == 0, f"exempt-only board must not alarm: {lines}"