Integrate Godaudits 2.0 canonical state

[hannsxpeter]

Summary

• consume canonical .godaudits/AUDIT.json with generated MDX and legacy Markdown fallbacks
• preserve Godaudits 2.0 checks, evidence metadata, findings, risks, scores, coverage, and typed remediation tasks
• synchronize open GA tasks into an idempotent managed Godpowers todo section
• fail closed on malformed or unsafe inputs, avoid symlink traversal, and make staleness follow canonical JSON
• update skills, routes, workflows, agents, templates, architecture, migration guidance, and release notes

Verification

• npm run release:check
• node scripts/test-sibling-artifacts.js (49 passed)
• live Godaudits 2.0 compiler and renderer compatibility probe
• git diff --check

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 37289f5951

ℹ️ 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]

Rehash the active godaudits source for staleness

When a project imported a legacy .godaudits/AUDIT.mdx (so state.json records that path in source-systems[].files) and later receives canonical .godaudits/AUDIT.json, this code reports the active path as JSON but still hashes the old recorded MDX file because entry.files wins. As a result state.detectDrift and /god-status do not flag the new canonical audit as stale, so /god-migrate is not prompted and the harden seed plus managed GA todos can remain based on the old audit.

Useful? React with 👍 / 👎.