grow-threadslisted

# Threads growth loop — one autonomous tick Growth skills are **split per platform** — tactics, tools, and state differ platform by platform. This skill is Threads-only; grow-instagram, grow-youtube, and grow-tiktok get added later on the same skeleton (plan = standing authorization · judgment-based publishing + review gate · idempotent state). That's also why the state path is scoped to `growth/threads/`. One invocation = one growth-cycle tick. The harness handles repetition: ``` /social-flow:grow-threads <channel> init # once — confirm the plan (HITL) /loop 30m /social-flow:grow-threads <channel> # 30-min autonomous loop (the user picks the interval) ``` A 30-minute interval is the recommendation — it fits two inbox checks inside the golden hour (first 60 minutes). The loop runs while the session is open. Closing the session stops it; the next `/loop` resumes it (state.json carries over). **Premise — why this structure**: Threads judges reach post by post, not by follower count, and reply engagement plus early response speed are the strongest signals. So the tick's priorities are ① reply fast to replies received → ② observe performance → ③ join other people's conversations → ④ new posts. There is no fixed cap on publishing frequency — **judgment decides how many posts go out, not a count rule**. Join any conversation where there's something real to contribute, and write whenever a topic gives you something to say. Conversely, a tick that publishes nothing because