automation: a cloned packaged flow reaches no Studio surface — the clone is stored with no package, and every Studio Automations rail lists only package-scoped flows #21332

QA-source: #21330 · automation.packaged-flow-clone-contract · acceptance[6]

What fails

ADR-0126 §7.1 makes a clone of a packaged flow "an ordinary org/install-owned flow", and §1.3 / the Setup › Packaged automation page promise it is edited in Studio ("Editing happens in Studio"). On 17.6.0 (617f25f8, Console pin 31971ff1e28f) the clone is created, survives a restart and dispatches, but no Studio surface lists or opens it.

Reproduction (stock showcase, admin)

1. POST /api/v1/automation/showcase_urgent_task_alert/clone {"name":"qa_urgent_alert_clone","label":"QA urgent alert clone"} → 200, status: draft.
2. POST /api/v1/data/sys_metadata/query {"where":{"name":"qa_urgent_alert_clone"}} → the row has package_id: null, scope: platform.
3. GET /api/v1/meta/flow?package=com.example.showcase → 30 flows, clone absent. Bare GET /api/v1/meta/flow → 31 flows, clone present.
4. Console /_console/studio → "No writable packages yet"; the only installed entry is the read-only showcase package. /_console/studio/com.example.showcase/automations lists the 30 packaged flows, not the clone. The deep link …/automations?surface=flow%3Aqa_urgent_alert_clone redirects to another flow.
5. Expected: the clone appears on a Studio Automations rail (or the clone lands somewhere Studio can open). Actual: unreachable from Studio.

Reproduced on two fresh boots by the runner and once more by an independent verifier (also via a clone created from the Setup page's dialog).

Mechanism

• The clone arm strips _packageId / _provenance on purpose (packages/runtime/src/flow-clone.ts) and persists a package-less row.
• Studio's Automations rail is package-scoped at the pin: objectui StudioDesignSurface.tsx → loadPackageSurfaces(client, 'flow', packageId) (both client.list(type, {packageId}) and listDrafts({packageId, type})); Studio has only /studio, /studio/:packageId, /studio/:packageId/:tab (apps/console/src/components/StudioRoute.tsx); the landing lists writable and installed packages only.
• So a package-less flow matches no rail.

Notes

• The durability half of the checklist clause's expected fail is fixed (cb4c31d, fix(runtime)!: the /automation create and update doors save the flow as a tenant row, so what they answer 200 for survives a restart (#20862) #20907); this card is the reachability half only. It was recorded in docs/qa/platform-checklist/FOLLOW-UPS.md §8 as row D18 ("safe to file") and never filed.
• The fix needs an owner decision — either Studio gains a surface for package-less (org/install-owned) flows (objectui), or the clone lands in a writable package (objectstack, against the deliberate provenance strip).
• Severity (verifier): major — the engine half works, but the one promised authoring surface cannot reach what it produces.

Full run evidence: #21330.

Generated by Claude Code