Refactor (packages/opencode/src/tool/edit.ts:69): Function with high complexity (count = 34): execute

[cmu-ccao2]

P1B: Starter Task: Refactoring PR

Use this pull request template to briefly answer the questions below in one to two sentences each.
Feel free to delete this text at the top after filling out the template.

1. Issue

Link to the associated GitHub issue:
#150

Full path to the refactored file:
packages/opencode/src/tool/edit.ts

What do you think this file does?
(Your answer does not have to be 100% correct; give a reasonable, evidence‑based guess.)
I think the file handle opencode editing and creating new files based on the execute() function I worked on.

What is the scope of your refactoring within that file?
(Name specific functions/blocks/regions touched.)
Refactored execute() by adding 3 closures and a helper function in place of a single function with many and potentially complicated pathing.

Which Qlty‑reported issue did you address?
(Name the rule/metric and include the BEFORE value; e.g., “Cognitive Complexity 18 in render()”.)
Function with high complexity (count = 34): execute in edit.ts

2. Refactoring

How did the specific issue you chose impact the codebase’s maintainability?
I think the function was just very long and complicated and doing a lot. If something where to go wrong involving the function, it may take a long time of code tracing to see which path the issue took and how it failed to do the correct thing.

What changes did you make to resolve the issue?
Broke it up into smaller pieces / closures / help functions.

How do your changes improve maintainability? Did you consider alternatives?
When code tracing bugs, I think it will be easier because you will know which function it failed in and be able to start debugging from there and not have to be distracted by code that the bug did not encounter. I did not consider alternatives, in large part because I don't know what other options there are to making it less complex of a function than to just break it up into pieces.

3. Validation

How did you validate that the change is correct?
Passed bun lint and bun test on the existing test cases and a newly made test suite for execute() specifically.

Attach a screenshot of the test coverage showing the lines were executed by the tests.

^ bun test against all of packages/opencode

^ bun lint against the entire codebase (the gradescope requirement feels like it implies it needs the previous 2 images, but im not sure why)

it is a pretty big file, so execute() makes up a small portion of it My changes are only made in the first 220 lines of the file, and all of those lines are covered.

Attach a screenshot showing the tests that cover the change passing during CI

Attach a screenshot of qlty smells --no-snippets <full/path/to/file.ts> showing fewer reported issues after the changes.
before:

after:

Function with high complexity (count = 34): execute is gone