[rockfordlhotka]

Closes #38.

When none of the proposed times work, someone invited can suggest others. The organizer gets an email and decides whether to add each time to the poll or dismiss it.

What changes

• Suggesting: a new suggest_slots MCP tool, and a "None of these work?" form on the voting page.
  • Up to 5 times per request, and at most 5 waiting per person, which also limits the email one person can cause.
  • Times are local wall time plus an IANA zone, as with slots. The voting page fills in the viewer's own zone when JavaScript is on, and uses the organizer's zone without it.
  • One person's requests are saved one at a time, under a lock on their participant rows, so a double submit can't save duplicates.
• Organizer email: one "Suggested time" email per request that adds suggestions. It lists the times in the organizer's zone with a link to the event page, and has plain-text and HTML bodies.
• Adding: propose_more_slots takes a new suggestionIds parameter, and slots is now optional. On the event page this is "Add to the poll" / "Add all".
  • It goes through the existing propose path, so the version check, the 20-time limit, reopening an expired or finalized event, and the "New times" email to every invitee all still apply.
  • A suggested time is built from its stored local time, seconds included. It is resolved leniently, like the time-zone job (new SlotTimeResolver.ResolveStored, which the job now uses too).
  • A time already in the round is added once, whether it is the organizer's own or the same moment suggested by two people. Every waiting suggestion of a time the round adds is marked added.
• Dismissing: a new dismiss_suggestions tool, and a "Dismiss" button on the event page.
  • It emails no one. The person who suggested the time sees "not added by the organizer" on their voting page, even after voting closes.
  • It takes the version, like any organizer edit.
• Visibility: the organizer sees every suggestion and who made it, and the /events dashboard shows how many are waiting. A participant sees only their own suggestions, with their status.
• Retrying is safe: a time already on the poll, or already suggested by the same person, isn't suggested again, and a notice says so. A dismissed time can't be suggested again.
• Email subjects: every event email's subject is now cut to the outbox's 256 characters. A long name plus a long title could overflow the limit and fail the change that queued the email. The invitation and "can't make any time" subjects had the same problem.
• Data: a new SlotSuggestion entity and the SlotSuggestions migration. Suggestions are their own rows, so, like votes, they don't change the event's version. They are deleted with their event.
• Agents: the server instructions and the handle_scheduling_requests prompt now cover suggestions.
• Docs: a new "Suggested times" section in docs/design.md, plus updates to the data model, tools, email, web UI, jobs and audit sections.

Choices worth a look

• The person who suggested a time isn't recorded as voting for it. They vote on it like everyone else once it's added.
• Withdrawing a time still sends no email, as before.

Testing

dotnet test Scheduler.slnx: Core 124, Data 170 and Web 93 tests pass, after merging main.

New tests:

• SuggestionTests: suggesting, visibility, retries, concurrent requests, limits, adding (including duplicate instants, seconds and times the time-zone rules now skip), dismissing, reopening an expired event, purge.
• Email-wording and subject-length tests in Core.
• A voting-page form test, which also checks the suggestion list after voting closes.
• A bUnit test of Add and Dismiss on the event page.

SchedulerApp.Browser.SubmitFormAsync can now post a specific form, because the voting page has two.

🤖 Generated with Claude Code

https://claude.ai/code/session_01NZSHCijStZzTcMJSBYoY6t

[Copilot]

🟡 Changes recommended

Unresolved concurrency, slot-resolution, status-visibility, and email-length defects can create duplicate suggestions, fail or mis-time slot additions, hide organizer decisions, and roll back submissions.

6 open issues

• Bound notification subjects to the outbox limit · New
• Serialize suggestion checks and inserts to prevent concurrent duplicates · New
• Resolve stored suggestions consistently after time-zone updates · New
• Preserve seconds when converting suggestions to slots · New
• Deduplicate selected slots by instant before adding suggestions · New
• Show existing suggestions when voting is closed · New

1 file not reviewed

• src/Scheduler.Data/Migrations/20261103210630_SlotSuggestions.Designer.cs: Generated file

What changed in this PR

