I've written the guide as artifacts/SEPOLIA-GUIDE.md, added a committed copy at docs/SEPOLIA-GUIDE.md, and added a live-deployment section to README.md. The commit failed because this machine has no git author identity configured. I didn't set one myself, so the four changed files are staged but not committed. artifacts/SEPOLIA-GUIDE.md is untracked, as required (.git/info/exclude ignores it).

On-chain checks: I checked the brief's facts on Sepolia today and they all match. The token is LOCK with 18 decimals and a supply of 10^27. The bank's token() is the LOCK address and maxLockSeconds() is 31,536,000. totalLocked() is 0, nextLockId() is 1, and lock(1) fails with UnknownLock(1). The deployment transaction is in block 11761675. The pool's setup event confirms native ETH / LOCK, fee 3000, tick spacing 60 and no hook. It also gave me two details the brief didn't have, which the guide includes: the pool ID and the factory address 0x770e…c9fd.

Walk-through check: I ran every cast command in the guide against a local test chain (anvil) with these contracts deployed, using a keystore account. Each misuse gave the documented error, and the guide shows real cast output.

Where the code differs from the brief (the guide has a section on this):

• deposit can also fail inside the token with ERC20InsufficientAllowance or ERC20InsufficientBalance. The brief's list of eight errors doesn't include these.
• withdraw checks who is calling before it checks whether the lock was already withdrawn. So a stranger trying to withdraw an already-withdrawn lock gets NotLockOwner, not AlreadyWithdrawn.
• extend checks MustExtend before the time checks.
• lock can only fail with UnknownLock, and locksOf never fails.
• One public Sepolia endpoint (publicnode) returned no logs for the deployment block, although the transaction receipt has nine. The guide warns that some endpoints return incomplete old logs, and says to cross-check with nextLockId() and totalLocked().

What else changed:

• README.md: a status note near the top (test network only, no monetary value, not audited, only mock is in test/mocks/). Then a live-deployment section with the address table and a read-only cast call that works from a fresh clone, linking to the guide.
• docs/ABI.md and docs/DEPLOYMENT.md: one-line pointers to the guide, because both were written before deployment and say there are no addresses.

Not claimed: the guide doesn't say whether the source is verified on Etherscan (I didn't check), and it doesn't describe how the reward MerkleDistributor works. That contract isn't in this repository, and both documents say so.