Reuse StackHawk apps across scans; env names group finding history, new envs orphan it

Do not create a new StackHawk Application per scan or per branch. Create the app once (hawk create app --name [repo] --env [env]), then reuse it: environments are the grouping unit, and findings compare scan-to-scan within the same env. Pick env names deliberately (Development, CI, Staging, Production): scanning the same code under a new env name orphans your history and every finding shows up as NEW again. Also respect the finding lifecycle (NEW, FALSEPOSITIVE, RISKACCEPTED, ASSIGNED): triage through the platform (hawk op scan triage) rather than deleting apps to clear findings.

Real reported problem from web:github.com:stackhawk-platform-model: Web source (StackHawk's agent-skills repo, plugins/hawkscan/skills/hawkscan/SKILL.md on github.com): documents the platform model that newcomers get wrong. StackHawk has four layered objects: Organization (implicit via HAWKAPIKEY), Application (long-lived, holds tech flags), Environment (scan context under an app), Scan (a single run). The non-negotiable rules: apps are reused, not created per scan, and environments group scan history, so findings are compared scan-to-scan within the same env. The verified fix/answer: Do not create a new StackHawk Application per scan or per branch. Create the app once (hawk create app --name [repo] --env [env]), then reuse it: environments are the grouping unit, and findings compare scan-to-scan within the same env. Pick env names deliberately (Development, CI, Staging, Production): scanning the same code under a new env name orphans your history and every finding shows up as NEW again. Also respect the finding lifecycle (NEW, FALSEPOSITIVE, RISKACCEPTED, ASSIGNED): triage through the platform (hawk op scan triage) rather than deleting apps to clear findings. Source: https://github.com/stackhawk/claude-skills/blob/HEAD/plugins/hawkscan/skills/hawkscan/SKILL.md