generated from coulomb/repo-seed
command-runner support and first OpenCMIS TCK wrapper boundary
This commit is contained in:
@@ -202,6 +202,8 @@ Acceptance:
|
||||
- Extension ownership boundaries make later extraction to a separate repository
|
||||
straightforward.
|
||||
- Python module runner contracts are documented in `docs/EXTENSION-SDK.md`.
|
||||
- Manifest-declared command runners execute without shell expansion and return
|
||||
normalized evidence through the same runner result contract.
|
||||
|
||||
## D1.8 - CMIS Seed Extension Integration
|
||||
|
||||
@@ -224,8 +226,9 @@ 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.
|
||||
- The OpenCMIS Java/Maven TCK wrapper executes through the command runner bridge
|
||||
and currently reports dependency or configuration blockers as structured
|
||||
evidence.
|
||||
|
||||
## D1.9 - Containerized Execution Design
|
||||
|
||||
|
||||
Reference in New Issue
Block a user