chore: contributor growth funnel (templates, CTAs, #504 build)

[cobusgreyling]

Summary

Make it easier to star → try → contribute and stop first-time build pain on loop-audit.

Changes

• Issue templates → YAML forms; share-story.yml (was .md, broken form link); security contact on this repo
• PR template → npm monorepo paths + 48h review SLA
• README → hero CTAs (Quickstart / Contribute / Star) + soft star line + SLA
• CONTRIBUTING → 48h first-response promise
• [bug] loop-audit fails to build after readiness-core extraction (43 TS errors) #504 fix: loop-audit / goal-audit prebuild builds file:../readiness-core so cd tools/loop-audit && npm run build works without a manual sibling build

Already done on main (same sprint)

• Merged green community PRs test(loop-sync): add CRLF frontmatter regression tests #496–docs(hermes): add CI Sweeper example #500
• Closed duplicate PRs Add CRLF frontmatter regression tests for loop-sync #489–Add invalid-JSON test for append-run-log #491 with thanks
• Assigned/replied on [bug] loop-audit fails to build after readiness-core extraction (43 TS errors) #504 for @AbarnaaSree

Test plan

• cd tools/loop-audit && rm -rf node_modules dist && npm i && npm test (26 pass)
• CI green on this PR

[github-actions]

Loop Readiness Audit

Score: 100/100 (L3)

Strong loop readiness — good candidate for L3 with explicit gates.

Top suggestions

• Loop Ready 80+: version this loop for a fleet — npx @cobusgreyling/loop-init . --with-fleet
• Loop Ready 80+: version this loop's memory — npx @cobusgreyling/loop-init . --with-memory
• Loop Ready 80+: version this loop as a harness — npx @cobusgreyling/loop-init . --with-foundry · showcase https://github.com/cobusgreyling/harness-foundry/blob/main/docs/showcase.md
• Scaffold a harness: npx @cobusgreyling/loop-init . --with-foundry (or npx @cobusgreyling/harness-foundry init --from loop-engineering:daily-triage)
• Scaffold memory tiers: npx @cobusgreyling/loop-init . --with-memory

_{Posted by audit.yml · loop-audit docs}