chore(main): release 1.7.0

[agents-workflows-bot]

Source: Issue #2367

Closes #2367

Automated Status Summary

Scope

Doc-rot was the audit's most pervasive defect class (most of §1/§4 findings were stale docs). maint-66's monthly audit only carries a static "update docs" checklist; nothing systematically detects drift. This closes that gap on a monthly cadence.

Tasks

• Post-2026-06-15, inline Claude Code Actions bill against the metered Agent-SDK credit (overflow is set to degrade-to-Codex); the lane fleet is cost-managed + Sonnet-pinned.
• The picked-up agent diffs with full repo context and reuses proven plumbing (no fragile new action wiring).

Acceptance criteria

• Registered in EXPECTED_NAMES + both inventory docs; tests/workflows/ green (24 passed).
• zizmor-clean (dogfooded), persist-credentials: false, scoped issues: write.
• Deduped: one open [Docs Drift Audit] issue at a time.

Head SHA: 77680d1
Latest Runs: ✅ success — Gate
Required: gate: ✅ success

Workflow / Job	Result	Logs
Agents Auto-Pilot	✅ success	View run
Agents Bot Comment Handler	✅ success	View run
Agents Keepalive Loop	✅ success	View run
Agents Verifier	✅ success	View run
Auto-label dependency PRs	⏭️ skipped	View run
CI Autofix Loop	✅ success	View run
Create Issue from Verification (Enhanced)	⏭️ skipped	View run
Create New PR from Verification	⏭️ skipped	View run
Gate	✅ success	View run
Health 40 Sweep	❔ startup failure	View run
Health 44 Gate Branch Protection	✅ success	View run
Health 45 Agents Guard	✅ success	View run
Health 50 Security Scan	✅ success	View run
Health 52 Semgrep Scan	✅ success	View run
Maint 52 Validate Workflows	✅ success	View run
PR 11 - Minimal invariant CI	✅ success	View run
Selftest CI	✅ success	View run

[stranske-keepalive]

Automated Status Summary

Head SHA: e66841b
Latest Runs: ⏳ pending — Gate
Required contexts: Gate / gate, Health 45 Agents Guard / guard
Required: core tests (3.12): ⏳ pending, core tests (3.13): ⏳ pending, docker smoke: ⏳ pending, gate: ⏳ pending

Workflow / Job	Result	Logs
(no jobs reported)	⏳ pending	—

Coverage Overview

• Coverage history entries: 0

Updated automatically; will refresh on subsequent CI/Docker completions.

---

Keepalive checklist

Scope

Doc-rot was the audit's most pervasive defect class (most of §1/§4 findings were stale docs). maint-66's monthly audit only carries a static "update docs" checklist; nothing systematically detects drift. This closes that gap on a monthly cadence.

Tasks

• Post-2026-06-15, inline Claude Code Actions bill against the metered Agent-SDK credit (overflow is set to degrade-to-Codex); the lane fleet is cost-managed + Sonnet-pinned.
• The picked-up agent diffs with full repo context and reuses proven plumbing (no fragile new action wiring).

Acceptance criteria

• Registered in EXPECTED_NAMES + both inventory docs; tests/workflows/ green (24 passed).
• zizmor-clean (dogfooded), persist-credentials: false, scoped issues: write.
• Deduped: one open [Docs Drift Audit] issue at a time.

[github-actions]

Runner dispatch state for codex on PR #2444. Do not edit.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 77680d1755

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Remove duplicated 1.6.0 entries from 1.7.0

This 1.7.0 changelog section repeats entries that are already in the existing 1.6.0 section below; for example, this e43b361 feature is an ancestor of the parent release commit, and git log 2a4770^..2a4770 contains only this release commit. If merged as-is, the v1.7.0 release notes will claim previously shipped changes were released again, making the version history and GitHub release audit trail misleading.

Useful? React with 👍 / 👎.