Harden Windows CI, security scanning, and local usage evidence

[thangldw]

Outcome

• Adds a checkout-free Windows smoke job for the published ragops==2.0.1 demo and evidence verification.
• Adds least-privilege, commit-pinned Python CodeQL analysis.
• Adds disabled-by-default local CLI usage JSONL plus usage-report; no arguments, paths, identifiers, or network transmission.
• Documents the boundary between local product-operation counts and consent-aware production pilot evidence.

Contract

• Required runtime dependencies remain empty and the core performs no network calls.
• Existing CLI commands and exit codes remain compatible; the console entrypoint now wraps main() only to append an explicitly enabled local event.
• No package version, PyPI release, or ChatGPT plugin submission is created.

Evidence

• ruff check passes for all tracked Python files.
• PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 pytest -q: 307 passed.
• Credential-free demo returns BLOCK and its evidence bundle verifies.
• Wheel builds; clean --no-deps core import and separate api extra import pass.
• Workflow YAML parses and all action references are immutable commit pins.

Closes #24

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.