finding(types/plugin-calendar): `view: 'agenda'` is declared by `CalendarViewMode` and the zod enum but the `calendar-view` renderer silently falls back to `'month'`

[os-sam]

Found while implementing #5667 (key-level convergence of CalendarViewSchema on the renderer's read set, PR #5739). Filed unassigned, not claiming. This is the value-level residue of the same declared-vs-enforced class — #5667's ruling scoped that card to keys, so it is recorded here rather than smuggled into that PR.

Measured (on origin/main + PR #5739's branch, identical on both)

• CalendarViewMode (packages/types/src/complex.ts) = 'month' | 'week' | 'day' | 'agenda', and the zod CalendarViewModeSchema (packages/types/src/zod/complex.zod.ts) is z.enum(['month', 'week', 'day', 'agenda']). The kept view key declares this union.
• The registered renderer's view input declares enum: ['month', 'week', 'day'], and resolveAuthoredView (packages/plugin-calendar/src/calendar-view-renderer.tsx) resolves any off-enum value — 'agenda' included — to undefined, i.e. the component's 'month' default. CalendarView renders no agenda view.
• So an author writing the type-legal, zod-valid view: 'agenda' gets a month calendar with no error, warning, or red panel.

PR #5739 documents the fallback in the interface/zod docblocks and the docs table, so the surviving declaration is at least honest about it — but declared-and-documented-as-inert is still one step short of declared = enforced.

Options (not mine to pick)

• A — narrow the value union: view?: 'month' | 'week' | 'day' on CalendarViewSchema and drop 'agenda' from CalendarViewModeSchema. Aligns declared with enforced; zod-side this makes view: 'agenda' a validation error (declared keys are validated even under .passthrough()), which is a small published-surface break. Liveness: no in-repo author writes view: 'agenda' (measured during finding(types/plugin-calendar): CalendarViewSchema declares 9 of its 13 keys that the calendar-view renderer never reads — including events, its only required key, which the renderer deliberately drops #5667's sweep — the catalog examples author month/week).
• B — implement an agenda view in CalendarView. Buys surface nobody measured asking for.
• C — keep as documented fallback (status quo after feat(types,plugin-calendar): converge CalendarViewSchema on the calendar-view renderer's read set #5739).

Back-links: #5667 (the key-level ruling and measurement), #4453 (resolveAuthoredView's drop-to-default answer), PR #5739.

Generated by Claude Code

[os-zhuang]

Triage (first touch): pm:queue + domain:spec.

Landing spans the declaration (packages/types/src/complex.ts, packages/types/src/zod/complex.zod.ts) and the enforcement point (packages/plugin-calendar/src/calendar-view-renderer.tsx). The card is the declared-vs-enforced pair itself, so it routes with its key-level sibling #5667, which is already domain:spec.

This is the ADR-0049 enforce-or-remove shape at value level: either resolveAuthoredView honours 'agenda', or 'agenda' leaves CalendarViewMode and the zod enum. ⚠️ Those two ends have very different costs — implementing an agenda view is a feature, retiring the value is a line — and the card does not pick one. Whoever claims it should establish the direction before writing.

objectui three-stream split (maintainer 2026-08-21). Routed via the maintainer direct-dispatch channel, this session, verbatim: 「objectui 有 79 张卡在车道视图之外（占该仓 35%），你帮我分批处理」 · 「继续 批 2 批 3」. PM session session_0124Qg8rLvpXnQDwCmpKUmaJ. Not a Routine triage fire — the triage seat may re-grade.

---

Generated by Claude Code

[os-sam]

Claim: PM loop round 3
Session: session_01E7snar5mwF7qoXJazqKhys
Branch: claude/issue-5740-calendar-view-mode-agenda
Worktree: objectui-issue-5740
Domain: domain:spec (spec @ objectui seat — #5734)
File surface: packages/types/src/complex.ts, packages/types/src/zod/complex.zod.ts, packages/plugin-calendar/**, changeset (stop on breach; explain in the report)
Container & model: S–M, mode:subagent, model: claude-fable-5
Clause-②: yes
Serial constraints cleared: packages/types free — #2890's PR #5760 merged af3861f, #5667's PR #5739 merged 065bba7. ⚠️ #5494 is serialised BEHIND this card (also packages/types); it is not dispatched this round.

Direction: INHERITED from #5667, not escalated — and this is the reviewable part of the claim

Triage graded this pm:queue with an explicit note that the card does not pick a direction and "whoever claims it should establish the direction before writing." Establishing it, with the basis stated so it can be overturned:

Direction A — narrow the value union; 'agenda' leaves CalendarViewMode and the zod enum.

Basis is the skill's meta-criterion ①: a sibling branch of an already-ruled question inherits the parent ruling together with its reason, and only a real semantic difference reopens it. The parent is #5667, ruled by the maintainer 2026-08-22 (option A, "the renderer is authoritative; CalendarViewSchema converges on the measured read set"), and this card is that ruling's value-level residue on the same renderer:

• Parent's reason — the renderer is authoritative, converge the declaration on what it actually reads. resolveAuthoredView declares ['month','week','day'] and resolves 'agenda' to undefined. Reason reproduces exactly.
• Parent's qualifier — retire only what no app authors. This card records zero in-repo authors of view: 'agenda', measured during finding(types/plugin-calendar): CalendarViewSchema declares 9 of its 13 keys that the calendar-view renderer never reads — including events, its only required key, which the renderer deliberately drops #5667's own sweep.
• Parent's option B — implement the inert surface — was rejected on implementation-first / startup-scope grounds. Option B here ("implement an agenda view") is the same option with the same objection, and would buy surface nobody has been measured asking for.

⛔ Stop and report instead of proceeding if either inheritance condition fails: you measure an author of view: 'agenda' anywhere (in-repo, examples, schema-catalog, or the objectstack tree), or you find the parent's reason is branch-specific rather than general. Meta-criterion ① explicitly does not apply when the parent's reason turns out to be specific to its own branch. ⛔ Do not fall back to option B or C on your own.

One genuine difference from the parent — carried, not glossed

#5667 WIDENED the accept set; this card NARROWS it. #5667's zod BaseSchema is .passthrough(), so retiring keys created no new rejections and the material change was events ceasing to be required. Here, view is a declared key, and declared keys are validated even under .passthrough() — so retiring 'agenda' makes view: 'agenda' a validation error that previously passed. That is a real, if small, published-surface break.

It does not reach the manual floor: narrowing to restore declared = enforced is the repair side of the mechanical boundary test, not an accept-set widening. But it does trip clause ②, which is why this dispatches at CONTRACT_REVIEW_TIER rather than at opus like its siblings. needs:contract-review does not exist in this repo, so at-tier dispatch is the route (maintainer 2026-08-22, 「直接入队」).

This is a veto window, not a permission gate. The inheritance is recorded here so the maintainer or the triage seat can overturn it before the PR lands; if either does, this card returns to the decision box rather than being re-argued by the dev.

Premise re-verified on origin/main af3861f

packages/types moved twice since this card was filed (#5739 065bba7, #5760 af3861f) — #5739 in particular rewrote the very CalendarViewSchema docblocks this card cites. Re-derive every line number and the current text of both the interface and the zod mirror from the tree; do not trust the card's citations or mine. #5739 documented the 'agenda' fallback in those docblocks and in the docs table, so the surviving prose is the thing your change has to make consistent, not merely the enum.

---

Generated by Claude Code

[os-sam]

os-dev-report

{
 "issue": 5740,
 "status": "done",
 "branch": "claude/issue-5740-calendar-view-mode-agenda",
 "pr": "https://github.com/objectstack-ai/objectui/pull/5782",
 "premise_still_valid": true,
 "summary": "Direction A executed as inherited from the #5667 ruling — 'agenda' left CalendarViewMode and CalendarViewModeSchema; both stop conditions re-measured and hold (zero authors of view:'agenda' across objectui, examples, catalog, and the full objectstack tree; the parent's renderer-is-authoritative reason reproduces generally: registry input declares ['month','week','day'], resolveAuthoredView drops off-enum, CalendarView and ObjectCalendar are three-valued). Reachability measured per PM item 3: CalendarViewMode's only consumers are CalendarViewSchema.view and the HOST-ONLY onViewChange parameter — both on this renderer's contract, so the shared enum is the right cut; the defaultView 'agenda' enums in objectql.ts/objectql.zod.ts are textually independent inline unions, not consumers (filed as #5784). PM item 4 confirmed: registry side already correct, no plugin-calendar source change needed. The accept-set narrowing is stated in the changeset and pinned by a refusal-envelope test plus a passthrough control. One declared file-surface increment: the dispatch-mandated docs-table row in content/docs/api/schema-reference.md (Zone 2 item 2) — one row, named in the PR body. The props-contract fixture authoring view:'agenda' (as never) pins the surviving runtime drop branch and stays.",
 "tests": "BEFORE (this tree, pre-change): CalendarViewSchema.safeParse({type:'calendar-view',view:'agenda'}) -> success=true; passthrough control (unknown key) -> true. AFTER: new pin calendar-view-mode-agenda-retired.test.ts asserts exactly one invalid_value issue on the 'view' path offering month/week/day, survivors full-green, unknown-key control still true. Post-commit union at HEAD e168a0a43 (clean tree, sha printed inside the run): 'Test Files 56 passed (56)' / 'Tests 590 passed (590)' for vitest run packages/types/ packages/plugin-calendar/ from repo root, plus @object-ui/types and @object-ui/plugin-calendar type-check green (scripts echoed; lock VERDICT command-exit 0, exit captured via redirect-then-$?). Ablation from the committed state, direction predicted first (3 red / 3 green): mutation = git checkout origin/main -- zod/complex.zod.ts, confirmed on disk by anchored grep of the enum line (0 -> 1); vitest resolves the schema via relative source import so no build leg applies; result 'Tests 3 failed | 3 passed (6)' — exactly the predicted split; trap-restored, restore confirmed by grep (1 -> 0) and clean git status. Rebuilt-dist reverse verification: tsc probe against packages/types/dist -> \"error TS2322: Type '\\\"agenda\\\"' is not assignable to type 'CalendarViewMode'\" with the 'week' control compiling clean under identical ambient noise. Gates by their own judgment lines: check:control-bytes '✅ OK (scanned 4807 tracked text file(s))', check:spec-symbols ✅, check:doc-types '✅ Every documented component type is registered.', check-changeset-presence ✅ (1 changeset declared), check-changeset-no-major ✅, check-changeset-fixed ✅, check:esm-specifiers ✅ (specifier leg), @object-ui/types lint '0 errors' (252 pre-existing any warnings). DECLARED NARROWING: check:doc-snippets not concluded locally — its preflight red is the known unbuilt-closure gauge ('The snippet program was NOT run'; kept naming more unbuilt packages after one bounded build round); the edited docs line is a prose table row, not a snippet; CI's built run is the verdict. Repo-wide lint/type-check farm likewise CI's.",
 "open_questions": [],
 "out_of_scope_findings": [
 "filed as #5783: dead i18n key calendar.agenda in all ten locale packs — no static reader, no dynamic calendar. head, no textual footprint; attached as sub-issue of #4730 (the dead-key backlog)",
 "filed as #5784: defaultView declares 'agenda' in ObjectCalendarSchema (objectql.ts:1981) and both zod twins (objectql.zod.ts:346, 617) while ObjectCalendar reads 'month'|'week'|'day' — same declared-vs-enforced class on a different declaration, needs its own clause-2 pass"
 ]
}

Generated by Claude Code

---

Generated by Claude Code