SYN-342 documentation diagram evidence

Issue #347 fixes raw Mermaid code fences in published mdBook chapters. The source and tests freeze is 140b2b52640d29bbc774709adeba728cab5864e2, based on b868337. This report adds no product, version, tag, release or npm changes.

The actual plain mdBook build ran one targeted method and failed by a typed AssertionError: the release-pipeline diagram remained code.language-mermaid. The RED commit is 467f0eb. An initial post-fix test expected unhashed script names and failed. That fixture expectation was corrected to mdBook’s actual content-hashed filenames. Its failed report is retained, with no second product defect claim. The initial raw-fence rejection remains in the final test.

The complete relevant suite runs python3 scripts/check-docsite.py -v using verified official mdBook 0.5.4 and mdbook-mermaid 0.17.1 binaries. All 14 methods pass, with zero errors, skips or expected failures. The reviewed typed collector also records 14 passes. The CI command rejects empty, filtered, skipped and expected failure results. A separate generated build at the exact source freeze passes all 138 chapter, 56 tracked asset, search, ADR, privacy and editorial checks. It contains four diagram containers across three chapters, with the pinned local runtime before the pinned initializer. No runtime CDN is configured.

The suite exercises actual publication, source-byte preservation, per-chapter coverage, missing/changed assets, reversed load order, remote and escaping script references, raw fences, missing containers and nested fence examples. It also checks pinned archive verification precedes unpacking in the Pages workflow. These are builder-authored negative controls; independent mutation review is pending. No separate renderer or source Markdown copy is maintained.

The official plugin warns that it was built against mdBook 0.5.0 when invoked by 0.5.4. The generated build succeeds. Both use the 0.5 preprocessor API.

Browser acceptance remains pending. Structural HTML and pinned bytes do not prove that JavaScript renders SVG, that the console is clean, or that diagrams are legible in both themes and on nested pages. The earlier deployed HTML is a raw-source observation, not a browser-rendering assertion. No browser, Cargo, GUI, Swift, Xcode or publication action ran in this task.

evidence.json records exact identities, commands, counts and SHA-256 digests. Raw logs, downloaded tools and generated HTML remain private outside Git. The later browser check and independent adversarial report must be recorded separately before closing the issue.

Independent follow-up

The independent review retains eight original variants: five assertion kills, three survivors and no invalid attempts. Three additional coverage controls kill the original survivor patches unchanged. The restored combined suite passes 17 actual methods. This follow-up does not rewrite the original 14-method source freeze, chapter counts or then-pending gates above. Pages now invokes both suites; the final integration validation is recorded separately. Browser acceptance remains pending.

Actual browser follow-up

The browser receipt records actual SVG execution and visual review for all four diagrams. Local rendering exposed an unreadable horizontal knowledge flow. Vertical arrangement and wrapped labels preserve the same relations and improve the reviewed text scale; sequence labels and the publication topology were adjusted for the same book column. Earlier structural tests and mutation receipts retain their original scope. Hosted deployment and mobile layout are not established by this local review.

Actual hosted acceptance

Pages deployment 39101189584 succeeded at source aea21468b93e25e42551d97560085d4a4a2284cc. The public publication receipt identifies that same commit. Actual browser inspection found four rendered SVGs across the release, knowledge-framework and publication ADR pages, with zero raw Mermaid fences and zero renderer-error elements. Their node and edge counts, view boxes and effective label sizes match the reviewed local layout. Directed flow arrows and the dashed committed-transition return were visually checked at the desktop viewport.

The previous public release page had zero Mermaid SVGs and one raw fence. The allowlisted hosted.json receipt preserves both observations and private screenshot digests. This is desktop browser evidence, without a mobile, alternate theme or universal accessibility claim.