record-project-memorylisted

## Constraints - Apply `@rules/compound-engineering/general.mdc` *Compound Memory (per project)* — this skill is the write side of that rule; it owns the promotion bar, the curation pass, and the file convention defined there. - Apply `@rules/git/general.mdc` - **Write-only to the memory file.** This skill modifies exactly one file: `docs/memory/PROJECT_MEMORY.md` in the project being worked on. It never edits production code, tests, configuration, `CLAUDE.md`, or `.cursor/rules/project.mdc`. - **Never record secrets, credentials, tokens, or PII** — apply the same prohibition the security rules apply to logs and tracker comments. When a lesson can only be stated with a secret, generalize it until the secret is gone or drop the entry. - **Per-project only.** The memory file lives in the target project, never in this shared rules package. Never write a project lesson into `rules/**` as a global rule. - Output must be in English (the memory file is a code artifact, like `CLAUDE.md`). ## Use when - A `@skills/resolve-issue` or `@skills/process-code-review` run has converged (review loop at 0 Critical / 0 Moderate) and is about to publish its final report. - An orchestrator (daidalos) reaches its final report after the convergence gate. - The user explicitly asks to record a lesson into project memory. Do **not** run this skill mid-task, before convergence, or for a task that produced no durable lesson. ## Inputs - `CONVERGED_CONTEXT` — required. The converged task context: wha