chore(loop-init): bump @cobusgreyling/loop-audit from 1.7.0 to 1.9.0 in /tools/loop-init

[dependabot]

Bumps @cobusgreyling/loop-audit from 1.7.0 to 1.9.0.

Changelog

Sourced from @​cobusgreyling/loop-audit's changelog.

[1.9.0] - 2026-08-28

Changed

• Loop activity requires a fresh Last run (≤14 days), a dated loop-run-log.md row, or a git commit that actually touches state / run-log files
• LOOP.md cadence text and a triage commit on README no longer count as activity
• Activity is worth 14 points (was 6)
• Missing STATE.md is a warning, not a fail, when .github/workflows/thin-loop.yml is present
• Companion funnels are not pushed to the top of --suggest

[1.8.0] - 2026-07-29

Added

• --auto-fix self-heal for missing repository structure (STATE, LOOP, budgets, gate.yaml, etc.)
• Memory-engineering readiness signals and --with-memory recommendations

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​cobusgreyling/loop-audit since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

This PR changes paths that must run the real validate and audit workflows (tools, patterns, scripts, or CI).

Fork PRs from first-time contributors start with those workflows waiting for approval. A maintainer needs to open the Checks tab and click Approve and run workflows. Until that happens, branch protection will show the PR as blocked even after a review.

Content-only PRs (docs/, examples/, stories/, skills/, root markdown) skip this step — required checks are posted from this workflow instead.

— loop-engineering fork-pr-gate

[github-actions]

Loop Readiness Audit

Score: 100/100 (L3)

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

Top suggestions

• Run the loop and commit changelog-drafter-state.md (or append loop-run-log.md) so Loop Ready can see a fresh timestamp
• 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
• Scaffold a fleet: npx @cobusgreyling/loop-init . --with-fleet

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