Adds the invitee-suggestion workflow from #38 across the scheduling service, MCP tools, and web UI. Invitees can suggest alternative times; organizers receive an email and can add those times to the poll or dismiss them.

Changes:

• Adds persisted suggestions, participant-specific visibility, limits, and organizer decisions.
• Connects suggestions to voting and organizer pages, MCP tools, and plain-text/HTML notifications.
• Adds workflow tests and documents the behavior.

File	Description
tests/​Scheduler.Web.Tests/​VotingPageTests.cs	Tests submitting suggestions through the voting page.
tests/​Scheduler.Web.Tests/​SchedulerApp.cs	Supports posting a specific named form.
tests/​Scheduler.Web.Tests/​OrganizerPageTests.cs	Tests organizer add and dismiss actions.
tests/​Scheduler.Data.Tests/​VotingTests.cs	Updates proposal calls for suggestion IDs.
tests/​Scheduler.Data.Tests/​SuggestionTests.cs	Covers suggestion permissions, limits, decisions, notifications, and purge.
tests/​Scheduler.Data.Tests/​SchedulingJobsTests.cs	Updates proposal calls for the extended API.
tests/​Scheduler.Data.Tests/​OrganizerTests.cs	Updates organizer tests for suggestion IDs.
tests/​Scheduler.Data.Tests/​OrganizerLimitTests.cs	Adapts email-limit tests to the extended API.
tests/​Scheduler.Core.Tests/​EmailComposerTests.cs	Tests suggested-time email wording and time zones.
src/​Scheduler.Web/​wwwroot/​app.js	Defaults suggestion inputs to the viewer’s zone.
src/​Scheduler.Web/​Mcp/​SchedulingTools.cs	Exposes suggestion and dismissal tools; extends proposals.
src/​Scheduler.Web/​Mcp/​SchedulingPrompts.cs	Adds suggestions to the participant workflow.
src/​Scheduler.Web/​Mcp/​SchedulerMcpOptions.cs	Explains suggestion handling to agents.
src/​Scheduler.Web/​Email/​Templates/​EventEmail.razor	Renders suggested times in HTML emails.
src/​Scheduler.Web/​Email/​HtmlEmailComposer.cs	Composes organizer suggestion notifications.
src/​Scheduler.Web/​Components/​Pages/​Vote.razor	Adds suggestion submission and status display.
src/​Scheduler.Web/​Components/​Pages/​Events.razor	Displays pending suggestion counts.
src/​Scheduler.Web/​Components/​Pages/​EventDetails.razor	Adds organizer controls for suggested times.
src/​Scheduler.Data/​SchedulingService.cs	Implements suggesting, dismissing, adopting, and visibility.
src/​Scheduler.Data/​SchedulingJobs.cs	Recomputes pending suggestions after time-zone updates.
src/​Scheduler.Data/​SchedulerDbContext.cs	Maps suggestion rows, indexes, and relationships.
src/​Scheduler.Data/​Migrations/​SchedulerDbContextModelSnapshot.cs	Records the updated persistence model.
src/​Scheduler.Data/​Migrations/​20261103210630_SlotSuggestions.Designer.cs	Defines the migration’s target model.
src/​Scheduler.Data/​Migrations/​20261103210630_SlotSuggestions.cs	Creates the suggestions table and indexes.
src/​Scheduler.Core/​Services/​ISchedulingService.cs	Defines suggestion operations and extended proposals.
src/​Scheduler.Core/​Services/​Contracts.cs	Adds suggestion views and pending counts.
src/​Scheduler.Core/​Model/​SlotSuggestion.cs	Defines the persisted suggestion entity.
src/​Scheduler.Core/​Model/​SchedulingEvent.cs	Adds the event’s suggestion collection.
src/​Scheduler.Core/​Model/​Enums.cs	Defines suggestion decision states.
src/​Scheduler.Core/​FieldLimits.cs	Adds the pending-suggestion limit.
src/​Scheduler.Core/​Email/​PlainTextEmailComposer.cs	Adds suggestion notification text and shared wording.
src/​Scheduler.Core/​Email/​IEmailComposer.cs	Adds the suggestion notification contract.
docs/​design.md	Documents the workflow and its system integration.

_{Review effort: Balanced}