CARD PAO-3 (A3)  written 2026-09-26 01:02:37 -0700  -- BEFORE its first compile
unit: source/ai/path_obstacle_avoidance   base: copies/pao12
observed: path_add_step leaves its chain walk through two 'goto done;' (no /Od attestation).
evidence: D /Od 0x4ca320: byte flag [ebp-0x1e] initialised 1 (TRUE) next to blocks_goal [ebp-0x1d]=0; the
  direction-mismatch exit does 'flag=0; break' (0x4ca3c7/0x4ca3cb); the dot/cross test does 'flag=0' (0x4ca4c7)
  then 'if (flag && (obstructed==previous || obstructed==NONE))' (0x4ca4cb) and break; after the loop
  'if (flag) { add the step }' (0x4ca51d). RTC names the vector 'desired_direction' (ours 'direction').
correction: replace both gotos with the /Od flag: 'boolean add_step= TRUE;' (name inferred, disclosed), set FALSE
  + break at the mismatch, set FALSE at the dot/cross test, guard the obstructed update with 'add_step &&', and
  wrap the step creation in 'if (add_step)'. Keep everything else (incl. product order) unchanged.
prediction: EXACT via VC7 jump threading of the constant flag (the successor's first node is the flag compare);
  no residual flag register. Confidence low-moderate.
alternative: size/sha differ -> goto is load-bearing -> disclose / owner question; try at most 2 more shapes.
