Implemented the child-call flow, parent validation, thesis follow-up links and feed reminders. Rebuilt dist/ and updated documentation.

Build, typecheck, hashes and 21 child-call scenarios passed in both Chromium and WebKit. Submission fits under 8 MiB.

Additional live checks encountered RPC 429/empty responses; no transactions were sent. No commit was created because .git/ writes are forbidden.

Saved one finding in .imd-findings.json.

Medium — bug: thesis completion leaves the child-call handoff above the viewport. After posting at 390×844, the visible confirmation omits the next action; its link sits over 1,400px above the viewport in Chromium and WebKit. Move the existing dated link from Post.tsx:194 into the confirmation below the submit button so authors see their required next step.

All 21 browser scenarios passed in WebKit. Chromium passed 20 initially; the polling-sensitive remaining scenario passed on rerun. Unit tests, live parent reads, 15 asset hashes and three deployment ABI hashes passed. No real transactions were sent.

The brief’s “same … caveat” requirement overrides the probe’s repetition and copy-budget flags.

Marginalia presents trades and bonded calls through a paper ledger with rust-colored primary actions. The site files remain unchanged.

The review is complete. The findings file is written and no repository file was changed.

Outcome: nothing blocks hosting. The v3.1 child-call work contains no critical or high content. I found one medium behavioural defect, one low copy defect and one informational gap, all recorded in .imd-findings.json.

What I verified

• Every hosted file was read: dist/index.html, both bundled scripts and the stylesheet, the ABIs, agents.md, llms.txt, the manifest and the full source they come from.
• The shipped dist/ is a byte-identical rebuild of web/src with the unchanged lockfile, and the regenerated manifest matches the shipped one. The project's manifest check passes.
• Approvals are unchanged: exact amounts to the hook's router or the Annex only. No external script loads, no hidden frames, no new outbound hosts. The only external links are the pre-existing Radar, explorer and X intent links.
• The three chain gates match MarginaliaHook: parent must exist, be ThesisOpen, belong to the posting wallet, and be inside the inclusive seven-day grace. Deadlines are capped at grace end.
• The project's unit suites pass. Its 21-scenario child-call browser suite passes against the export in a headless Chromium I set up under /tmp.

Findings

• Medium, web/src/trade.tsx:41. The trade box writes the child-link parent into the saved draft. On any later plain visit to #/ the thesis is prefilled and the next "Trade and post" is sent as another child; after the grace passes, the restored parent disables the primary action until cleared by hand. Reproduced in the real export: the sent tradeAndNote carried the thesis as parentId, and the expired case showed the deadline error with the button disabled.
• Low, web/src/pages/Feed.tsx:45. The feed still prints "needs its child call" for a thesis whose grace has expired, while the note page for the same thesis offers "Forfeit thesis". Reproduced in the export.
• Info, AGENTS.md:48. The served agent document does not mention the new child route or the own-thesis parent field, though the README does.

The review is complete. No repository file was changed; the only new file is .imd-findings.json at the root, which holds five substantiated findings.

What I checked. I read the v3.1 diff against the hook source for the child-call rule, ran the project's unit test and its 21-scenario Chromium browser suite against the built export (all pass as claimed), then wrote my own scenarios on that harness, outside the repository, to reproduce each candidate. Parent validation itself is correct: the three gates, the inclusive grace boundary, fixed-block reads, the fresh preflight before approve and post, and the deadline cap at grace end all match the contract's checks at src/MarginaliaHook.sol:478. Counter rules, the Annex exclusion and seal reveals are untouched.

Findings, most severe first.

• Medium, saved trade draft keeps the thesis parent. Opening the child link writes parentId into the persisted draft and nothing clears it. Every later plain home visit is still a child call. After the grace passes the home composer's primary button is disabled until the hidden parent field is cleared by hand. Reproduced end to end, including a tradeAndNote request carrying the thesis id from a plain home visit.
• Low, the thesis page CTA blinks and can vanish silently. The button is gated on a loading flag that flips true during every 15-second poll, so it unmounts for one RPC round trip each time. A transient 429 on the fixed-block read hides it with no message and no retry on that page.
• Low, the child link discards an in-progress trade draft. The stored draft is replaced by the empty child draft on mount, so a half-written reason is lost.
• Low, feed card still says "needs its child call" after the grace. Confirmed from the specialist report. The brief's literal wording is satisfied, so this is a copy accuracy issue.
• Info, served agents.md omits the child routes and parent field. Confirmed from the specialist report.

The specialist's trade-draft and feed-label findings reproduced and are kept, the first merged with my own extended reproduction. None of the findings is in Solidity, so no Foundry proof applies. Nothing I examined warrants a high rating.