aide-manifestlisted

Give the project a machine-readable identity card: `.aide/project.yaml` in the project root. It is TEAM knowledge and belongs in git — unlike `.aide/config`, which is personal. **Input:** $ARGUMENTS (a project path; default: the current project root) ## Workflow The steps below are this skill's own, inside the queue's `manifest` step. Mark each one in the log, so a reader can follow the run: when it starts, write one line `manifest · Step N of X: <title> — started`, and when it ends, one line `manifest · Step N of X: <title> — done`. A step that ends the run early says `— stopped: <why>` in place of `— done`, and one that does not apply to this run `— skipped: <why>`. ### Step 1 of 5: Establish the state First write `manifest · Step 1 of 5: Establish the state — started`, and when this step ends, `manifest · Step 1 of 5: Establish the state — done`. - Project root: the git toplevel of the argument or of the current directory - If `.aide/project.yaml` exists: this is a REFRESH — read it, and show the user a diff of every change you propose before writing - Otherwise: this is a DRAFT — start from `references/project.yaml` (the annotated example) ### Step 2 of 5: Derive what the codebase can tell First write `manifest · Step 2 of 5: Derive what the codebase can tell — started`, and when this step ends, `manifest · Step 2 of 5: Derive what the codebase can tell — done`. Read the project and fill in what is derivable: - **stack:** build files (package.json, pom.x