P2: Make Files, Photos and Sharing workflows discoverable in the registry CLI #840

Open
opened 2026-10-02 13:23:13 +00:00 by kayg · 0 comments
Owner

Research follow-up under #484. Source snapshot: c4a61e8cf090170f35b1bed3350d9de20c83ecd5.

Files streaming commands work and all applicable routes have generated adapters. The remaining gap is completing User workflows without a manual protocol recipe.

Evidence:

  • CLI has ls/cat/put/get/mv/rm/trash/restore/versions/share and Files visibility commands.
  • Copy, mkdir, Empty Trash, Version restore, public-link update/revoke, folder pins, Photos timeline/search/stack/key-photo operations remain raw operation IDs.
  • Generated tools use 128 KiB input and 1 MiB output. Large ZIP/original/segment reads do not all have a range/paging solution.
  • Photo Trash can expand pairs/stacks in the browser; the shared adapter exposes underlying Files operations rather than this selection intent.

Acceptance:

  1. Expose area discovery and thin registry-derived commands for the existing actions; reuse current transfers for large files.
  2. Document or add bounded continuation for each supported tool transfer without losing headers, revisions or bytes.
  3. Preserve stable item identities, Home-prefix grants and Share recipient isolation in every adapter.
  4. Check RAW/JPEG and motion/photo selection behavior, copy/move, public options, recoverable Trash/Version restore and explicit confirmation.
  5. Keep newer Sharing and Photos work in their existing product slices; do not invent unapproved features.

Matrix F1–F8/P1–P3/V1; #484, #479 and #592. These are workflow/ergonomic gaps; no missing raw adapter is claimed.

Full evidence and decisions: docs/research/agent-surfaces.md on branch job/research-surfaces. No runtime change was made by the research job.

Research follow-up under #484. Source snapshot: `c4a61e8cf090170f35b1bed3350d9de20c83ecd5`. Files streaming commands work and all applicable routes have generated adapters. The remaining gap is completing User workflows without a manual protocol recipe. Evidence: - CLI has ls/cat/put/get/mv/rm/trash/restore/versions/share and Files visibility commands. - Copy, mkdir, Empty Trash, Version restore, public-link update/revoke, folder pins, Photos timeline/search/stack/key-photo operations remain raw operation IDs. - Generated tools use 128 KiB input and 1 MiB output. Large ZIP/original/segment reads do not all have a range/paging solution. - Photo Trash can expand pairs/stacks in the browser; the shared adapter exposes underlying Files operations rather than this selection intent. Acceptance: 1. Expose area discovery and thin registry-derived commands for the existing actions; reuse current transfers for large files. 2. Document or add bounded continuation for each supported tool transfer without losing headers, revisions or bytes. 3. Preserve stable item identities, Home-prefix grants and Share recipient isolation in every adapter. 4. Check RAW/JPEG and motion/photo selection behavior, copy/move, public options, recoverable Trash/Version restore and explicit confirmation. 5. Keep newer Sharing and Photos work in their existing product slices; do not invent unapproved features. Matrix F1–F8/P1–P3/V1; #484, #479 and #592. These are workflow/ergonomic gaps; no missing raw adapter is claimed. Full evidence and decisions: `docs/research/agent-surfaces.md` on branch `job/research-surfaces`. No runtime change was made by the research job.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/calternal#840
No description provided.