observation: console FormPage does not resolve the `current_user` seed the way `schemaDefaults.ts` has since #5683 — correct, but the operator cannot see the attribution before submitting

[claude]

Found while implementing #5727 (guarding readPrefill's seeding with isRuntimeDefault). Recording a parity gap, not a defect — after #5727 the console behaves correctly, just not as helpfully as the sibling renderer.

Measured on origin/main 1939c9610.

What the sibling chain does that this one does not

@object-ui/plugin-form's schemaDefaults.ts skips runtime defaults when seeding, with ONE documented exception (#5683): current_user is resolved, not seeded literally, when the caller threads a SeedContext:

} else if (isCurrentUserSeedField(f) && ctx?.currentUserId) {
 defaults[name] = ctx.currentUserId;
}

The argument there is that this is not a second default contract but a preview of the same one: the engine's current_user resolution is the acting user's id (applyFieldDefaults -> execCtx.userId), and the session already knows that id exactly, so seeding it and omitting it are equivalent by construction. The type gate mirrors the spec's own authoring rule (user, or lookup with reference: 'sys_user').

apps/console/src/components/FormPage.tsx's readPrefill takes no such context: after #5727 a current_user field simply opens empty on both console form routes and the server stamps the id at insert. Correct, but the operator does not see who the record will be attributed to before submitting — which is the gap #5683 closed on the other chain.

Why this is filed as an observation, not a bug

Nothing is stored wrong and nothing is suppressed; the outcome is identical, only later and invisible. It also is not free: readPrefill is a pure function taking (fields, search, record), so threading usePermissions().userId into it is a signature change on a seam this repo has been keeping narrow, and the public /f/:slug route is anonymous — there is no acting user there, which the sibling handles by seeding nothing. Whether that parity is worth the seam is a triage call.

Prior art to reuse rather than re-derive if it is taken up: isCurrentUserDefaultToken from @objectstack/spec/data and the isCurrentUserSeedField type gate in packages/plugin-form/src/schemaDefaults.ts.

Related: #5727, #5683, #4047, #4068.

---

Generated by Claude Code

[os-zhuang]

Triage (first-touch grading): closing not_planned. Reasons, recorded so reopening is cheap: (1) behavior after #5727 is correct — nothing stored wrong, nothing suppressed; the gap is purely that the operator sees the current_user attribution only after submit; (2) the cost is real and named on the card — a signature change on the deliberately narrow readPrefill seam plus an anonymous-route edge on /f/:slug; (3) zero measured pull — no operator-facing report of confusion. Reopen triggers: an operator/user report of attribution confusion on console forms, or any change that threads a SeedContext/user identity into readPrefill for another reason (at that point the parity comes nearly free — reuse isCurrentUserDefaultToken + isCurrentUserSeedField per the card's prior-art notes). Maintainer veto of this closure reopens it, as with any triage grading.

---

Generated by Claude Code