Skip to Content
TestingWalk-and-Fix preview

Walk-and-Fix preview

Walk-and-Fix turns autonomous-walker findings into owner-scoped FixIntent records so teams can triage, assign, and close defects through a stable API.

Planning surface only for current deployments: automatic patch generation is not implemented. run_fix_cycle proposes a plan but does not execute it. The only implemented apply adapter edits files inside a legacy local VM; that conflicts with the current immutable app deployment model and must not be used as a production repair path. GitHub PR and provider-redeploy modes are not implemented.

Supported workflow

  1. Run an autonomous walk.
  2. Review the finding and its evidence.
  3. Call propose_fix to create a traceable intent, or run_fix_cycle to create intents for a bounded set of blocker/major findings.
  4. Change the source repository through your normal review process.
  5. Build and deploy a new immutable variant.
  6. Re-run the walk and compare it with the prior walk.
  7. Call close_finding only after the new evidence demonstrates the finding is fixed, duplicated, not a bug, or intentionally not fixed.

This keeps source control, review history, and the deployed artifact aligned.

Tools and boundaries

ToolCurrent behavior
propose_fixCreates a FixIntent; does not generate code
run_fix_cycleCreates a bounded plan; does not apply changes
get_fix_intent / list_fix_intentsReads owned intent records
close_findingRecords a disposition for an owned finding
apply_fixLegacy local-VM full-file replacement; not an immutable-deploy workflow

apply_fix accepts full file contents, not a unified diff. It should be limited to disposable legacy tester deployments where the operator explicitly accepts that the change is outside source control and will be lost on redeploy.

Evidence required to close a finding

A successful build or deployment is not enough. Capture:

  • the source revision containing the change;
  • the replacement deployment ID and status;
  • a new passing scenario or walk that exercises the affected path; and
  • a diff showing the finding resolved without a new blocker or major regression.

If the test cannot reproduce the original path, leave the finding open or record the evidence limitation in its disposition.