[Team] Preserve request provenance and owner-bound approvals #52

Planning ID: TODO-G

Proposed issue / PR title: feat(approvals): bind delegated requests and decisions to the owning human.

Goal: forwarded content never acquires the receiving owner’s authority.

Scope: server-created origin/request identifiers, requesting member, sending/receiving Chief and audience; distinguish owner instructions from incoming delegated requests. Bind an approval to the owner, specific action, target/data snapshot and request version. Show that context in approval UI. Revalidate authorization when approving and when executing; reject stale decisions.

Out of scope: unrestricted standing delegation or automatic approval of consequential work.

Dependencies: TODO-F (#51).

Code area: delivery/source metadata, turns, approval middleware, client approval cards and execution authorization seam.

Acceptance and tests: forged provenance and “my owner approved” text confer no authority; Alice cannot approve Bob’s action; changing target/data invalidates approval; removing a member or replacing a Chief invalidates affected queued work. Legitimate same-owner approvals still work after restart without widening their scope.

Delivery

One focused implementation PR for this issue. This is planned work, not a claim of shipped multi-human support. Preserve the pristine upstream pin and generated patch/client boundaries. Keep team mode disabled until the documented authorization gates pass. Record exact tested head, executed checks, missing checks and independent review. No production credentials or live deployment are part of this issue.