aih-updatelisted

## Task Update the local aihaus installation by pulling the latest package from the remote git repository. Fully autonomous — fetches, compares versions, applies changes, re-links, and reports what changed. $ARGUMENTS ## Flags - `--check` — Only check if an update is available. Do not apply. - `--force` — Skip version comparison, always pull and apply. - `--session-log <milestone-slug>` — M004 story L post-hoc retrospective. Skip update logic; generate `.aihaus/milestones/<slug>/execution/SESSION-LOG.md` from `pkg/.aihaus/templates/SESSION-LOG.md`. Fill Timeline/Friction/Wins/Ideas/Artifacts/Hand-off from on-disk artifacts (RUN-MANIFEST.md, CHECK.md, VERIFICATION.md, INTEGRATION.md, reviewer reports, `.claude/audit/*.jsonl`, self-evolution additions). Opt-in only (F-M5); template H2 headers load-bearing — smoke-test enforces. - No flag — Default: check version, pull if newer, apply, re-link. --- ## Phase 1 — Detect Package Source ### 1. Find the aihaus package repository Check these locations in order: 1. If `.aihaus/.install-source` exists, read the remote URL from it. 2. If `.aihaus/` is a symlink, resolve it to find the package root, then check `git -C <pkg-root> remote get-url origin`. 3. If a `pkg/` directory exists in the current repo (dogfooding mode), use the current repo's remote: `git remote get-url origin`. 4. If none found, ask the user: "Where is the aihaus package repo? Provide a git URL or local path." Store as `PKG_REMOTE` and `PKG_LOCAL` (l