v1.14.0 — top-level agent_name on create payloads

Ports the canonical stride plugin's W1684 change (released as stride v1.37.0) into the Pi extension — the last of the six-plugin fleet, after stride-codex (v1.25.0), stride-copilot (v2.26.0), stride-gemini (v1.36.0), and stride-opencode (v1.28.0).

Added — every documented create payload carries a top-level agent_name (W1694)

stride-creating-tasks, stride-creating-goals, and both decomposer docs — skills/stride-task-decomposer/SKILL.md and extensions/subagent-dispatch/agents/stride-task-decomposer.md, which carry the contract in parallel — now document a top-level agent_name on every create request: beside the task root key for POST /api/tasks and beside the goals root key for POST /api/tasks/batch, set to the exact same plain agent name the extension already sends as agent_name on claim and complete ("Pi", never the ai_agent:<model> token form).

Per-task created_by_agent is forgotten in practice and cannot be backfilled (PATCH rejects it), so tasks lost their attribution permanently and the /agents feed rendered them with a ? avatar. The root-level param is the always-sent fallback the server reads.

Both creation skills gain the full five-step server resolution order (explicit created_by_agent → token ai_agent:<model> → top-level agent_name → token's last agent name → unset), an agent_name row in their field tables, and an explicit note that agent_name is display metadata only — never an authorization signal.

Fixed — stride-creating-tasks documented the single-create body without its task root key

The skill's complete example was a bare task object, but POST /api/tasks requires a {"task": {...}} envelope and returns 422 Missing 'task' key without it. A new Request Envelope section shows the wrapper with agent_name as its top-level sibling, and the Quick Reference heading now names the block as the value of the task key rather than the request body; the single-goal format in both decomposer docs is corrected the same way. The extension inherited this defect from the canonical plugin, where W1684 fixed it.

Scope

Documentation-only. The extension's TypeScript builds no create payload — the hook bridge handles curl matching, changed_files capture/PUT, and the after_goal PATCH, while the agent itself issues the create request. skills/stride-workflow/SKILL.md references the create endpoints in prose only and embeds no payload shape, so it is unchanged.

Testing

npm test (node --test) — 213 pass, 0 fail, unchanged: no .ts file was touched.

Backward compatibility

Fully backward compatible, and safe to ship ahead of the server. No .ts, hook, .stride.md, env-var, or .stride_auth.md change. Unknown top-level keys are ignored by older servers. created_by_agent guidance is unchanged and still highest precedence — the new param is a fallback, never a replacement.