Notes: bring state-of-play back to current, and fix what aged

[mgravell]

Notes only - no product or test changes.

state-of-play.md

This is the "read first after a break" page, and it was the most wrong thing in the repo: still listing #206/#207/#208 as in flight with a landing order to follow, and unaware of #209-#216. Rewritten to say what is true - nothing of ours is in flight, and the four open PRs (#167, #153, #151, #84) are all external and all awaiting a decision only you can give.

It also rescues content that existed nowhere in main. The account of why #206 was closed was sitting on the typehandler-registration-note branch in a commit pushed after that PR merged, so it never landed: gating stopped the bridge emitting anything for consumers who did not opt in, but the read-side check still sat in RowFactory.GetValue<T> - the type-flexible arm of every mapped member, ~130 call sites across the goldens - so everyone paid for a feature almost nobody would enable. The emission-time fix that was considered and rejected is recorded alongside it, being the part most likely to get re-proposed.

Two things promoted out of the small print, because they gate real work:

• the behavioural harness does not exist on this machine. aot-harness was deliberately local-only and lived on the Windows box; ../Dapper here is clean main, there is no DapperAotEnable.cs, no SQL Server running, and the repack recipe names C:\Code\NugetPackageCache. So no phase-3 round can be closed, and 677/793 cannot even be re-measured, until it is rebuilt;
• net48 is unverified since Docs refresh for .NET 10, and make the interceptor goldens run outside Windows #216 and Type-based APIs become an explicit non-goal, and say so (DAP056) #214, both of which changed interceptor goldens, and that leg cannot run on Linux.

Corrections: #117 and #162 are closed, not awaiting a decision; the type-handler branch harvest was filed as "before #208 settles" and #208 has now settled, so that is due (or a deliberate write-off); diagnostic ids recorded as actually shipped - DAP053 runtime registration, DAP054 unusable handler, DAP055 duplicate, DAP056 Type-based non-goal, next free DAP057.

parity.md

One row had aged out: CommandDefinition still claimed "27 overloads, every one skipped silently". #214 moved the Type+CommandDefinition combinations into the non-goal bucket, so it is now 21 of the 22 rows in that bucket. Reworded to cite the generated report rather than restate a number - which is what #213 was for, and this row was a leftover of exactly the habit it set out to kill.

Dangling links

typehandlers-design.md never existed in main - it was a file on the closed #206 branch - and was linked from README.md, state-of-play.md and parity.md. All three now point at the note that did land, typehandler-registration.md. Every .md link under notes/ now resolves.

[andreasblueher]

@mgravell Thanks for all the work you've put in to publish 1.1 much appreciated!