Skip to content

Ship a default recipe for the page-box drag move #205

Open

Description

@mberrys

Ship a default recipe for the page-box drag move

Outcome

A completed page-box drag in Quick can run to a published, revalidated artifact on a default installation. Today the drag proposes a move that cannot execute, because no shipped recipe offers translate-page-box.

Parent and boundary

Parent: #4 (L03 - Quick Workspace). Follow-up to #104 (actionMoveSelection, ADR-012). Plan, approval and execute remain the Fix workspace's; the command catalog remains the only route in, and this issue adds no second mutation path.

Grounding

  • ADR-012 implementation notes: "With no recipe offering translate-page-box, the command fails with move/rejected and the host announces that a recipe is needed; there is no built-in recipe, so the drag proposes a move but cannot execute one until the operator imports one."
  • docs/QUICK_CANVAS_EDITOR_GAPS.md: "The move needs a recipe that offers translate-page-box; none ships built in."
  • The recipes directory is empty in every test and smoke environment (docs/WORKSPACE_SURFACES_586.md), so no existing sample can satisfy the drag.

Acceptance

  • One recorded decision for where the recipe ships (bundled sample recipe, profile entry, or first-run onboarding step), including where it lives for an installed package and how it is versioned or updated.
  • One end-to-end default-install run: drag a page box, the proposal binds to the recipe, plan, approval, execute, exact published-byte revalidation, with the artifact identity recorded.
  • A user-imported recipe remains supported and is not silently shadowed by the shipped one; precedence is recorded.
  • Failure case: with the recipe absent, stale, or offering a removed operation, the move still fails closed with the typed move/rejected reason and a message naming what is missing.

Required proof

A quick-lane or acceptance test that drives the default journey over a representative fixture, plus the decision record. Record the exact source SHA, test command or hosted run, fixture identity, and any skipped lane. Run the repository's mapped proof and check-change gate for a PR.

Handoff

Record changed files, observed result, remaining risk, and a 1-3 sentence anti-slop review. Completion means acceptance evidence, not merely a merged implementation.

Sources

Approved master roadmap (L03 scope) and ADR-012 / issue #104. Gap review of the issue suite and reset repository state, 2026-10-04.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Promotion stage

    Stable present

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions