duplicate-bodies stays red after #7864: three identical stubs in the trios tasks port (assign/status/update_status) #7873

After #7864, duplicate-bodies stays red on master because of a second group, from d4f74f8 (#7491):

a body written under assign is now copied [3] time(s) and was in no ledger

specs/port/trios/crates/trios-server/src/mcp_endpoints/tasks.t27 ports assign, status and update_status from trios, and all three return the same stub, TaskReply{task_id: "task-123", status: "assigned"}. The stubs predate #7491. At d4f74f8^, dupe_scan --like on this file reported "no function body long enough to compare". Renaming Value to TaskReply for the types ratchet made the bodies long enough to be measured.

So the copy is not new. It is an unfinished port: three endpoints that answer the same thing whatever they are asked. Recording the group with dupe_scan --bless turns the gate green and changes no behaviour. The real fix, porting the three bodies from gHashTag/trios:crates/trios-server/src/mcp_endpoints/tasks.rs, is a port task of its own and lowers the ledger when it lands.

Generated by Claude Code

User Scenarios

• Given the duplicate-bodies gate is red on master due to three identical stub bodies in specs/port/trios/crates/trios-server/src/mcp_endpoints/tasks.t27, When the duplicate group is recorded in the ledger with dupe_scan --bless, Then the duplicate-bodies gate passes (exit 0) without changing any behavior.

Requirements

• FR-001: The duplicate body group for assign, status, and update_status in specs/port/trios/crates/trios-server/src/mcp_endpoints/tasks.t27 MUST be blessed into the ledger.
• FR-002: The duplicate-bodies gate MUST pass (exit 0) after the blessing.
• FR-003: No functional code in specs/port/trios/crates/trios-server/src/mcp_endpoints/tasks.t27 MUST be modified.

Success Criteria

• dupe_scan --bless specs/port/trios/crates/trios-server/src/mcp_endpoints/tasks.t27 exits 0 and records the duplicate group
• duplicate-bodies gate check exits 0
• specs/port/trios/crates/trios-server/src/mcp_endpoints/tasks.t27 remains functionally unchanged (three stubs still return TaskReply{task_id: "task-123", status: "assigned"})

Boundary

• specs/port/trios/crates/trios-server/src/mcp_endpoints/tasks.t27