feat(init): adopt existing remote stackr metadata instead of initializing fresh

[amustafa]

What

sr init in a clone whose remote already holds stackr metadata now adopts that shared state instead of creating blank local state.

Why

Creating blank state in a second clone silently shadows the shared graph: two clones then disagree about the stack, and the first push-meta from the blank one clobbers or forks the shared metadata. Init is the natural first command a new clone runs, so it should notice the metadata and do the right thing.

How

• Before initializing fresh, runInit probes each remote for the stackr metadata ref (new Runner.RemoteHasRef, an ls-remote — unlike RemoteBranchExists it needs no prior fetch, since custom refs are never fetched by default). On a hit it announces the adoption and delegates to engine.PullMeta.
• Best-effort by design: an unreachable remote is treated as one without metadata, so offline sr init still works.
• --reset keeps meaning "start over deliberately" and skips the adoption probe.

Stacked on the pull-meta bootstrap PR, whose semantics this relies on.

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 67dc8556-69f0-47f7-b122-8ac10977b7c1

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}