(CODUX-105) Document node-flow workflows

[numnx]

🧩 Task: Document node-flow workflows

Automated task PR opened by Code UX for T07.

📋 Summary

Sprint: Sprint 173 · Repeatable node flows · Task: T07

Implement repeatable n8n-style node workflows in Code UX with durable flow definitions, node invocation execution, MCP automation, agent skill attachment, scheduler support, an editable dashboard canvas, and current documentation.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.5

⏱️ Timing

Started	2026-07-07 12:07:52 UTC
Finished	2026-07-07 12:19:01 UTC
Duration	11m 9s

📊 Token Usage

Metric	Value
Input tokens	153,474
Cached input tokens	2,216,192
Output tokens	30,161
Total tokens	2,399,827
Invocations	1
Tool calls	61
Active time	10m 32s

Included usage estimate (subscription/local login): $2.78

✅ QA Review

⏳ QA review runs after this PR is opened. Check the task card in the dashboard for the outcome once it lands.

📝 Full Task Prompt

## Objective
Document the new repeatable node-flow feature so developers, MCP integrators, and dashboard users understand flow creation, dynamic widgets, node invocation execution, scheduling, and agent skill attachment.

## Scope
- Create `docs/architecture/node-flows.md`
- Create `docs/dashboard/node-flows.md`
- Edit `docs/mcp/tools-and-contracts.md`
- Edit `docs/dashboard/scheduler.md`
- Edit `docs/architecture/execution-invocation-tracking.md`
- Edit `docs/index.md`
- Edit `docs/SUMMARY.md`
- Create `docs-web/user/dashboard/node-flows.md`
- Edit `docs-web/user/dashboard/scheduler.md`
- Edit `docs-web/developer/mcp-tools.md`
- Edit `docs-web/architecture/data-model.md` if the public data-model page exists and covers persisted tables

## Implementation Requirements
1. Document the architecture: `node_flows`, agent skill attachments, run records, node run records, and how `execution_invocations` uses `type: "node_flow"` and `type: "node_flow_node"`.
2. Document the MCP surface for `manage_node_flows`, including create/update graph payloads, validation, run, run inspection, and attach/detach examples with secret-safe widget guidance.
3. Document dashboard usage for the Nodes page: library, canvas editing, dynamic widget inspector, validation states, manual run panel, agent attachment, and responsive/accessibility expectations.
4. Document scheduler behavior for `node_flow` entries, including recurrence, JSON input, pause/resume, failure handling, and run due semantics.
5. Add senior-grade agent guidance explaining how specialist agents should design Code UX-adapted node workflows, define editable widget schemas, avoid one-to-one n8n copying, preserve repeatability, and validate node fields.
6. Link new docs from `docs/index.md`, `docs/SUMMARY.md`, and the corresponding docs-web navigation/index pages where applicable.
7. Keep claims accurate to the implemented feature; do not claim checks, providers, or node types that are not implemented by prior tasks.

## Constraints
- Do not include raw PR summaries or release notes.
- Do not claim a validation command passed unless it was actually run by the worker.
- Keep canonical `docs/` and public `docs-web/` behavior descriptions aligned.
- Avoid exposing secret values in examples.

## Verification
- Run `pnpm run lint` to catch TypeScript/doc import side effects if any docs are referenced by typed tooling.
- Run `pnpm run build` and confirm docs or bundled assets do not break the package build.
- Manually verify new documentation links from `docs/index.md` and `docs/SUMMARY.md` point to existing files.

🌿 Branch Info

Base: feature/CODUX-173-repeatable-node-flows
Head: task/feature-codux-173-repeatable-node-flows-t07-codex-mralu89w

---

🤖 Generated by Code UX