Add challenge and exclusion review handling

workplans/GUIDE-BOARD-WP-0005-challenge-and-exclusion-handling.md

@@ -4,12 +4,12 @@ type: workplan
 title: "Challenge And Exclusion Handling"
 repo: guide-board
 domain: markitect
-status: active
+status: completed
 owner: codex
 planning_priority: high
 planning_order: 5
 created: "2026-05-15"
-updated: "2026-05-15"
+updated: "2026-05-16"
 state_hub_workstream_id: "fb11e1c7-6c0c-4ec7-a163-da98b2fe9f8f"
 ---
 
@@ -42,7 +42,7 @@ but the core should preserve them without embedding domain policy.
 
 ```task
 id: GUIDE-BOARD-WP-0005-T001
-status: todo
+status: done
 priority: high
 state_hub_task_id: "6ff4e6f7-bce6-4e7f-a5af-e0c67cfa7e55"
 ```
@@ -57,11 +57,21 @@ Acceptance:
 - Keep the data contract usable by executable harnesses, hosted suites, and
   procedural packs.
 
+Progress:
+
+- Added `docs/schemas/challenge-set.schema.json` and
+  `docs/schemas/exclusion-set.schema.json`.
+- Added optional `challenges_ref` and `exclusions_ref` assessment profile
+  fields.
+- Supported requirement, check, evidence, result, classification, authority
+  source, owner, review status, rationale, review date, expiry, native ID, and
+  metadata fields.
+
 ## D5.2 - Policy Application And Finding Annotation
 
 ```task
 id: GUIDE-BOARD-WP-0005-T002
-status: todo
+status: done
 priority: high
 state_hub_task_id: "fd384bd3-40c4-4344-8b7d-cb123dbf2cac"
 ```
@@ -76,11 +86,20 @@ Acceptance:
 - Add tests that prove challenge and exclusion records affect reporting without
   corrupting gate semantics.
 
+Progress:
+
+- Loaded challenge and exclusion refs through the policy layer.
+- Annotated findings with challenge refs, exclusion refs, and review status.
+- Annotated matching evidence with review refs.
+- Kept default `unexpected_findings` gate semantics visible unless a finding is
+  separately expected or waived.
+- Added tests proving challenged and excluded findings remain gate-visible.
+
 ## D5.3 - Report Visibility And Review Workflow
 
 ```task
 id: GUIDE-BOARD-WP-0005-T003
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "791071c0-8a9a-462b-83b3-75548bb8524f"
 ```
@@ -94,11 +113,19 @@ Acceptance:
   run.
 - Document how an operator should treat challenged or excluded findings.
 
+Progress:
+
+- Added Markdown report review summaries.
+- Added challenge, exclusion, unresolved defect, and unresolved review counts to
+  retention summaries and trend projections.
+- Included applied challenge and exclusion records in JSON assessment packages.
+- Exposed review counts through existing retained run helpers.
+
 ## D5.4 - Tests And Documentation
 
 ```task
 id: GUIDE-BOARD-WP-0005-T004
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "43b966da-af8d-479b-93bd-6b6741fdab37"
 ```
@@ -111,6 +138,14 @@ Acceptance:
 - Update assessment operations, extension SDK, and compliance evidence pack docs.
 - Keep certification boundary language explicit.
 
+Progress:
+
+- Added focused schema and policy tests through a fixture extension scenario.
+- Updated assessment operations, extension SDK, compliance evidence pack, and
+  architecture docs.
+- Kept boundary language explicit: challenges and exclusions are review state,
+  not certification conclusions.
+
 ## Definition Of Done
 
 - The core has separate, tested concepts for expectations, waivers, challenges,