fix: settle-only advisory dedupe by pending set signature (0.0.34)

[okisdev]

summary

• the settle-only stop advisory re-emitted identically at every stop boundary while settlement was legitimately deferred (observed three repeats in minutes from a session whose package verification waited on a sibling landing); it now persists a pending-set signature next to the in-flight advisory's existing one and emits only when the set changes, staying silent otherwise
• blocking collection demands keep their current behavior and refresh the signature when they emit combined with settle-only rows

test plan

already verified

• node --test tests/fusion-worker-lifecycle.test.mjs tests/stop-gate.test.mjs -> 103/103 in the main environment
• hot-deployed into the installed cache during verification; live sessions already run the deduped advisory

reviewer should verify

• four platform CI matrix settles green

notes

• marketplace refresh to a real 0.0.34 directory formalizes the already-live behavior