[GH-ISSUE #7517] [Docs] Archive historical verification and release inventories #4467

New issue

Closed

opened 2026-10-31 00:50:04 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 00:50:04 +00:00

Owner

Originally created by @gensokyo-dev on GitHub (Oct 27, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/7517

Before submitting

Searched existing issues and PRs for a related archival cleanup.
Excluded credentials and sensitive target data.

Documentation location

docs/releases/6.4.0–6.7.0.contributions.json and docs/verification/javascript-route-inventory-2026-10-21.{json,md} at main 65f1c447344a423fa2785847dbcea1e9a9e2454a.

Problem

The active documentation tree retains four older released contribution inventories that are identical to their published tag snapshots, plus a 2,681,223-byte historical route-inventory verification record containing 32 prior qualification entries. The raw route record's direct link is in its paired Markdown summary. These historical payloads total 5,438,839 bytes in the current working tree.

This is documentation/archive maintenance; no runtime defect or measured analysis slowdown is claimed.

Expected content

Keep the current 6.8.0 publication inventory and its generation/verification owners. Remove the older main-tree copies while preserving their published tag records and existing CHANGELOG links. Keep the route verification summary, replace its relative JSON link with the exact immutable archived source and SHA-256, then remove its main-tree JSON copy. Preserve original evidence and failed-attempt history through that archive; introduce no replacement data schema or archival framework.

Supporting evidence

Executed Git identity checks:

File/version	Bytes	Preserved snapshot
`6.4.0.contributions.json`	415,295	`rea-agents-6.4.0`
`6.5.0.contributions.json`	1,497,855	`rea-agents-6.5.0`
`6.6.0.contributions.json`	839,190	`rea-agents-6.6.0`
`6.7.0.contributions.json`	5,276	`rea-agents-6.7.0`
`javascript-route-inventory-2026-10-21.json`	2,681,223	`7d0efef62d56d0a10134bea62d709302daa1565f`

Remote release-tag refs match local objects; each tag inventory and main inventory have the exact same Git blob. The raw route record has SHA-256 9d7ea2582a6f33ff0741578aec9f01b9327b3256ce50c582437164868e544d51; the archived commit is confirmed reachable through GitHub's Git API and its blob equals main's.

contributionSummary already links release tags, and verifyNotesPublication reads the reviewed Git snapshot with git show. Consumer searches found no runtime reader of this route JSON; managed conformance outputs and other verifier fixtures are distinct and retained.

Additional context and validation

Follow-up to the repository review and merged #7515. Validate all archive identities, remaining links/current inventory, focused release-note/publication checks, generated docs and rendered documentation. Savings refer to the checked-out documentation tree; complete Git history and published records remain available. Real-provider testing is not applicable to this documentation-only cleanup.

Originally created by @gensokyo-dev on GitHub (Oct 27, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/7517 ### Before submitting - [x] Searched existing issues and PRs for a related archival cleanup. - [x] Excluded credentials and sensitive target data. ### Documentation location `docs/releases/6.4.0–6.7.0.contributions.json` and `docs/verification/javascript-route-inventory-2026-10-21.{json,md}` at main `65f1c447344a423fa2785847dbcea1e9a9e2454a`. ### Problem The active documentation tree retains four older released contribution inventories that are identical to their published tag snapshots, plus a 2,681,223-byte historical route-inventory verification record containing 32 prior qualification entries. The raw route record's direct link is in its paired Markdown summary. These historical payloads total 5,438,839 bytes in the current working tree. This is documentation/archive maintenance; no runtime defect or measured analysis slowdown is claimed. ### Expected content Keep the current 6.8.0 publication inventory and its generation/verification owners. Remove the older main-tree copies while preserving their published tag records and existing CHANGELOG links. Keep the route verification summary, replace its relative JSON link with the exact immutable archived source and SHA-256, then remove its main-tree JSON copy. Preserve original evidence and failed-attempt history through that archive; introduce no replacement data schema or archival framework. ### Supporting evidence Executed Git identity checks: | File/version | Bytes | Preserved snapshot | | --- | ---: | --- | | `6.4.0.contributions.json` | 415,295 | `rea-agents-6.4.0` | | `6.5.0.contributions.json` | 1,497,855 | `rea-agents-6.5.0` | | `6.6.0.contributions.json` | 839,190 | `rea-agents-6.6.0` | | `6.7.0.contributions.json` | 5,276 | `rea-agents-6.7.0` | | `javascript-route-inventory-2026-10-21.json` | 2,681,223 | `7d0efef62d56d0a10134bea62d709302daa1565f` | Remote release-tag refs match local objects; each tag inventory and main inventory have the exact same Git blob. The [raw route record](https://github.com/morluto/rea/blob/7d0efef62d56d0a10134bea62d709302daa1565f/docs/verification/javascript-route-inventory-2026-10-21.json) has SHA-256 `9d7ea2582a6f33ff0741578aec9f01b9327b3256ce50c582437164868e544d51`; the archived commit is confirmed reachable through GitHub's Git API and its blob equals main's. `contributionSummary` already links release tags, and `verifyNotesPublication` reads the reviewed Git snapshot with `git show`. Consumer searches found no runtime reader of this route JSON; managed conformance outputs and other verifier fixtures are distinct and retained. ### Additional context and validation Follow-up to the repository review and merged #7515. Validate all archive identities, remaining links/current inventory, focused release-note/publication checks, generated docs and rendered documentation. Savings refer to the checked-out documentation tree; complete Git history and published records remain available. Real-provider testing is not applicable to this documentation-only cleanup.

bsakaguchi

2026-10-31 00:50:04 +00:00