docs: record 7.0.8 publication and per-host installed checks - #224
Conversation
Adds the v7.0.8 current-snapshot section to status-and-evidence.md (published assets, byte-identical local rebuild, staged Phase B' matrix qualification, per-host post-install canaries, fresh project-estimation maintenance receipt), renames v7.0.7 to historical, and updates the root README plus six architecture pages (README, capabilities-and-workflows, claude-participation, lifecycle-and-operations, project-estimation, repository-and-release) to describe the current 7.0.8/5.0.9 generation. Records a new positive Claude context.documents.intent qualification from staged live qualification (a genuine live canary with selected_agent=claude and a fixture-marker-correct answer), superseding the 7.0.7 cycle's explicit-exception framing while retaining the sole-admitted-action boundary. The immutable plugins/agent-collab/README.md package snapshot is deliberately left untouched, per its own documented 'immutable release-time snapshot' contract. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 65bd8e26cf
ℹ️ 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".
| | --- | --- | | ||
| | `agent-collab.v7.0.8.plugin` | `6590230d69218a6a537988db520af905684cc14b4fd64c0a44e16bbf965fd4b3` | | ||
| | `agent-collab-v7.0.8.spdx.json` | `7d8cc8797459d441be159248dde16ca06c8b596455299c0a68c635611e6b810b` | | ||
| | `agent-collab.v7.0.8.plugin.sha256` | (contains the archive digest above) | |
There was a problem hiding this comment.
Record the sidecar asset's SHA-256
The table promises a verified SHA-256 for each published asset, but this cell describes the checksum file's contents rather than recording the SHA-256 of agent-collab.v7.0.8.plugin.sha256. This prevents an auditor from comparing the downloaded sidecar itself with the closeout evidence—unlike every preceding snapshot, which records all three asset digests—so replace the parenthetical with the verified digest or relabel the table to distinguish content from asset hashes.
AGENTS.md reference: AGENTS.md:L44-L48
Useful? React with 👍 / 👎.
…aude evidence (#225) Follow-up to PR #224. A downstream review of the workspace companion (#3190) correctly flagged that the retried Claude/Grok installed canaries were described as 'confirming' or resolving the earlier silent-timeout attempts, which the runtime's own no-replay contract does not support ('a new request ID alone does not make repeating consumed work permissible'). Also ran and recorded a genuine, clean, explicitly-targeted (explicit_target: claude) installed context.documents.intent canary, replacing the prior 'staged qualification stands in for installed' framing with actual installed-unit evidence (selected_logical_agent: claude, native_model_identity.model: claude-opus-5-5, execution_status: ok, confirmed cleanup). Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
Summary
Public documentation closeout for the v7.0.8 release, per
the release runbook's Phase F.
Documentation-only; no
plugins/bytes change.Changes
docs/architecture/status-and-evidence.md: new "Current snapshot — v7.0.8" section (published assets, byte-identical local rebuild verification, staged Phase B' full-matrix qualification, per-host post-install canaries including a genuine live Claude canary, fresh project-estimation maintenance receipt); renames v7.0.7 to historical.README.md: bumps "Current published release" and the closeout cross-reference to v7.0.8.docs/architecture/README.md,capabilities-and-workflows.md,claude-participation.md,lifecycle-and-operations.md,project-estimation.md,repository-and-release.md: bump current-release mentions;claude-participation.mdadditionally records the new positive Claudecontext.documents.intentqualification.plugins/agent-collab/README.mdis deliberately not touched — it is the immutable release-time snapshot per its own documented contract.Verification
python3 -m unittest discover -s tests -t . -v— 275 tests, OKpython3 scripts/check_release_consistency.py— OKpython3 scripts/check-public-export-safety.py --active-tree— SAFEpython3 scripts/secret_scan.py— cleanpython3 scripts/build-changelog.py --dry-run— OKgit diff --check— cleanCompliance trace
author: claude
standing_directives: docs/provider-runtime-release-runbook.md Phase F; docs/public-governance.md Tier 1; CLAUDE.md "Final release documentation closeout"
tier: 1
cross_check: N/A -- documentation-only, no executable, policy, security, or packaging effect; every stated fact is bound to already-published evidence (tag, release, byte-comparison, staged/installed qualification results)
post_condition: fetch and positively read back main after merge; the workspace companion records this PR's exact merge commit before it merges
mcp_coverage_gap: NONE
contributor_rights: OWNER-AUTHORED
operator_reserved: no
🤖 Generated with Claude Code