whetstone_DSL/docs/taskitem_pipeline_gap_log_2026-03-08_multi_project.md

Taskitem Pipeline Gap Log (Multi-Project Targeting) - 2026-03-08

Scope

Runs analyzed:

• logs/taskitem_runs/constcad_ecosystem_roadmap_20260307_210200
• logs/taskitem_runs/constcad_ecosystem_roadmap_20260307_210213
• logs/taskitem_runs/sprint_005_execution_spec_whetstone_20260307_221636

Input:

• /home/bill/Documents/cad_orchestrator/docs/constcad_ecosystem_roadmap.md

Observed Gap

1. Multi-project targeting is not reliably grounded from orchestration specs.

• Symptom: generated taskitems target Whetstone-internal files (for example: editor/src/mcp/RegisterArchitectIntakeTools.h, tools/mcp/run_sprint_taskitem_pipeline.sh) instead of the intended integration files in cad_orchestrator, hivemind, gleaner, and constcad.
• Repro detail:
  • default workspace run and WSTONE_WORKSPACE=/home/bill/Documents run both produced the same Whetstone-internal targetFiles.
  • reproduced again on SPRINT-005 execution spec run with WSTONE_WORKSPACE=/home/bill/Documents.
• Impact:
  • autonomous implementation for cross-repo orchestration work is misdirected.
  • worker token efficiency gains are reduced by required manual correction.

Initial Workaround

• Use a hardened sprint execution spec with explicit sections and concrete file targets:
  • /home/bill/Documents/cad_orchestrator/docs/sprints/sprint_004_execution_spec_whetstone.md
• Keep WSTONE_WORKSPACE at the mono-root (/home/bill/Documents) for cross-repo tasks.

Proposed Tooling Fix Direction

1. Add multi-project path grounding in architect/taskitem generation:

• detect absolute and repo-qualified file targets from spec
• preserve them in targetFiles without replacing with internal defaults

2. Add validator rule:

• if spec includes explicit external target files but generated taskitems map to internal editor paths, classify as capability gap.

3. Add queue blocker class:

• cross_project_target_mismatch