noteShareLine takes the first sentence of the raw thesis text. A thesis that starts with an x.com/twitter.com status citation (which parseReceipt recognises and noteColumn strips from the card) keeps that URL inside the sentence, because the dot in 'x.com' is not followed by whitespace.

The share text, which is what gets posted next to the writer's wallet, then leads with the cited account's URL rather than the thesis sentence; the card image and the feed deliberately separate citations from the author. Cosmetic/consistency only; nothing is signed or spent.

The brief asks for 'unclaimed · escrow N IMD' on a registered-but-unclaimed handle. The status line is rendered for every syntactically valid handle, including ones with no registerHandle event and no trades, so a visitor who mistypes a handle sees an 'unclaimed' escrow status for a subject that does not exist yet while the Register-handle button is still the only trade control.

The reads are view-only and the register/buy gates are unchanged, so this is wording, not a spending issue.

readPagesDirectory walks from block 26180753 to the live head in 2000-block chunks, issuing Trade and HandleRegistered getLogs per chunk sequentially, with no cap, no cache and no abort on route change. The window grows by about 3.6 chunks (7 RPC calls) per day, so the Pages tab gets slower every day on the public RPCs; refused ranges are disclosed as gaps as required. Behaviour matches the brief ('from deployment to a fixed head'); noted for the next continuation.

Carried over from site v3 and previously accepted: the four constants are the canonical mainnet USDC, WETH and v2/v3 factory addresses named by the brief, and the code comment states the factories and WETH are cross-checked against the router's UNIV3_FACTORY/UNIV2_FACTORY/WETH at runtime. USDC only feeds the informational dollar context and never enters a transaction. No action needed; recorded because the discovery rule says runtime addresses come from the manifest.

noteShareLine takes the first sentence of the raw thesis text. A thesis that opens with a status citation (which parseReceipt recognises and noteColumn strips from the card so the cited account is never shown as the author) keeps that URL inside the sentence because the dot in 'x.com' is not followed by whitespace. The share text posted next to the writer's wallet then leads with the cited account's URL instead of the thesis sentence.

Cosmetic and consistency only; nothing is signed or spent. Reproduced by bundling web/src/share.tsx with esbuild and calling noteShareLine directly; the shipped bundle dist/assets/index-Cpz-eHKw.js is byte-identical to a fresh build of this source.

The brief asks for 'unclaimed · escrow N IMD' on a registered-but-unclaimed handle. The status line is rendered for every syntactically valid handle, including one with no HandleRegistered event and no trades, even though s.registered is already read and used to show the Register-handle button. A visitor who mistypes a handle therefore sees an 'unclaimed' escrow status and 'The 90-day clock starts with the first page trade.' for a subject that does not exist.

Reads are view-only and the register/buy gates are unchanged, so this is wording, not spending. The browser fixture at web/tests/v6-browser.mjs line 362 opens /pages/new_writer with registered:false and only asserts the clock line, so the test does not catch it.

viem's isAddress runs in strict mode and treats any address with upper-case hex letters as checksummed. An all-uppercase 40-hex address (what some explorers and wallets copy) fails the EIP-55 check, falls through to the handle branch, fails the 15-character handle regex and produces the error 'Enter a full wallet address or an X handle of 1–15 letters, numbers or underscores.' even though the input is a complete, valid address.

All-lowercase and correctly checksummed inputs route correctly. Reproduced by calling pagesSearchRoute from an esbuild bundle of the source.

The brief asks for a pending state that polls until the payee is set or the deadline passes. The implementation puts Math.floor(now/15) in the read dependencies of the whole panel read, so subjects, claims, buyPrice, pendingBurn, registeredHandle, CLAIM_WINDOW, ANSWER_DEADLINE, margPriceInImd, pagesOf, eligible, balanceOf, allowance, claimMessage, intake, action, priceOf and a quote are re-read every 15 s on every author and handle page, including when no claim exists.

On the public RPCs this is a steady load per open tab and competes with the sequential directory scan. Behaviour is otherwise correct; noted for the next continuation.

readPagesDirectory walks from block 26180753 to the live head in 2000-block chunks, issuing Trade and HandleRegistered getLogs per chunk sequentially, with no cap, no cache and no abort on route change. The window grows by roughly 3.6 chunks (7 RPC calls) per day, so the Pages tab gets slower every day on the public RPCs; refused ranges are disclosed as gaps as required and the whole-window scan matches the brief ('from deployment to a fixed head').

Verified against the unit fixture: every chunk is read before any row appears. No action required by this brief; recorded for the next continuation.

Carried over from site v3 and previously accepted: the four constants are the canonical mainnet USDC, WETH and v2/v3 factory addresses named by the earlier brief, and the factories and WETH are cross-checked against the router's UNIV3_FACTORY/UNIV2_FACTORY/WETH at runtime. USDC only feeds the informational dollar context and never enters a transaction, approval or settlement.

Every spending target (router, Annex, Pages, hook stamp) comes from the manifest, and no other address outside the manifest appears in the bundle apart from well-known sentinels and test vectors. Not a hosting blocker; recorded because the discovery rule says runtime addresses come from the manifest.

Now: The first-sentence matcher requires whitespace immediately after punctuation, so a closing quotation mark makes it include the next sentence in thesis share text.

Change to: Recognize closing quotation marks after terminal punctuation when selecting the first sentence, and retain that closing mark without adding an extra full stop. Add a regression for quoted first sentences.

Why: Requirement 6 asks for only the first sentence of the thesis, up to 140 characters, followed by its status.