feat(meta): let pull-meta bootstrap a fresh clone

[amustafa]

What

sr pull-meta now works in an uninitialized clone, so it is the bootstrap path for a fresh clone of an sr-managed repo.

Why

Git does not fetch custom refs, so a fresh clone of an sr-managed repo has no local stackr metadata — and the config naming the remote lives inside that metadata. Gating pull-meta on being initialized was a catch-22: the command that gets you out of the uninitialized state refused to run until you were initialized.

How

• cmd/meta.go drops the RequireInit gate on pull-meta (deliberately — it is the way out of the uninitialized state).
• engine.PullMeta resolves the remote without local config when bootstrapping: the sole configured remote when unambiguous, else origin. After a bootstrap pull it runs the store's Init to create the local scaffolding (undo/rollback dirs) the rest of stackr expects, and errors clearly when the remote has no metadata at all.
• ErrNotInitialized now points at sr pull-meta as the alternative to sr init for repos that already use stackr.

🤖 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: d15380d3-549d-462a-834b-3dca43123319

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.}