{"content":"GT#87 observation fix batch 4/4 (P2-4): member-clause extraction reads all @clauses and attaches floating trailing deadlines. Two systematic clock-loss shapes observed in GT#87: (a) the chair greeted a member at the message top and dispatched them in a later numbered paragraph - first-mention-wins clause extraction read the tagless greeting, and the 45m in the actual dispatch clause was silently dropped (the acceptance seat ran clockless); (b) the deadline written as a trailing standalone paragraph after a blank line - a completely natural chair format - stopped the clause at the boundary, so the 20m follow-up and the 140m biggest-baton implementation deadline were never reachable by the parser. Fix (commit 1bc602b0): extractMemberDispatchClause now scans EVERY @-mention clause and prefers the first one carrying a [DEADLINE:] tag; when none of the member's clauses carries a tag, it attaches the first FLOATING deadline segment that follows - a blank-line-separated block with a tag but no @-token, which cannot belong to another member's clause by construction. Cross-member isolation is preserved (another member's @-clause is never borrowed); the bare-name branch keeps GT#72 wake semantics with the same attachment. Combined with the address gate (batch 2) and the clock-hygiene fixes (batch 3), every deadline stated in GT#87's dispatches would now parse, arm on the right member, and die on completion. Full group-task suites green (270 + 249 tests).","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}