Add audit documentation and CI lint workflow

[danielpmadden]

Summary

• refresh the README to match the current PowerShell script capabilities and point to new dependency documentation
• add ROADMAP and CHANGELOG files plus a tests directory placeholder to guide future contributions
• create a lint-focused GitHub Actions workflow and repository .gitignore for generated artifacts

Testing

• not run (documentation and automation scaffolding only)

---

https://chatgpt.com/codex/tasks/task_e_68f356d6591c8332b97934887f4212e6

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Fail lint job when ScriptAnalyzer reports violations

The lint workflow captures Invoke-ScriptAnalyzer output and prints it, but the step never sets a failing exit code when $results contains findings. As written, pull requests with lint errors will still pass CI because the job always exits successfully after the Write-Host calls. Consider returning a non‑zero exit (e.g., if ($results) { $results | Format-Table; exit 1 }) so lint violations actually block merges.

Useful? React with 👍 / 👎.