`getGanttConfig` reads 24 more top-level keys ObjectGanttSchema does not declare — same defect as #5903, hidden by the index signature instead of a cast

[yinlianghui]

Measured while implementing #5903 (declare the cast-read gantt keys). Filed
unassigned, observational — recording a measurement, not proposing the fix.

The fact

#5903 counted the keys ObjectGantt reads through (schema as any).K. An
AST enumeration of every top-level key read off the schema prop in
packages/plugin-gantt/src/** (non-test) finds 47 distinct keys. Eleven were
the cast reads #5903 handled. Of the remaining 36, twenty-four are read bare
by getGanttConfig (ObjectGantt.tsx:350-381) and are declared by neither
ObjectGanttSchema nor ObjectGridSchema:

dependenciesField colorField borderColorField parentField
typeField lockField objectField summaryExtent
defaultCollapsedDepth tooltipFields baselineStartField baselineEndField
groupByField resourceView assigneeField effortField
capacity quickFilters autoZoomToFilter timeSegments
interactions exportFileName timeZone dependencyTypes

These are the "flattened ObjectGanttSchema style" branch — the same
GanttConfig members the { gantt: { … } } block carries, spelled at the top
level.

Why it is the same defect with a different mechanism

#5903's eleven were invisible because a cast erased the type. These twenty-four
are invisible because BaseSchema carries [key: string]: any (#5155's
structural ceiling), so a bare schema.colorField type-checks as any with no
cast needed. Same outcome — nothing connects read to declaration — reached
without any syntax to grep for. That is why they score zero on the cast-aware
sweep #5903 published, and why an enumeration has to be AST-based to see them at
all.

What is different, and why this is not just "#5903 times two"

Most of the twenty-four are already modelled by the spec's GanttConfigSchema
(or by objectui's GanttConfig extension for timeSegments). So the question
here is not "invent a declaration" — it is whether the flattened top-level
spelling is a sanctioned second authoring form for GanttConfig, or whether
authors should be moved to the gantt block. That is a ruling, and it decides
whether the resolution is "declare 24 keys" or "retire the flat branch".

Related: #4631 is the on-hold CLASS card. This is not an attempt to reopen it —
#5903's triage said doing the gantt instance does not reopen the class, and this
card is the same instance's remainder, filed so the measurement is not lost.

Reproduce

The cast-aware regex in #5903 scores every one of these 0. An AST walk that
treats an expression as schema-rooted after stripping as / parenthesis /
non-null wrappers, and follows local aliases, finds all 47; the same walk finds
the legitimately declared objectName, viewMode, startDateField and label,
which is the counter-probe that it is not blind.

---

Generated by Claude Code

[os-zhuang]

Triage routing: domain:ui added (fix face is packages/plugin-gantt's getGanttConfig); stays finding, first-touch grading deferred. Grading note: same defect class as #5903 (in flight, PR #6053) hidden by the index signature instead of a cast — re-verify the 24-key census on the post-#6053 merged ref before promoting; #5903's declaration work may absorb part of the population, and the residue is the real card.

Session: session_012od9QE3Wzmgb3aXQ7U156P (triage seat, hourly round)

---

Generated by Claude Code

[claude]

Concentrated triage batch: finding → pm:queue + domain:ui, Task, M — same defect as #5903, one concealment over (index signature instead of casts): 24 top-level keys read bare by getGanttConfig are declared by neither schema. Resolve per #5903's landed pattern (declare the renderer-honoured keys); the AST enumeration in the body is the population, re-derive it on the merged ref at claim. Clause-②: yes (accept-set widening on a published schema) — claim declares it, contract-review tier, mirroring however #5903's landing was reviewed.

---

Generated by Claude Code