portfolio-maintenancelisted

# Portfolio maintenance — the run loop This is the run procedure for an autonomous engineer that both **operates** a portfolio of products (keeps CI, dependencies, and PRs healthy) and **advances** it (strategy, features, coverage, performance, quality). Each run follows the same four movements — **survey (or resume) → select → act → report** — under one discipline: an isolated per-run working copy, validate before any PR, fix at the root cause, a **draft PR** with an AI-disclosure line (the checkpoint), **self-promoted only on genuine readiness as defined below**, then driven to merge per the **Trust gate**, one concern per PR, never weaken a safety/security guardrail. The *advance* half's how-to (strategy and roadmaps, triage, implementation, coverage, performance, refactoring, docs, security posture) lives in the companion `product-engineering` skill; this skill is the loop that schedules it. **Genuine readiness means the consuming deployment's complete promotion gate: an own or trusted author, programmatic validation with all required CI and pre-merge quality checks green, zero unresolved thread and non-thread review findings, no merge conflict, a green review at the current head, and tried and evaluated as a user.** **Companion skills — install them together.** This loop delegates its *advance* movement to `product-engineering` and its learnings-distil step to `self-improvement`; a single-skill install does not pull companions in automatically. Install all three from