| ... | ... | @@ -47,3 +47,24 @@ share records and four selected-file rows matched the expected path-only |
| 47 | 47 | projection, and all nine affected public URLs returned their original 200 |
| 48 | 48 | responses within a 78.2-second upper bound. Production source metadata and |
| 49 | 49 | share records remained unchanged during rehearsal. |
| 50 | |
| 51 | ## 2026-10-16 production evidence |
| 52 | |
| 53 | Release `765dec72842b4d08` deployed described main revision |
| 54 | `e0cc66a00eb2757846148a241961225d1f9b1253`. All production routes passed |
| 55 | the release workflow's checks. The canonical host unit now serves share |
| 56 | operations; obsolete Win10/ARM host overrides were archived with the release |
| 57 | backup after their effective VM code matched main byte for byte. |
| 58 | |
| 59 | The six requested folders moved to `Share` with their requested names. |
| 60 | All 2,184 metadata entries retained their device, inode, mode, size, and mtime. |
| 61 | All 20 native shares and four selected-file rows matched the path-only |
| 62 | projection, and all nine affected public URLs returned their original 200 |
| 63 | responses. Meadow had no native public link; its folder moved without creating |
| 64 | one. Copyparty remained stopped throughout the folder and database changes. |
| 65 | |
| 66 | The move's stop-to-public-readiness interval was 13.44 seconds. Independent |
| 67 | one-second HTTPS HEAD sampling bounded total public unavailability across |
| 68 | release activation and the move to 55.12 seconds over three intervals. |
| 69 | Restricted plan, database/config backups, frozen job, and result evidence are |
| 70 | in `/var/lib/studio/copyparty-cutover/20261016T082910Z-424b5410`. |