Case study: PLT-1224 — doc updates and PR ship (agent run)
Date: 2026-04-06
Linear: PLT-1224
PR: #529 (branch uttam/plt-1224-create-executive-q2-planning-operating-model-and-repo-plan)
This records what the Cursor agent actually did in the session summarized as “ship and PR this resource and the operating stuff,” so future runs do not assume live Operating MCP/API calls when the work was repo + GitHub only.
Tools and surfaces used
| Action | Mechanism |
|---|---|
| Inspect branch / commits | git status, git log |
Resolve divergence from main | git fetch, git merge origin/main |
| Resolve rename conflicts (Operating files) | Stage files at post-restructure paths: knowledge/delivery/plans/active/, knowledge/executive/plans/planned/, knowledge/standards/03-knowledge/engineering/setup/operating-api-setup.md |
| Push | git push (Husky pre-push ran apps/platform build because main brought in platform changes—not because Operating files touched the app) |
| PR metadata | gh pr view, gh pr edit (title + body with Summary / Changes / Impact / Related) |
| Merge attempt | gh pr merge → blocked by branch protection; auto-merge disabled on repo |
Operating MCP / REST in that run
No call_mcp_tool invocations to the Operating server and no curl to api.operating.app were part of that handoff. The “Operating stuff” was already in the branch as markdown and standards; the agent’s job was integrate main, fix paths, push, and refresh the PR description.
Prior work (same branch, earlier commits)
Earlier commits on the same branch (documented in PR history and execution reports) describe live Operating changes—positions, allocations, project archive/create via API/MCP—per knowledge/delivery/plans/active/operating-changes-executed-2026-03-25.md and related files. Those are the right place to see what changed in Operating, not this case study.
Takeaway for agents
- “Ship Operating docs” often means git + GitHub + markdown path alignment, especially after a monorepo knowledge restructure.
- “Change Operating data” requires MCP/API + logging in the delivery plans active execution artifacts.
- Always state which of the two you performed in the chat summary or execution log.