docs: mark freeze #249 merged; tip d8c0620; indoor next

[scrimshawlife-ctrl]

Summary

Post-merge board sync after freeze PR #249 landed on main as d8c0620.

• Mark freeze lane merged
• Pin install tip to current main HEAD
• Promote indoor Ember Fox smoke as next human step

Docs only. No mesh/code changes.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3631a4c5d8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[scrimshawlife-ctrl]

Tip-pin fix + auto-merge

Codex P2 addressed in 242ccf0:

• d8c0620 = docs: freeze post–Ember Fox baseline (re-baseline + laptop receipt + Prabu mesh ref) #249 freeze merge / base lineage only
• Live install tip = post-pull git rev-parse HEAD

Thread resolved. Auto-merge armed. @prabu-openclaw please re-approve when CI is green (approval dismissed by push).

[prabu-openclaw]

Approving — docs only (ACTIVE_WORK + device-lane handoff receipt), no code or asset changes.

Verified:

• Pinned tip d8c0620 matches current main HEAD exactly
• Laptop PASS scoped as OBSERVED laptop, not extended to device
• #247 explicitly stays open, closable only with tip-bound OBSERVED authored-mesh evidence
• States plainly that this is neither outdoor PASS nor TF archive approval

The SHA discipline is the useful part — requiring git rev-parse HEAD on the device build is exactly what would have caught the confusion we hit repeatedly, where a stale install made correct code look broken.