vgsp-sema: re-seed and apply the first release of a fresh CE channel when the pool word is residue (ISSUE-0002)

A fresh session's first CE release could read a previous session's value
through the just-injected pool pin (r64: cur=134 pay=1; r63: cur=114696).
svc_init_expected_payload seeded the channel expectation from that residue,
the release candidate then skipped as stale (payload <= cur) and the client's
first tracker wait never completed.

When the first GPFIFO entry of a fresh CE channel (submissions == 0) decodes a
pool release whose word reads ahead of the payload, treat the word as residue:
re-seed expected_sem_payload/entry_want from the payload and apply the release
absolute instead of skipping. Monotonic trackers make the absolute write
idempotent; displaced pins stay owned by the fan-out/pending paths. Bounded
'sema-chan: pool residue' diagnostic plus a residue counter in the drain line.

0 files changed, 0 insertions, 0 deletions