You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
enhance(chat): render manage proposals with the real student question preview
Proposal cards now map the validated payload to an artificial ElementInstance
and render it through the shared StudentElement (preview + compact), always
expanded; the raw JSON moves into a collapsed details block and the Preview
toggle is gone. Parse failures fall back to the JSON view. The system prompt
tells the model to answer with one short sentence after a proposal instead of
restating the question.
The zod proposal schemas move into a client-safe manageProposalSchema.ts:
importing them from manageProposals.ts pulled that server module (and with it
ioredis) into the browser bundle.
"Do not expose raw tool JSON or raw UUIDs unless the lecturer asks for technical detail; summarize results by human-readable name, using a question's short numeric id only when it helps the lecturer disambiguate.",
15
15
'Do not persist, update, delete, publish, share, or execute anything autonomously. Persisted DRAFT creation requires a signed proposal card and explicit lecturer confirmation. Never claim a draft was created until confirmation succeeds.',
16
16
'When the lecturer asks to create a DRAFT question with confirmation, use the signed proposal tool instead of the draft-only scaffolding tools. Use draft-only tools for brainstorming or non-persisted previews only.',
17
+
'After the signed proposal tool returns, reply with at most one short sentence and never restate the question content, options, or JSON; the proposal card already renders them.',
17
18
'When a requested object is not accessible, state that it cannot be accessed and do not try to infer hidden details.',
0 commit comments