Assessment companion repair, v0.4.2
17 November 2026. Local repair; original Library preview unchanged.
Failure reproduced
In the current Library directory preview, Method & coverage → Open assessment companion navigated its preview frame to a sibling MapleJockey_Assessment.html URL. That file was absent from the single-file preview. The browser displayed “This content is blocked. Contact the site owner to fix the issue.” The pilot link had the same sibling-file dependency.
Source was downloaded from the existing Library project package, version v0.4.1, into the previously empty local MapleJockey workspace. Existing typography, colours, catalogue, assessment records and pilot logic were retained.
Repair
- Embedded both complete companion documents into the generated directory file and added Assessment and Pilot workspace navigation.
- Companion hash links remain within their srcdoc document. Browser testing caught and corrected the inherited-base-URL behaviour that would otherwise reload the parent file inside the companion.
- Companion frames remain mounted across navigation to preserve unsaved session edits. Navigation messages accept only the actual companion windows and the three supported destinations.
- Kept application network requests disabled. The parent permits only about: frames for the embedded documents; no hosted dependency or external API was introduced.
- When a preview denies browser storage, saving controls are disabled with a visible instruction to export JSON.
- Added a root build command to rebuild companions before embedding them.
Automated verification
| Check | Passed | Log |
|---|---|---|
| Assessment core | 10 | assessment-tests.txt |
| Directory, packaging and companion navigation harness | 65 | directory-tests.txt |
| Pilot event/rendering harness | 18 | pilot-tests.txt |
| Total | 93 |
The six new regression checks cover embedded assessment/pilot availability, frame retention, navigation source/route validation, srcdoc hash links, executable embedded scripts and network restrictions. Harness tests are separate from browser observations.
Browser observations
Tested through the permitted in-app browser at localhost, serving the generated HTML:
- Assessment loads with its existing records and controls.
- Claims and inventory navigation display the correct sections inside the assessment.
- Created a synthetic assessment, edited its name, added a service and saved the record.
- Navigated through the directory and returned; the same draft and service remained visible.
- Opened the pilot through the assessment link, then returned to the retained assessment.
- Saved the synthetic assessment in browser storage, reloaded the page, and restored the saved name and service with Load saved.
- Selected a synthetic JSON fixture through the native file chooser. Import succeeded and displayed the imported case name and provenance warning.
- Desktop layout visually inspected. Screenshot included in this folder.
Remaining limits
- The assessment JSON download was attempted but no resulting file was confirmed. Native download completion remains unverified; core JSON serialization/round-trip tests pass.
- The corrected file was not uploaded back to Library. No replacement tool or replacement menu action was available. The existing Library link still serves the previous file.
- Direct file-URL testing was denied by the browser URL policy; no workaround was attempted. Offline dependency checks pass, but native file opening was not browser-verified here.
- Mobile layout, a full keyboard audit, printing and final Library-hosted behaviour are unverified.
- This repair does not claim a live provider migration, production deployment or new assurance over historical assessment evidence.
Reproduce
From the package root:
node build.mjs
node --test maplejockey/tests/core.test.js
node expansion/ui/smoke-test.mjs
node pilot/ui/smoke-test.mjs
Open the generated root directory HTML in a permitted browser. For localhost testing, serve the package directory with an ordinary local static server. Use synthetic assessments, save/reload/load, switch workspaces, export/import and confirm download completion before treating those remaining gates as closed.