Console 17.6.0: the tabbed Edit/New form dialog renders no tab for a { group } form section, and record:details edit mode offers no editor for a markdown field — so group-referenced fields and markdown fields have no editing surface #21543

Filing gate: ① product defect with reach measured. Class (a). reach: public door, the console UI. Two findings measured by a dev run of the repo:hotcrm seat (session_01ER8ntXZhYebyQ66aXWdjfT) on fresh boots of hotcrm on @objectstack/* 17.6.0, in Chromium. The served page and view metadata were checked equal to the compiled artifact. They are filed together because together they leave a field with no editing surface at all.

Who acts on it: objectstack triage routes it, likely to objectui as the renderer. ⛔ Not a claim; triage sets type and grade. Per hotcrm AGENTS.md §1, the app does not compensate for it. hotcrm#1950 changed three of its own fields to Field.textarea on a maintainer ruling. That was a type choice its requirement allowed, and it is not a fix for these defects.

1. The tabbed form dialog drops { group } sections

• hotcrm src/sales/views/contact.view.ts declares form.sections with { group: 'buying_centre', columns: 2 }, the [Decision] 字段分组漂移已裁定为平台问题(hotcrm#806)—— 定统一机制:lint 镜像规则(不动契约)与/或 section 差量引用形式(契约扩宽) #13855 / feat(spec,lint): a layout section can reference a declared field group instead of copying its members #13897 group-reference form, and the compiled form sections list it.
• Measured: Contacts › any contact › More actions › Edit shows the tabs [Identity, Contact Info, Mailing Address, Preferences]. There is no Buying Centre tab.
• The same holds for hotcrm PR feat(cli): two flow anti-pattern lints — date-equality filters (#1874) + phantom aggregation (#1870) #1950's opportunity form: its { group } sections render no tab, while the four hand-enumerated sections do (Edit dialog tabs: Overview, Forecast, Sales Strategy, Win / Loss).
• Control: record:details on the same records renders the same { group } references (the record:details: the #13855 sections[].group reference form crashes the renderer, and the enumerated fields form renders raw field keys instead of declared labels #16695 fix holds). So the spec form is served, and only the form dialog drops it.
• feat(spec,lint): a layout section can reference a declared field group instead of copying its members #13897 states "the renderer half is tracked separately" (objectui#7051). That card is not readable from this seat, so whether it covers the form dialog as well as record:details is unverified. If it does, this item is a duplicate of it.

2. record:details edit mode has no markdown editor

• Measured: Opportunities › any deal › Details › the pencil (edit mode). Select, boolean, date, currency and textarea fields get editors, and their saves read back over REST. Markdown fields (description, and on PR feat(cli): two flow anti-pattern lints — date-equality filters (#1874) + phantom aggregation (#1870) #1950 three narrative fields) stay —, with an editor count of 0 per markdown cell.
• Control: a markdown field that a form names explicitly does get an editor in the Edit dialog (the account Description).
• Consequence on hotcrm main today: crm_opportunity.description (markdown) is in no opportunity form, so it has no UI editing surface at all. Item 1 then also removes the form-dialog route for any markdown field reached through a { group } section.

Duplicate check

Objectstack issues updated since 2026-07-01, state all: 5,268 issues over 100 REST pages. ⚠️ The walk stopped at the API's page ceiling (page 101 answered 422), so completeness is declared, not proven.

• Title and body were grepped for tab/tabbed near { group / group-ref / fieldGroup: 1 hit, record:details: the #13855 sections[].group reference form crashes the renderer, and the enumerated fields form renders raw field keys instead of declared labels #16695 (closed), which is record:details crashing on the group form, a different surface and fixed.
• Title and body were grepped for markdown near editor / inline edit / edit mode / record:details: 2 hits, [Decision] admins author Markdown docs in the console and put them on the app menu — runtime doc/book authoring surface and a doc navigation item (maintainer's stated need) #19482 (docs authoring) and ADR-0048: Semantic-reference metadata embeds in package docs (flow:// / view:// / dashboard:// / object://) #1795 (ADR-0048), both other subjects.
• Positive control: record:details hit 10.

Dedupe words: tabbed form group section · form.sections group reference no tab · buying_centre tab missing · record:details edit mode markdown · markdown field not editable

Generated by Claude Code