Skip to content

Release 0.6.13 monitoring freshness and frozen chronology - #11

Merged
sunlover7 merged 2 commits into
mainfrom
codex/monitoring-package-0613-20261007
Oct 8, 2026
Merged

sunlover7 merged 2 commits into
mainfrom
codex/monitoring-package-0613-20261007

Conversation

@sunlover7

Copy link
Copy Markdown
Owner

An unchanged successful source check now updates the activity dates shown by status, fleet and reports. A later unknown check preserves the prior conclusive/link verification only for the same placement identity. Adds chronology pull for compatible hosted versions and chronology export for saved pages, with explicit denied origins, history gaps, partial paging, exact identity and refusal to replace an input or existing output. Existing frozen version-two reports remain intact. The generated catalog, plugin manifests and REST/MCP client identity move to 0.6.13.

Validation and custody:

  • The 29 committed changes match the canonical product package; all 345 reviewed canonical payload bodies match. Existing workflow bodies, vendor/browser payloads and unrelated ignored files were preserved.
  • The qualified private 0.6.13 archive contains 213 members, is 526,151 bytes and has SHA256 0b770b46bf676c77e7e79ff1cce43de60c3547b2d12978a3c4da2a91804ca198. This is a prepared archive, not npm publication or a fresh customer installation.
  • Canonical monitoring qualification records 232/232 affected tests plus passing interfaces and final generated-reference text scans. This PR's full Ubuntu/Node 22 and 24 tests and packed-CLI checks must supply their own cloud results.

0.6.13 remains unreleased. The latest recorded npm readback is 0.6.11; hosted command availability and consumer adoption are separate receipts. The retained release workflow stays disabled with if: ${{ false }} so this PR/tag cannot publish a second artifact. No supplier activation, recurring collection or message delivery is introduced by this package release.

@sunlover7
sunlover7 merged commit 724b101 into main Oct 8, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant