#92 PM skill: source deploy.md from project git root, push after first successful deploy

[Anonymous]

Originally created by: kumaakh

Problem

The PM skill currently maintains `deploy.md` in the PM project folder (e.g. `apra-fleet-projects/<project>/deploy.md`). This means:</project>

• The runbook lives outside the project repo and is not version-controlled alongside the code
• It must be manually kept in sync — in this sprint the PM folder had a stale `npm install -g .` runbook while the source repo had the correct binary-based runbook
• A new PM session or a different operator has no way to discover the authoritative runbook

Desired behaviour

1. Source from project git root first. When PM needs to deploy, check for `deploy.md` at the project git root (e.g. `C:/akhil/git/apra-fleet/deploy.md`). If present, use it as the runbook.

2. Fall back to PM folder. If not in git root, fall back to `<project-folder>/deploy.md` as today.</project-folder>

3. Develop and push on first success. If no `deploy.md` exists anywhere, PM should:

4. Work with the user to draft one interactively during the first deploy
5. After a successful deployment, commit and push `deploy.md` to the project git root on the project's base branch

6. Also copy it to the PM folder for local caching

7. Update on change. If PM deviates from the runbook (workaround, new step), prompt to update and re-push.

Motivation

Deploy runbooks are project artifacts, not PM session state. They should live in the repo, be reviewed like code, and be reusable across sessions and operators.

Acceptance criteria

• `skills/pm/single-pair-sprint.md` deploy section references checking project git root for `deploy.md`
• PM does not rely solely on the PM folder copy
• First successful deploy results in a committed `deploy.md` in the project repo root

[Anonymous]

Originally posted by: kumaakh

Fixed. deploy.md now lives in the project git root (e.g. C:/akhil/git/apra-fleet/deploy.md) and PM reads it from there. PM skill deploy step references <project>/deploy.md which resolves to the git root file. Verified working in production deploy of PR [#128].

[Anonymous]

Ticket changed by: kumaakh

• status: open --> closed