[viktar-b]

Summary

The installed initializer acceptance covered existing example references but did not prove the shipped figure/reference authoring recipe. Extend its packaged composed-report recipe through complete reference and live-report qualification.

fresh installed scaffold + packaged composition/figure recipe
  independently established intermediate/output expectations
    matching pass / wrong matching failure / unmatched pending
    formula + text-only edits invalidate matching
      explicit reviewed rebinding preserves expectations
        browser edits + output-only curl
          same-run HTML, PDF, reference and evidence hashes

Closes #70. Changes are confined to integration acceptance and its guide. Generated/package docs and calculation behavior are unchanged.

Evidence

• Before: the packaged recipe stopped at checked HTML without a bound reference or live report; maintained two-panel sources supplied the existing reference workflow.
• After: full external installed-consumer acceptance passes, including 16 CLI reference scenarios, complete two-symbol coverage, expected failure on wrong values, source-edit invalidation/rebinding, matching and unmatched browser states, output-only curl, and same-run HTML/PDF/evidence checks. Browser downloads match the captured PDF hash.
• Both new acceptance PDFs are one A4 page and were visually inspected on every page. No clipping, missing steps or unreadable notation found. Source consistency, independent agreement, automated retention/rendering, visual review and engineering approval remain distinct.
• The separate documentation-only triangle trial passed 18 CLI scenarios, complete three-symbol references for symmetric/asymmetric cases, browser/curl and exact same-run artifact assertions. Both one-page PDFs and HTML reports were visually reviewed. The issue comment retains full provenance, commands, expected values and artifact hashes. Engineering approval is NOT SUPPLIED.
• Local root typechecking, workspace lint and CI recipe checks pass. Lint retains existing warnings. The first acceptance attempt used a report source outside the documented calculations/ registry root; the synthetic test location was corrected and the full run passes.

Automated evidence keeps visual inspection pending; separate hash-bound review records contain the completed agent visual review. Test artifacts from other acceptance cases keep their existing review status. Registry publication was not performed.

Merge Danger

Door: two-way

Blast Radius: tests

Adds acceptance time and artifacts. The command runner can assert an expected nonzero exit for the deliberately wrong reference. No production dependency or runtime change.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
calculation-source-object	Ready	Preview	Nov 6, 2026 9:12am UTC