Files
prometeu-studio/discussion/lessons/DSC-0095-canonical-documentation-migration/evidence

Canonical documentation migration evidence

Owner: compiler/general. Discussion: DSC-0095; accepted decision DEC-0082; implementation plan PLN-0160. Recorded on 2026-10-28, macOS ARM64.

Commands and results

  • ./gradlew test :prometeu-app:installedKnowledgeTest --console=plain passed against the final corpus. The normal suite reports 1,099 cases, zero failures and errors, and 13 skipped. The installed suite reports two passing tests.
  • python3 tools/documentation/verify.py --runtime ../runtime checks local paths, encoded spaces and anchors, and provider-context mirror links. Final navigation output is retained in navigation.log.
  • git diff --check and discussion validate pass; the workflow is finalized through CLI housekeeping rather than manual index edits.
  • The installed probe runs the real JAR distribution outside the checkout. All 12 old filename IDs share canonical resources/hashes with numbered IDs. Existing SDK and example reads, example compilation and packaged LSP checks also pass.

Retained artifacts

  • regression.log.gz: final Gradle command output.
  • results.json: baseline revision, platform, normal/installed suite counts, installed JAR fingerprint and packaged-corpus results.
  • content-verification.json: exact 14-file source/destination map, original and final source hashes, body-preservation results and 65 unchanged evidence/mirror fingerprints. Body normalization excludes changed Markdown link destinations, status/owner/scope metadata, the added authority section and whitespace.
  • installed-reference-index.json: actual index extracted from the final installed PBS JAR. There are 79 references, 12 aliases and 28 distinct specification resources.
  • navigation.log: final documentation navigation verification.
  • SHA256SUMS: fingerprints of these evidence files.

All 28 packaged specification resources were also compared byte-for-byte with their final checked-in source paths. Old unnumbered spec resources are absent. Historical evidence/mirrors were not rewritten. The sibling runtime was used only to resolve provider-reference targets and anchors; no files or commits were written there. These checks do not claim new runtime/platform qualification.