fix(ci): repair MegaLinter full-repo scan failures on main

[ChipWolf]

What

Fixes the four blocking MegaLinter findings that fail the workflow on main. The push-event scan sets VALIDATE_ALL_CODEBASE, so it lints the whole repo, surfacing files that per-file PR scans never checked.

Linter	File	Fix
LUA_STYLUA	home/dot_config/nvim/scripts/headless-install.lua	Real finding — reformatted with stylua (single→double quotes, multiline callbacks)
TYPESCRIPT_STANDARD	skills/agent-audit/lib/opencode-plugin.ts	False positive — standalone skill resource outside tsconfig.json's include, so parserOptions.project can't parse it; excluded (same class as the already-excluded vendored rtk.ts)
JAVASCRIPT_STANDARD	skills/consensus/resources/consensus.workflow.js	False positive — Workflow-tool script body; the runtime wraps it in an async function, so top-level return/await is valid there but parses as 'return' outside of function under standardjs; excluded skills/*.workflow.js
YAML_V8R	home/dot_glzr/glazewm/config.yaml	False positive — SchemaStore matches **/glazewm/config.yaml to its GlazeWM v2 schema, but this config is v3 (restructured; no upstream v3 schema exists), so every v3 key reads as an unknown property; excluded

Why these exclusions are genuine false positives (not silencing)

Per repo policy, the one real finding (lua formatting) is fixed, not muted. The three exclusions each carry an inline comment naming the linter and reason, and were verified against evidence:

• Confirmed SchemaStore's glazewm.json is the v2 schema (top-level bar/workspaces, general.window_animations) and that glzr-io/glazewm ships no config-schema.json.
• The .workflow.js parse error is structural — top-level return/await cannot be made standardjs-valid without breaking the Workflow runtime.
• The skill .ts file is outside the maintained opencode-plugins TS project, mirroring the existing rtk.ts exclusion.

Reviewer notes

• Non-blocking warnings (461 markdownlint, prettier, shfmt, and the executable_skills-review "not executable" bash-exec hit) are unaffected — they don't fail CI and are out of scope here.

🤖 Generated with Claude Code