update guides for dev loop

[michaelneale]

just agents/docs

Summary by CodeRabbit

• Documentation
  • Updated build and release documentation to clarify native runtime configuration options and release path defaults.
  • Added guidance distinguishing standard development workflows from release distribution and validation testing.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0f22c765-3ebe-4d94-8419-cd1ee17def4a

📥 Commits

Reviewing files that changed from the base of the PR and between 2b8c41f and 013a2b4.

📒 Files selected for processing (3)

• AGENTS.md
• Justfile
• docs/design/NATIVE_RUNTIMES.md

---

📝 Walkthrough

Walkthrough

Documentation across AGENTS.md, Justfile, and docs/design/NATIVE_RUNTIMES.md is updated to clarify that just release-build defaults to MESH_LLM_DYNAMIC_NATIVE_RUNTIME=1, distinguish the release packaging path from the branch-local ABI development loop, and add a "Development Loop Boundary" section to the native runtimes design doc.

Changes

Dynamic Native Runtime Dev/Release Boundary Documentation

Layer / File(s)	Summary
NATIVE_RUNTIMES.md: Development Loop Boundary section docs/design/NATIVE_RUNTIMES.md	Inserts a new "Development Loop Boundary" subsection specifying that branch-local native/Skippy ABI changes should be iterated with just build, dynamic runtime artifacts are for release/SDK/installer validation requiring exact skippy_abi match, and MESH_LLM_DYNAMIC_NATIVE_RUNTIME=0 just release-build runs release-mode testing with embedded branch-local native libraries.
AGENTS.md and Justfile: release-build and ABI guidance AGENTS.md, Justfile	Updates the "Building" section in AGENTS.md and the Justfile comment to describe the dynamic native runtime default; adds a native-ABI development note warning against testing new ABI symbols against downloaded release runtimes; clarifies under "llama.cpp ABI Patch Queue" that the dynamic path is not the normal ABI/patch-queue development loop.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'update guides for dev loop' is vague and generic. While it references the development loop, it doesn't specify what aspect of the guides was updated or the actual substantive changes (clarification of dynamic native runtime behavior, development boundary distinctions, etc.).	Consider a more specific title like 'clarify dynamic native runtime and development loop boundaries in guides' to better convey the actual changes.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch micn/devloop-docs

---

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