Use the same additive LFS rules as main to resolve the shared-file conflict; preserve raw/data content and pending human review. Regression-tested fixes and truthful evidence provenance.
Apply the v1.1 version and tooling migration to EgoHOS/shared-v1.1
Co-Authored-By: Claude Code <noreply@anthropic.com>
Candidate PR: rename EgoHOS `shared-v1.0` to `shared-v1.1` and replace
`doc/CONTRACT.md` with the v1.1 contract. **Please review before merging.**
EgoHOS is the one dataset in this migration with nothing to merge. Its registry declares
exactly two components, `rgb` and `segment`, and both are media; the only `.pt` files in the
tree are the 212 media validity files (`rgb_valid.pt` / `mask_valid.pt`, 360,114 B in
total), which v1.1 keeps exactly as they are. There is no per-frame numeric tensor file
anywhere under `EgoHOS/shared-v1.0`, so v1.1's merge rules bind nothing here, no reader
needs adapting, and there is no local migration or acceptance run to make. What remains is
the version change itself: the directory rename and the contract.
### What this PR changes
- **`EgoHOS/shared-v1.1` is created from `EgoHOS/shared-v1.0` by server-side copy.** All
1,570 files are `CommitOperationCopy` operations sourced at `main`, so every byt…
