Skip to content

Record page: the default record page offers no way to turn on stage press, so authors must write a whole page #30118

Closed as duplicate

Description

@objectstack-fleet

epic:#26676#1 · zhuangjianguo · session_cdb7a717def74e719988f089fbaa18ff

From a real-user walkthrough of the development flow, filed on the maintainer's word: 「第一组:会卡住人或误导人,立卡」 (2026-11-04). Measured on main 987ff33b88 unless a line says otherwise. Test project scaffolded with create-objectstack@18.3.0.

Governing text: #28061 and PR #28303 made stage press an opt-in, allowStageChange on the record:path block, off by default. #11243 made the inert path stop looking like a control. This card does not reopen that default.

What a customer sees

On a ticket the path shows New, In Progress, Resolved. A technician clicks In Progress and nothing happens. They open the edit form, face every field, and change Status there. Measured by clicking on the published 18.3.0.

Measured

  • An object that declares stageField gets its record page from ui/packages/plugin-detail/src/synth/buildDefaultPageSchema.ts, which draws record:path without allowStageChange.
  • allowStageChange appears only on the block: packages/spec/src/ui/component.zod.ts:2175 and ui/packages/plugin-detail/src/renderers/record-path.tsx. No key on the object or the default page reaches it.
  • So the author who wants this one behavior has to author and maintain a full record page. The stage press itself was not exercised in this walkthrough.

Expected

An author can turn stage press on for the default record page without writing a page, in the same opt-in posture. Where the key belongs is for the contract review.

Activity

  1. objectstack-fleet commented on Nov 4, 2026

    @objectstack-fleet
    ContributorAuthor

    triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

    Path: none

    Triage: first-touch audit · p2 · domain:ui · pm:queue · 2026-11-04T16:00Z

    ⛔ Not a claim.


    Generated by Claude Code

  2. objectstack-fleet commented on Nov 4, 2026

    @objectstack-fleet
    ContributorAuthor

    triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

    Duplicate of the triage audit just above (comment 6635414689), posted twice by a timed-out relay retry. Read that one.


    Generated by Claude Code

  3. added
    domain:uiDomain lane — seat card indexed by label:pm:seat
    pm:queueReady for the PM dispatch loop
    on Nov 4, 2026
  4. objectstack-fleet commented on Nov 5, 2026

    @objectstack-fleet
    ContributorAuthor

    domain:ui#4 · os-support-ai · session_01WGufzinedUGSXteN45poyo

    Premise re-read · #30118 already met on main · ⛔ not a claim

  5. objectstack-fleet commented on Nov 5, 2026

    @objectstack-fleet
    ContributorAuthor

    triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

    Closed as duplicate · 2026-11-05T12:31Z

    The maintainer ruled in the triage session 「同意」 on closing #30118, #26059, #30373 and #30374 (2026-11-05). The same ruling lets triage close duplicate cards and completed tracking parents from now on. Read fresh before this stroke.


    Generated by Claude Code

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

    domain:uiDomain lane — seat card indexed by label:pm:seatenhancementNew feature or requestpm:queueReady for the PM dispatch looppriority:p2Medium: important, M3

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions