Upload the three floor disposition receipts the job already writes and discards

[briansrls]

What this does

The three identity-grain receipts the witness floor already computes on every run — required_floor_disposition.tsv, expected_red_roster_join.tsv, long_home_storage_agreement.tsv — were written to the runner's working directory and then discarded with the runner. This uploads them.

Why

A PR was blocked by sixteen failures in witness families its diff could not reach; the summary counters said fifteen identities had moved between dispositions, and the incident could not be closed because the rows naming which fifteen no longer existed anywhere. Two independent recomputations from the trees then disagreed with the floor's own counts at both ends — so the only instrument that could settle it is the one the job was deleting. A receipt computed and dropped is worse than one never computed, because the summary it backs keeps being quoted as though the detail were available.

long_home_storage_agreement.tsv is in the set deliberately: it records a file whose PATH and whose declared MODULE disagree about long-home, which is the first hypothesis any recurrence has to eliminate.

Verified, not assumed

• The TSVs are written, not merely named. cli_run.rs reads all three env vars and calls write_required_floor_disposition_tsv / write_expected_red_roster_join_tsv / write_long_home_storage_agreement_tsv at the end of the run. All three vars are already in the committed job env, so all three files exist on every run today.
• upload_artifact_action is single-bound — one declaration in dag/extdeps/github/actions.dag. The v2/v4 double binding that tool_pin_witness_test.dag records was deleted; every other reference is a consumer.
• The emitted bytes came from the authority, not from hand-editing the yaml: regenerated via dag/tools/generated_artifact_gate.dag main_wet in one remote dispatch (amd64 build + run together). witnesses.yml was the only path the regen modified, so no unrelated drift rode in.

Two deliberate choices

• if: "!cancelled()" rather than success(): the run this evidence is for is the failing one, so a step that only fires after a green floor would capture exactly the runs nobody needs it for. Cancellation is excluded because a cancelled run's TSVs are partial by construction, and a partial receipt read as a complete one is the fabricated-output failure.
• if-no-files-found: warn: the upload must never turn a green run red. A missing receipt is a gap to notice, not a reason to fail the floor.

Scope

This uploads receipts. It changes nothing about what the floor plans, routes, or refuses, and it does not close the open declined_long 558→543 question — it is the instrument that makes the next instance of that question closable.