Fix lifecycle examples that violate the open-mode command contract #2201

Problem

The shipped planning lifecycle example adds actor/time attribution after the backticked Last command. The strict open-mode contract requires that field to end at the closing backtick. Following the example can therefore reject an entire research/plan safe-output batch, including the accompanying artifact.

Reproduction

1. Derive a Researched or Planned lifecycle body from the shipped lifecycle example, substituting the requested command.
2. Submit it with the corresponding artifact to the compiled open-mode guard.
3. The attribution suffix causes Squad open-mode lifecycle must describe only the requested research or plan.
4. Removing only the suffix allows the batch through the unchanged guard.

Expected repair

• Keep Last command command-only and put optional actor/time attribution on a separate Updated by line.
• Align canonical instructions, generated package workflows, and related documentation.
• Add template-derived research/plan coverage through the compiled guard and lifecycle writer, plus live-source mutation coverage restoring the rejected suffix.
• Preserve invalid-state and duplicate-command rejection without relaxing validator authority or changing deployment policy.

Working as agentic-workflows-dev (Agentic Workflows Engineer). Generic synthesized fixtures only.