[Repo Assist] refactor: remove unintended this.standard mutation in getArgs()

[github-actions]

🤖 This is an automated pull request from Repo Assist.

Problem

getArgs() contained an unintentional side effect: it called this.getStandard(document) and stored the result back into this.standard as a by-product of building the argument list.

// Before
getArgs(document, tmpFileName) {
    ...
    this.standard = this.getStandard(document);   // ← side effect
    if (this.standard) {
        args.push("--standard=" + this.standard);
    }
    ...
}

This is problematic because:

• getArgs() reads like a pure builder (returns an array of CLI arguments) but silently mutates instance state.
• this.standard is loaded by loadSettings() and read by getStandard(); having getArgs() overwrite it mid-flight makes the data flow harder to follow.
• If call order ever changes (e.g., multi-format parallelism), the mutation could corrupt state between calls.

In practice the bug was harmless — loadSettings() is called before every format() invocation — but the pattern is misleading.

Fix

Use a local const so getArgs() computes the standard for the argument list without touching this.standard:

// After
const standard = this.getStandard(document);
if (standard) {
    args.push("--standard=" + standard);
}

this.standard is now exclusively managed by loadSettings().

Test Status

✅ node --check extension.js — no syntax errors
✅ npm run test:unit — 7/7 tests pass

Generated by Repo Assist

Generated by Repo Assist · ◷

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@346204513ecfa08b81566450d7d599556807389f