v0.2.0 — memory recall & hardened orchestration

Highlights

• Memory recall at task start — project memory ($STARKS_MEMORY_DIR/<project>/) is now read before grilling, so settled questions are never re-asked. Deterministic project naming (repo basename, fallback to _index.md) prevents memory fragmentation.
• Structural anti-recursion on the Codex reviewer side — the cross-review invocation disables the starks skill itself via skills.config, so the reviewer cannot even see it. The STARKS_CROSS_REVIEW env guard remains as a second layer.
• Structured two-stage review — new prompts/spec-review.md and prompts/code-review.md templates with file:line / blocking-or-suggestion findings.
• Bounded rework loop — at most 2 rework rounds, then stop and escalate to the user.
• Safer parallel sub-agents — disjoint write-sets required; worktree isolation mapped for both platforms; per-slice pipelined review.
• Leaner trigger description — frontmatter no longer summarizes the workflow (it misled models into treating cross-review as mandatory; it is user-opt-in).
• Memory writer keeps the last 5 dated entries instead of overwriting history; durable preferences go to platform-native memory.
• Cross-reviewer may browse the repo read-only; timeout pinned to ~10 min.
• CI: lint runs on every push/PR.

Install

git clone https://github.com/uniStark/starks_skill.git
cd starks_skill
bash scripts/install.sh

Full design rationale in docs/DESIGN.md.