slides: no structural commands — create/duplicate/reorder native slides, create/move/style elements

[sebsnyk]

Problem

gog slides has no structural commands. It can create full-bleed image slides (add-slide), edit text, and delete slides — but cannot:

• create a native (themed, editable) slide — add-slide requires an <image>; there's no "new slide from layout".
• duplicate a slide (duplicateObject) — the highest-value missing op for reusing a branded template slide.
• reorder / move a slide (updateSlidesPosition).
• create or manipulate elements: createShape, createLine, move/resize/rotate (updatePageElementTransform), fill/outline (updateShapeProperties), z-order, group/ungroup, alt text, delete a single element (deleteObject).

Everything structural therefore requires the raw Slides API.

Repro

gog slides add-slide <deck>            # requires an <image> arg; no native slide
gog slides --help                      # no duplicate-slide / move-slide / shape / line / element commands

Suggested

• gog slides new-slide <deck> --layout TITLE_AND_BODY [--index N] (native, themed).
• gog slides duplicate-slide <deck> <slideId> [--to-index N] and move-slide <deck> <slideId> --to-index N.
• A gog slides element subtree: create-shape/line, move/resize, recolor/outline, z-order, group, alt-text, delete.

gog 0.27.1.

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 18, 2026, 5:32 PM ET / 21:32 UTC.

Summary
Keep open: the native slide create/duplicate/move slice has landed, but the remaining element subtree is still missing and a collaborator explicitly kept this issue open for that work.

Reproducibility: yes. Source inspection shows the slide-level commands now exist, while the requested element subtree and shape/line/transform/style/group/alt-text/delete-object commands are still absent.

Root-cause cluster
Relationship: canonical
Canonical: #826
Summary: This issue remains the canonical tracker for the remaining Slides element-structure work after a merged slide-level partial implementation.

Members:

• partial_overlap: feat(slides): add native slide structure commands #833 - The merged pull request implements native slide creation, duplication, and reordering, but its body and maintainer follow-up explicitly leave the element subtree in this issue.

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Next step
A maintainer already landed the slide-level slice and left the broader element subtree open, so the next step is human scoping or splitting before another implementation pass.

Review details

Best possible solution:

Keep this issue open as the canonical tracker for the remaining element manipulation surface, with maintainer-scoped follow-up PRs that add docs, dry-run tests, and live Google Slides proof.

Do we have a high-confidence way to reproduce the issue?

Yes. Source inspection shows the slide-level commands now exist, while the requested element subtree and shape/line/transform/style/group/alt-text/delete-object commands are still absent.

Is this the best way to solve the issue?

No for one broad sweep. The best path is to split the remaining element surface into focused, live-tested command slices that fit the existing Slides command style.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• The remaining element subtree spans several Slides API primitives and command UX choices, so a single broad automated PR could overreach without maintainer slicing.
• Current main already has adjacent insert-image, insert-text, table, and text-style commands; new element commands should avoid duplicate or conflicting semantics.

Codex review notes: model internal, reasoning high; reviewed against c172741709aa.

Label changes

Label changes:

• add clawsweeper:no-new-fix-pr: Current issue advisory state selects this label.
• add clawsweeper:needs-maintainer-review: Current issue advisory state selects this label.
• add clawsweeper:needs-product-decision: Current issue advisory state selects this label.
• remove clawsweeper:fix-shape-clear: Current issue advisory state no longer selects this label.
• remove clawsweeper:queueable-fix: Current issue advisory state no longer selects this label.

Label justifications:

• P2: This is a normal-priority Slides automation feature with clear user value and limited blast radius, not an urgent regression or security issue.
• impact:other: The issue affects practical Slides structural automation, which is maintainer-visible but outside the specific owned impact categories.

Evidence reviewed

What I checked:

• Issue and maintainer scope: The issue asks for native slide creation, duplication, reordering, and an element subtree; the latest maintainer comment says the slide-level first slice landed as a91cead and this issue remains open for create/transform/style, z-order, group/ungroup, alt text, and single-element deletion.
• Current slide-level commands: Current main registers new-slide, duplicate-slide, and move-slide alongside existing Slides commands, so the slide-level portion is implemented on main. (internal/cmd/slides.go:25, c172741709aa)
• Slide-level implementation: SlidesNewSlideCmd builds CreateSlide requests, SlidesDuplicateSlideCmd builds DuplicateObject plus optional UpdateSlidesPosition, and SlidesMoveSlideCmd builds UpdateSlidesPosition. (internal/cmd/slides_structural.go:42, c172741709aa)
• Remaining element gap: The command registry has adjacent insert-image, insert-text, table, and text-style commands, but no element subtree or dedicated create-shape, create-line, transform, shape-style, z-order, group/ungroup, alt-text, or single-element delete command surface. (internal/cmd/slides.go:31, c172741709aa)
• Adjacent existing element commands: Existing element-related support covers table creation, text insertion, and image insertion, which reduces but does not replace the requested generic element manipulation subtree. (internal/cmd/slides_table.go:14, c172741709aa)
• Merged slice provenance: Git history ties the new slide-level commands to the merged structural-slides commit, and no release tag contains that commit, so this slice is current-main-only while the issue remains open for elements. (internal/cmd/slides.go:25, a91ceadc8c31)

Likely related people:

• steipete: Recent history and comments show Peter Steinberger landing adjacent Slides table, introspection, image, release, and maintainer-scope work around this issue. (role: recent area contributor and reviewer; confidence: high; commits: c78e609203f9, 5ff811dcc498, 32a6dddf8d86; files: internal/cmd/slides.go, internal/cmd/slides_table.go, internal/cmd/slides_insert_image.go)
• Chris Parsons: Git history shows the original add-slide, list-slides, and delete-slide command work that this structural command request extends. (role: introduced core Slides editing commands; confidence: medium; commits: 91b1e5b3f325, 8b08d11777fe; files: internal/cmd/slides.go, internal/cmd/slides_add_slide.go, internal/cmd/slides_delete_slide.go)
• Chris Sanchez: Git history shows insert-text and replace-text command work adjacent to the requested element manipulation surface. (role: adjacent Slides text-editing contributor; confidence: medium; commits: 929a3d22efee, d047a0325f12; files: internal/cmd/slides_insert_text.go, internal/cmd/slides_replace_text.go, internal/cmd/slides.go)
• sebsnyk: The issue author supplied the concrete remaining element operations and command-shape examples now being tracked. (role: reporter and command-shape source; confidence: medium)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

[clawsweeper]

🦞⚠️
Automatic implementation stopped before completion.
Reason: The automatic implementation worker stopped before all deterministic gates completed. Open the workflow run for the exact blocker.
Worker: https://github.com/openclaw/clawsweeper/actions/runs/27742748068

[steipete]

Slide-level first slice landed in #833 as a91ceadc: native blank/predefined/exact-layout slide creation, duplication, and reordering, with live provider ordering proof.

Keeping this issue open for the remaining element subtree: create/transform/style, z-order, group/ungroup, alt text, and single-element deletion.