licensing.py: forgery-hammer message claims 'Incident has been flagged' but nothing is logged anywhere #486

Summary

The forgery-hammer message in enforce_licensing_guard() (gitgalaxy/licensing.py) says:

Incident has been flagged. Executing under maximum compliance friction.

There's no log write, no local file, no telemetry call anywhere in this function -- nothing persists anywhere. Given this project's Zero-Trust/no-data-transmission design elsewhere, that's consistent with intent (nothing should phone home), but the message actively claims something happened that didn't.

Impact

This is a "says one thing, does another" bug, not just a design tradeoff. A user hitting this path (e.g. a fat-fingered key, see #4-style issue) is told an incident was "flagged" somewhere, which isn't true and could be misleading about what data this tool does or doesn't collect/transmit.

Reproduction

1. Trigger the forgery-hammer branch in enforce_licensing_guard() (a key that parses correctly but fails RSA signature verification).
2. Read the printed message: "Incident has been flagged."
3. Observe: no file write, no log line, no network call anywhere in the function.

Suggested fix

Soften the copy to not claim persistence that doesn't happen -- e.g. state plainly that the check runs entirely offline and nothing is logged or transmitted, since that's the actual (and, per the project's design elsewhere, intentional) behavior.

Status

Fixed in #483 (bundled with the related malformed/forged key distinction). Filing for tracking since this was found during a manual review rather than starting from a filed issue.