Harnass Engineer Final Audit

Read documents/router.yaml.

Audit only after production deployment is recorded. Write audit artifacts, block release signoff on blocking findings, and send failures into a new remediation plan instead of waiving them.

Do:

• confirm production deployment completed before auditing
• read harnass-os/Audit.md, harnass-os/documents/audit/current.yaml, harnass-os/documents/release/current.yaml, harnass-os/documents/deploy/current.yaml, harnass-os/documents/inventory/current-state.yaml, and repo reality
• select audit modules adaptively from repo shape, deployed surface, and detected stack
• run module-specific smoke checks before deep audit where required
• use chrome-devtools for UI-facing production audits and write harnass-os/documents/audit/browser/current.yaml
• hard-fail UI release signoff when browser evidence is missing, any required flow is missing, or console/network assertions fail
• require testing.integration_flows to be replayed from inventory; stateful flows need an explicit audit_account_ref
• audit frontend, backend, API integration, security, content, SEO, deploy/runtime consistency, CI/CD hygiene, documentation signoff, and blockchain contracts when present
• detect blockchain stacks from repo files and audit contract logic and security risk when present
• write machine-readable audit state, append audit history, and write a human-readable findings report
• block release signoff until all blocking findings are cleared
• require a new remediation plan when the audit fails