docs: add browser click workflow example

This commit is contained in:
lda
2026-06-15 00:33:00 +07:00 Verified
parent 06bd1f36b4
commit 18df04101c
5 changed files with 54 additions and 0 deletions
+2
View File
@@ -75,6 +75,8 @@ Evidence:
- `src/wf_sources_python/`
- `tests/examples/test_report_workflow_example.py`
- `tests/wf_sources_python/test_loader.py`
- `examples/browser_click_workflow/`
- `tests/examples/test_browser_click_workflow_example.py`
## Limitations
+3
View File
@@ -931,6 +931,9 @@ single deterministic extraction node. The surrounding Python source includes
additional capabilities used for capability discovery and extensibility
evidence; it is not evaluated as a multi-node read -> extract -> render
pipeline in this artifact.
A supplemental browser-click example demonstrates a serial three-node workflow
with bounded before/after snapshots; it is supporting evidence, not the main
case study.
(Evidence: `tests/examples/test_report_workflow_example.py`.)
+1
View File
@@ -187,6 +187,7 @@ stable.
- Completed thesis system-design draft: `docs/add/system-design-implementation.md`
now frames the platform as a formal system design/implementation report backed
by `docs/add/evidence-index.md` and the report-workflow case study.
- Completed supplemental browser-click workflow example with serial multi-node lifecycle evidence.
## Historical References
+2
View File
@@ -69,6 +69,8 @@ see [`workflow platform presentation`](add/2026-06-workflow-platform-presentatio
- `examples/rpc_cli_smoke.py` spawns `wf-rpc-server`, runs the bounded CLI
lifecycle from the RPC CLI smoke runbook, and cleans up. Use
`--keep-temp` to preserve the generated config/store on failure.
- `examples/browser_click_workflow/` is a serial browser-click workflow
example with bounded before/after snapshots and full lifecycle tests.
## Documentation