test: the tests P6's gate never reached, under one-record dedup

P6's branch paused with its gate interrupted, so five tests that
predate plan P6 step 4 (the same bytes filed twice are one attachment,
linked to each subject) still encoded the invariant it replaced, and
one golden carried counts from before extraction records existed.

- store: `blob_dedup_and_hash_verification` expects one attachment
  row under the first filing's name, not two. The `attach_receipt`
  spec block's INVARIANT 2/3 now say what P6 built; the stale "each
  filing is its own attachment" was the one wording left.
- store: the power-loss replay copies the blob store too. The books
  on disk were always journal, database and blobs; verify now reads
  an extraction's text blob (P6 step 2), so a copy without `blobs/`
  cannot verify.
- store: the refusals property allows `AttachReceipt` and
  `FileDocument` to journal nothing when the bytes are already on
  file: the record they return is the record they were.
- viewer: each statement the reconciliation helper files has its own
  bytes (a wrong statement is voided and a new one comes); identical
  bytes would be one record, and a record is one statement.
- viewer: the tall sidebar's shapes golden is re-blessed. The fixture
  books now carry extraction records, so the Overview attention
  count, the event count and the verified-file count the sidebar
  prints moved; no layout changed.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HS8WZziDnyxunC23MUxrLp

crates/ledger-store/src/store.rs

@@ -4488,9 +4488,11 @@ impl Store {
     /// INVARIANTS:
     ///   1. The bytes MUST be stored under their SHA-256 and read back
     ///      identical, verified against it.
-    ///   2. The same bytes filed twice MUST share one stored file, and the
-    ///      second filing MUST say deduplicated.
-    ///   3. Each filing MUST be its own attachment, journaled
+    ///   2. The same bytes filed twice MUST be one record (plan P6 step 4):
+    ///      the second filing returns the first's id, says deduplicated,
+    ///      and links that record to the new subject (`attachment.linked`)
+    ///      when it isn't linked there yet.
+    ///   3. The first filing of bytes MUST be journaled
     ///      (`receipt.attached`), with its name, type, and description.
     /// SCENARIOS:
     ///   1. IF `entry_id` names no entry: SHOULD refuse