内核限制追踪：map 子流程 end 递归限制 + if 块作用域隔离（plaita-nodes report 节点是 workaround）
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 28/100
Research direction
Start with src/plaita_nodes/report.py and its docstring, then read ADR-2026-08-27 for the broader orchestration context. Identify the kernel behavior behind map-end aggregation and if-block scope isolation before proposing a path forward. Done means the native kernel semantics are available, and report has a documented migration or deprecation decision.
Written by the indexing model from the issue text.
Description
背景
plaita-nodes 的 report 节点（src/plaita_nodes/report.py）是为绕开内核两个限制而存在的 run 级结果通道：
- map 子流程 end 的表达式递归限制 —— 子流程 end 无法引用/聚合自身累积结果；
- if 块内赋值对块外不可见 —— 作用域隔离导致块内产物无法带到块外做聚合。
现状 workaround
report 节点用文件做旁路：map 子流程把结构化结果 append 到 <repo>/.flowcast/plaita-reports/<token>.jsonl，主流程聚合节点按同一 token read 回来（write/read 两个 action，0.6.x 起在用）。
期望
- 内核层面解决（map 聚合语义或作用域规则调整）后，业务流程迁回内核原生表达；
- 届时评估
report节点降级/移除（至少在 plaita-nodes 文档标注 deprecated 并给出迁移路径）。
关联
- plaita-nodes：
src/plaita_nodes/report.py（docstring 同步有此说明） - 大仓 ADR-2026-08-27 编排收敛（plaita + agentproc）
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 3h
- Merged PRs (30d)
- 6
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
docling-project/docling-mcp#147 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
autowarefoundation/autoware_carla_scenario#405 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mohitmishra786/readprism#322 ·
Maintainers usually reply within 1 day