chore(sdui-parser): stop claiming .objectui-sha on this PR — the pin lands via #19398 first

The Single-Claim Path Guard on the pin-bump PR fails with "At most one open PR
may modify a declared single-writer path": .objectui-sha is a declared
single-writer path and this draft still rewrites it (53ded82bf7a4 to
cfcc17d9dd04), so it counts as an open claimant. Per ruling batch #200 item 4
the pin bump lands on its own PR first.

So this branch releases the claim: both pin-carried files are restored to
main's blobs byte for byte (.objectui-sha and scripts/sdui-manifest.record.json,
the latter because check-sdui-manifest requires record pin == .objectui-sha).
Nothing else is touched — the parser port, its tests and the changeset are
unchanged.

check:sdui-lockstep is RED in the interim, by design: [pin-moved], the lockstep
record was taken at cfcc17d9dd04 while .objectui-sha now reads 53ded82bf7a4.
This PR stays draft and re-records the lockstep at the new pin in a merge lap
after the pin bump lands.

Claude-Session: https://claude.ai/code/session_012GcsUbuqFGBibkEDMRC1eE
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.objectui-sha

@@ -1 +1 @@
-cfcc17d9dd04ebb80c092cacb4f4034425f51b29
+53ded82bf7a494f54e344e19099dbf00854b8694

scripts/sdui-manifest.record.json

@@ -9,10 +9,10 @@
     "a pin bump without regeneration goes RED there — that is the anti-rot half of the freshness gate.",
     "Regenerate + re-record: node scripts/gen-sdui-manifest-node.mjs (see its header for the offline mode)."
   ],
-  "objectuiSha": "cfcc17d9dd04ebb80c092cacb4f4034425f51b29",
+  "objectuiSha": "53ded82bf7a494f54e344e19099dbf00854b8694",
   "objectuiPackagesVersion": "17.6.0",
   "generator": "scripts/gen-sdui-manifest-node.mjs",
-  "generatedAt": "2026-09-17",
+  "generatedAt": "2026-09-08",
   "sha256": "49211fee7792cf51174930dc2c1be2169d5175f77a83491f68f90b3f0c19e69d",
   "components": 57
 }