STATE.md develop_head is two commits stale, so the next factory session opens on sha-currency drift

Heads-up on a project-state condition rather than a code defect, in case it saves a confusing session start.

`factory-artifacts` at `7ce4c071` records `develop_head: 85f30ea7f`. `develop` is now `561d8bac`, two commits ahead:

```
561d8bac fix(dtu-claroty): embed fixtures so the clone runs outside its build tree (#287)
daac70dc ci: onboard nightly + fuzz-nightly to the owned fleet scheduler (#284)
```

`#287` is mine, so I own half of this. `#284` is yours, merged out of band. Either way `verify-sha-currency.sh` compares `STATE.md`'s `develop_head` against `git rev-parse origin/develop`, so the next factory session looks likely to open on a drift failure whose cause is two merges that never had a state-manager burst behind them.

No action needed from me, and I am not going to touch `factory-artifacts`. Flagging it because the cause is invisible from inside a session: nothing in the drift message says "two PRs merged without a burst".

The general shape of it is filed upstream as BOHICA-LABS/vsdd-factory#833, since it applies to any factory-run project rather than to prism specifically. If you would rather I hold further PRs until there is an agreed intake path, say so and I will queue them as issues instead. #288, #291 and #292 are all green and can wait without going stale.

Examine STATE.md in the factory-artifacts directory to see the develop_head SHA. Compare it with the current origin/develop using git rev-parse. The script verify-sha-currency.sh likely performs this check; run it to see the drift failure. Understanding the factory session flow and the upstream issue BOHICA-LABS/vsdd-factory#833 is needed to grasp the full context.

Written by the indexing model from the issue text.