diff --git a/src/views/workplace-collaboration-view.jsx b/src/views/workplace-collaboration-view.jsx
index e3c23b4c..f04f112d 100644
--- a/src/views/workplace-collaboration-view.jsx
+++ b/src/views/workplace-collaboration-view.jsx
@@ -302,10 +302,21 @@ function MeetingCard({meeting, myUserId, onRespond, onToast}) {
     {!isOrganizer ? (
       meeting.my_response && meeting.my_response !== 'pending' ?
         <footer><button type="button" className="meeting-responded" disabled>{RESPONSE_LABEL[meeting.my_response] || meeting.my_response}</button></footer> :
-        <footer className="meeting-response">
+        // Live-repro'd (round 12): this branch used to render regardless of `permissions.can_respond`,
+        // so a canceled meeting the viewer never responded to (my_response still 'pending', a normal
+        // state for a canceled invite -- canceling doesn't force every invitee to respond first) kept
+        // showing live-looking 拒绝/接受 buttons here. Clicking either got a 403 PERMISSION_DENIED from
+        // PUT .../my-response (confirmed against a real canceled meeting, mtg_0w2TnfQiqaMwy8Bj) --
+        // the request body/version were fine, the backend just correctly refuses to accept a response
+        // once a meeting can no longer be responded to. MeetingDetail already gates its own copy of
+        // these same two buttons on this exact flag (line ~406 below); this list card independently
+        // duplicates the buttons but had never adopted the same guard. Requirements 9.4 also calls for
+        // expired meetings to become read-only history, which this same flag should cover -- can_respond
+        // is a general "still actionable" signal, not canceled-specific.
+        (meeting.permissions && meeting.permissions.can_respond ? <footer className="meeting-response">
           <button type="button" disabled={busy} onClick={() => respond('declined')}>拒绝</button>
           <button type="button" className="primary" disabled={busy} onClick={() => respond('accepted')}>接受</button>
-        </footer>
+        </footer> : null)
     ) : null}
   </article>;
 }