first extension execution path

workplans/GUIDE-BOARD-WP-0001-bootstrapping.md

@@ -189,7 +189,7 @@ Acceptance:
 
 ```task
 id: GUIDE-BOARD-WP-0001-T006
-status: todo
+status: done
 priority: high
 state_hub_task_id: "3c757929-a5e4-4c11-bbf1-6d7f26def93e"
 ```
@@ -201,12 +201,13 @@ Acceptance:
 - Provide a minimal extension template.
 - Extension ownership boundaries make later extraction to a separate repository
   straightforward.
+- Python module runner contracts are documented in `docs/EXTENSION-SDK.md`.
 
 ## D1.8 - CMIS Seed Extension Integration
 
 ```task
 id: GUIDE-BOARD-WP-0001-T007
-status: todo
+status: in_progress
 priority: high
 state_hub_task_id: "455f92b0-1d2b-43d0-aa61-464d9dc83a62"
 ```
@@ -218,6 +219,14 @@ Acceptance:
 - CMIS output normalizes into the same evidence model used by other extensions.
 - CMIS capability mappings are extension-owned.
 
+Progress:
+
+- `open-cmis-tck` declares runner entry points through `extension.json`.
+- The CMIS Browser Binding preflight runner executes through the generic runner
+  bridge and produces normalized evidence.
+- The OpenCMIS Java/Maven TCK runner remains external and blocked until the
+  extension harness wrapper is implemented.
+
 ## D1.9 - Containerized Execution Design
 
 ```task