declarative Markdown workflow layer

workplans/MKTT-WP-0011-markdown-dataflow-pipeline-workflows.md

@@ -3,7 +3,7 @@ id: MKTT-WP-0011
 type: workplan
 title: "Markdown Dataflow Pipeline Workflows"
 domain: markitect
-status: todo
+status: done
 owner: markitect-tool
 topic_slug: markitect
 planning_priority: P2
@@ -51,7 +51,7 @@ See `docs/markdown-dataflow-workflow-assessment.md`.
 
 ```task
 id: MKTT-WP-0011-T001
-status: todo
+status: done
 priority: high
 state_hub_task_id: "c335cbaa-dfb9-4df5-b1ae-87aaf6097bd8"
 ```
@@ -61,11 +61,18 @@ steps, outputs, variables, dry-run behavior, diagnostics, and provenance.
 
 Output: workflow schema, examples, and validation diagnostics.
 
+Implemented: `docs/workflow-definition-standard.md` defines the workflow
+standard with metadata, intent, inputs, outputs, steps, dependencies,
+conditions, artifacts, permissions, resource requirements, timeouts, retry
+policies, escalation rules, observability events, and human/agent/system
+responsibility boundaries. `WorkflowPlan` preserves all standard sections and
+unknown extension fields.
+
 ## P11.2 - Implement Markdown source collectors
 
 ```task
 id: MKTT-WP-0011-T002
-status: todo
+status: done
 priority: high
 state_hub_task_id: "16a89801-d96d-437f-a883-81d09586f47a"
 ```
@@ -75,11 +82,15 @@ selectors, sections, blocks, metrics, and future reference/index backends.
 
 Output: source collector API, selector integration, and tests.
 
+Implemented: workflow inputs collect `file`, `path`, `files`, `glob`, and
+`directory` Markdown sources, support frontmatter filters, metrics,
+frontmatter, selectors, and named extractions.
+
 ## P11.3 - Implement deterministic step registry
 
 ```task
 id: MKTT-WP-0011-T003
-status: todo
+status: done
 priority: high
 state_hub_task_id: "808bed93-c7e2-4b34-90f4-f6f961fef503"
 ```
@@ -89,11 +100,15 @@ render, contract stub generation, contract checks, and data shaping.
 
 Output: deterministic workflow runner with dependency ordering.
 
+Implemented: deterministic workflow runner supports dependency ordering and
+step kinds `shape`, `extract`, `query`, `template`, `compose`, `transform`,
+`include`, `contract_stub`, `contract_check`, and `assisted` boundary.
+
 ## P11.4 - Implement data expression and binding model
 
 ```task
 id: MKTT-WP-0011-T004
-status: todo
+status: done
 priority: high
 state_hub_task_id: "ea1ad9d2-3668-4b65-afb4-f490e5bfd0c6"
 ```
@@ -103,11 +118,15 @@ for example `${sources.adrs.decisions}` or `${steps.summary.markdown}`.
 
 Output: expression resolver, type checks, and missing-reference diagnostics.
 
+Implemented: `${...}` bindings preserve native types for full-expression
+values, interpolate text inside longer strings, support dictionary paths,
+numeric list indexes, and list projection over dictionaries.
+
 ## P11.5 - Add optional assisted processing step boundary
 
 ```task
 id: MKTT-WP-0011-T005
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "ed1adc60-fdd8-4d4c-b4d7-7ce906e641c6"
 ```
@@ -118,11 +137,15 @@ dry-run, optional steps, and policy gates before sending data to a provider.
 
 Output: hook adapter interface and tests with fake providers.
 
+Implemented: assisted steps use the provider-neutral generation hook boundary.
+Without a hook, optional assisted steps are skipped with warning diagnostics and
+required assisted steps fail. Tests include an injected fake hook.
+
 ## P11.6 - Implement multi-output sinks
 
 ```task
 id: MKTT-WP-0011-T006
-status: todo
+status: done
 priority: high
 state_hub_task_id: "902707d7-46fe-45d6-a9ec-b85763065ff9"
 ```
@@ -133,11 +156,15 @@ their source data.
 
 Output: output sink API, path-safety checks, and provenance manifests.
 
+Implemented: outputs can render content or templates, write multiple Markdown
+files under a safe output root, support dry-run planning, and emit output
+records plus provenance/trace events.
+
 ## P11.7 - Add workflow CLI
 
 ```task
 id: MKTT-WP-0011-T007
-status: todo
+status: done
 priority: high
 state_hub_task_id: "ccc26867-5724-4205-b3fe-a8b9d046775d"
 ```
@@ -152,11 +179,19 @@ mkt workflow run <workflow.md>
 
 Include JSON/YAML outputs for agent use.
 
+Implemented:
+
+- `mkt workflow inspect <workflow.md>`
+- `mkt workflow plan <workflow.md>`
+- `mkt workflow run <workflow.md>`
+
+All commands support text, JSON, and YAML output.
+
 ## P11.8 - Add representative end-to-end examples
 
 ```task
 id: MKTT-WP-0011-T008
-status: todo
+status: done
 priority: high
 state_hub_task_id: "f8501ea6-1ead-477d-8f64-c196e7edfe68"
 ```
@@ -168,6 +203,9 @@ Create examples covering:
 - source snippets -> docs
 - deterministic summary -> optional assisted review -> final Markdown
 
+Implemented: examples under `examples/workflows/` cover ADR release notes,
+source snippet extraction, and an optional assisted review boundary.
+
 ## Exit Criteria
 
 - A non-programmer can write a Markdown/YAML workflow that extracts data from