Prevent silent truncation of Squad activation label operations #1961

Parent: #1957

Problem

The add-labels safe-output maximum may be interpreted or enforced differently across calls and individual labels. A large supported activation must not silently lose label operations while still reporting success.

Scope

Define, configure, and enforce capacity for the documented maximum Squad activation size.

Success criteria

• The maximum documented activation size and worst-case number of label operations are calculated and recorded in tests or workflow rationale.
• Safe-output limits accommodate that worst case with an explicit bounded margin.
• The workflow distinguishes limits on output items/calls from labels per call.
• If an activation exceeds any supported limit, the run emits an explicit incomplete/failure result identifying affected work items.
• No cap overflow is represented as a clean successful activation.
• Self-validation compares expected activated items with targeted label operations.
• Boundary tests cover the maximum supported size and one-over-limit behavior.
• Strict gh-aw compilation and targeted tests pass.

Out of scope

Changing the planning hierarchy’s product limits or distributing the post-activation checker.