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
{{ message }}
Repository navigation
A write-secretary cannot send invitations for an event in the owner's calendar; the model invented Telegram ids for named invitees #909
Same incident (2026-10-31, revision bb7a9d4). send_invitation had no owner_id, so a write-secretary could not invite, resend, cancel or read the roster for an event in the owner's calendar. The sharing tools now accept owner_id. The recipient-identity change only treats the requester's own Telegram id as verified and adjusts the rejection hints for delegated calendars; invented ids are still refused by the existing recipient verification.
Why (motivation)
Secretaries manage calendars for owners and must be able to invite people.
User impact
A secretary managing someone else's calendar could not invite anyone, and the assistant could have sent invitations to unrelated strangers using made-up ids.
Cost of inaction
Secretary invitations stay broken and may reach the wrong people.
Acceptance criteria
A write-secretary can invite, resend, cancel and read the roster for the owner's own personal events
Rejection hints for a delegated calendar do not send the model to the picker, and the requester's own id is accepted as verified
After the merge, production reports the merged revision on /health and the running image, and a live or stage check shows a secretary confirmation with several invitees ending in a delivered, readable reply (production still runs bb7a9d4 on 2026-11-01)
Shipped: merged via #940.
Merge commit: 4b2372d
This does NOT close the ticket — acceptance still needs proof. Run task read #909 for the outstanding criteria, then task check/task done.
Shipped and deployed: PR 940, merge 4b2372d (version 0.3.2). A write-secretary can invite, resend, cancel and read the roster for the owner's own personal events (owner_id); group events and events somebody else organises are an explicit scope denial; recipient identity checks are unchanged. Tests: sharing-secretary-invitation.test.ts, sharing-secretary-invitation-scope.test.ts, sharing-failure-paths.test.ts. Deployed: the odroid runs the merge SHA (image tag, revision label, receipt, /health ok, /ready 'ok (unverified)', no level 50+ log lines). NOT verified live: criterion 3, a secretary confirmation with several invitees ending in a delivered, readable reply; that needs an owner-authorised live test with a second account. The ticket stays open for it. Open: #910, #915, #918, #922.
Activity
fix(sharing): a write-secretary invites, resends, cancels and reads r…
fix(ai,sharing): long ask_user options reach the user, a write-secret…
alex-mextner commentedon Nov 4, 2026
Shipped: merged via #940.
Merge commit: 4b2372d
This does NOT close the ticket — acceptance still needs proof. Run
task read #909for the outstanding criteria, thentask check/task done.alex-mextner commentedon Nov 4, 2026
Shipped and deployed: PR 940, merge 4b2372d (version 0.3.2). A write-secretary can invite, resend, cancel and read the roster for the owner's own personal events (owner_id); group events and events somebody else organises are an explicit scope denial; recipient identity checks are unchanged. Tests: sharing-secretary-invitation.test.ts, sharing-secretary-invitation-scope.test.ts, sharing-failure-paths.test.ts. Deployed: the odroid runs the merge SHA (image tag, revision label, receipt, /health ok, /ready 'ok (unverified)', no level 50+ log lines). NOT verified live: criterion 3, a secretary confirmation with several invitees ending in a delivered, readable reply; that needs an owner-authorised live test with a second account. The ticket stays open for it. Open: #910, #915, #918, #922.