• … work, compress bloated incident log
    
    - Delete org-graph-as-work-graph-unified-loop-requirements.md: fully
      superseded by org-graph-unification-and-universal-self-planning-
      requirements.md; folded its one non-duplicated detail (the 2084590a
      benchmark-narration trigger incident) into that doc's background instead.
    - Split scheduler-production-polling-loop-{requirements,design}.md by
      completion status: FR-2 (in-flight task reconciliation, shipped) moves to
      docs/done/scheduler-task-reconciliation-{requirements,design}.md; FR-1
      (new-goal auto-dispatch, still undecided) becomes a small standalone
      docs/todo/scheduler-new-goal-dispatch-requirements.md instead of staying
      bundled with a doc that's mostly done.
    - Compress validator-test-script-narrative-output-issue.md's six
      ad-hoc "第N轮更新" paragraphs crammed into one status line into a scannable
      timeline table; moved the task 2084590a benchmark evidence into §1 where
      the other repro examples live instead of leaving it stranded in the header.
    - implementation-gap-analysis.md: logged two new gaps found today (no
      pre-Coder review of Planner's output; node execution still depends on
      native Dynamic Workflow) plus the architecture.md §10.1 staleness itself,
      per that doc's own "edit in place" maintenance convention.
    - Updated the doc-path references left in src/task_execution.py and
      src/task_reconciliation.py docstrings to point at the new locations.
    
    Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
    bboonnee authored
     
    Browse Code »
  • - org-graph-unification-phase1-review-gate-design.md: implementable SDD for
      inserting a planner_reviewer stage (new org role, since _PRE_STATE/
      _POST_STATE map org_node -> status 1:1 and can't reuse "validator" twice)
      between Planner and Coder. Folds in the P0 resume-artifact-assumption fix
      and a newly-found sibling KeyError in the fresh-run path.
    - graphlemon_architecture.md §10.2: records that §10.1's "方案 A" (reuse
      Claude Code's native Dynamic Workflow for Work Graph execution) was
      superseded -- the graph-orchestration layer already diverged (REQ-06
      checkpoint/resume), and per today's decision the single-node execution
      layer is being migrated off it too, for controllability.
    - work-graph-node-execution-deblackbox-requirements.md: requirements+design
      for that migration -- replace the 3 remaining write_workflow_script/
      execute_work_graph call sites with plan_work_graph()'s already-proven
      flat `claude --agent` + JSON-fence-extraction pattern.
    - Cross-referenced the two new docs from each other and from the existing
      P0/P2 todo docs they fold into or relate to.
    
    Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
    bboonnee authored
     
    Browse Code »
  • Merges the fixed-flow change (Planner -> Validator -> Coder -> Validator),
    universal per-org-agent self-planning, node-level validator skill, and
    frontend dynamic/historical graph asks into one requirements doc, folding
    in the P0 resume-artifact bug and the P2 test_script structural-fix
    placeholder that were blocking on the same design. Records the user's
    2026-08-08 decision to merge all four org stages into one work_graph_run
    (scheme A) rather than cross-graph routing (scheme B), plus the concrete
    schema conflicts that decision surfaces (work_graph_run.org_node's single
    value + unique-active-run index) for Phase 2's SDD to resolve.
    
    Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
    bboonnee authored
     
    Browse Code »
  • work-graph-partial-artifact-persistence and work-graph-self-planning-
    and-loop-back (requirements + design) are all shipped and tested;
    move them out of docs/todo/ and fix up the docs/todo/*.md and
    src/*.py path references that pointed at their old location.
    
    Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
    bboonnee authored
     
    Browse Code »
  • Real end-to-end verification of Work Graph self-planning + loop-back
    (task 2084590a) hit the narrative-output problem again -- this time on a
    self-planned benchmark node, not test_script, disproving the earlier
    "BRD/PRD/SDD/Benchmark won't recur" hypothesis in validator-test-script-
    narrative-output-issue.md. The judge caught it once (round 3) but couldn't
    force a fix; the loop_back retry limit correctly exhausted and blocked the
    task cleanly instead of hanging or crashing.
    
    Also drafts org-graph-as-work-graph-unified-loop-requirements.md: extending
    today's Work-Graph-internal judgment/on_fail/loop_back mechanism up to the
    Org Graph itself, so Coder doesn't start from an unreviewed Planner output
    and a Validator FAIL can route to a precise node instead of a whole phase.
    Flags the real hard part (Planner/Coder each plan their own graph_manifest,
    so node ids don't share an address space across the org boundary) as the
    first open question, not yet implemented.
    
    Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
    bboonnee authored
     
    Browse Code »
  • v_task_board's task_id cell now links to #/graph?task_id=<id> for quick
    navigation to a task's execution graph. v_graph_console reads that param
    to preselect the task, and syncs the URL (via history.replaceState) on
    every task load -- including the initial auto-preselect -- so the address
    bar always reflects the task actually showing.
    
    Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
    bboonnee authored
     
    Browse Code »
  • graphlemon authored
     
    Browse Code »
  • graphlemon authored
     
    Browse Code »
  • …76ae-main-checkout-drift
    graphlemon authored
     
    Browse Code »
  • …4843-main-checkout-drift
    graphlemon authored
     
    Browse Code »