chore: bump packages/owletto pointer to ad46ebf

[buremba]

Bumps packages/owletto pointer.

Before: d940389
After:  ad46ebf

Picks up: fix(mac): open menu-bar deep-links as plain web URLs (#232)

Summary by CodeRabbit

• Chores
  • Updated project dependencies.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates the packages/owletto subproject reference to point to a newer commit, advancing the submodule dependency from d9403899c3747a9f975923ada795108b130055f4 to ad46ebf725ab7393bf010e1630c73bae0eced3a6.

Changes

Submodule Pointer Update

Layer / File(s)	Summary
Owletto subproject commit advance packages/owletto	The packages/owletto subproject commit pointer is updated to a new revision.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• lobu-ai/lobu#934: Both PRs only update the packages/owletto submodule/git pointer to a different commit.
• lobu-ai/lobu#1041: Both PRs only update the packages/owletto subproject pointer to a different commit, with no other code changes.
• lobu-ai/lobu#1084: Both PRs only bump the packages/owletto submodule pointer to different commit hashes.

Poem

🐰 A pointer springs forward, one line takes flight,
The owletto submodule hops to new height,
No code was changed, just the ref was renewed,
Git's version dance, so cleanly pursued. ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete and missing required sections from the template (Test plan and Notes are empty or absent).	Complete the description by filling out the Test plan section with which checks were run, and add any relevant Notes such as the picked-up fix details.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: bumping the packages/owletto subproject pointer to a specific commit hash.
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 chore/bump-bump-owletto-runlink

---

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

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@packages/owletto`:
- Line 1: The submodule pointer for packages/owletto is currently set to commit
ad46ebf725ab7393bf010e1630c73bae0eced3a6 which is not reachable from
owletto/main; update the packages/owletto gitlink to point to a commit that
exists on owletto/main (or rebase/merge the upstream owletto/main so that the
pinned SHA becomes reachable) before merging. Locate the submodule entry
(packages/owletto) in the repository index or .gitmodules and change the
gitlink/commit to a valid HEAD on owletto/main, or adjust your PR order so the
target commit is pushed to the owletto remote branch owletto/main first, then
update the pointer to that commit and re-run git submodule sync/update.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1e660a6a-61e9-4e5a-9be7-8a0db551c7b9

📥 Commits

Reviewing files that changed from the base of the PR and between 7f2ae5e and a3d4485.

📒 Files selected for processing (1)

• packages/owletto

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify the new submodule SHA is reachable from owletto/main

cd packages/owletto
git fetch origin main
PINNED="ad46ebf725ab7393bf010e1630c73bae0eced3a6"

if git merge-base --is-ancestor "$PINNED" origin/main; then
  echo "✓ SHA $PINNED is reachable from owletto/main"
  exit 0
else
  echo "✗ SHA $PINNED is NOT reachable from owletto/main"
  echo "This violates the deployment safety rule."
  exit 1
fi

Repository: lobu-ai/lobu

Length of output: 504

---

Critical: Ensure the owletto submodule pin commit is on owletto/main before merging.

ad46ebf725ab7393bf010e1630c73bae0eced3a6 is not reachable from owletto/main in the packages/owletto submodule (git merge-base --is-ancestor ... origin/main fails; fetch also reports not our ref). This violates the deployment safety rule that the parent must never pin a SHA not present on owletto/main. Update the submodule pointer to a commit that exists on owletto/main (or adjust PR sequencing).

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/owletto` at line 1, The submodule pointer for packages/owletto is
currently set to commit ad46ebf725ab7393bf010e1630c73bae0eced3a6 which is not
reachable from owletto/main; update the packages/owletto gitlink to point to a
commit that exists on owletto/main (or rebase/merge the upstream owletto/main so
that the pinned SHA becomes reachable) before merging. Locate the submodule
entry (packages/owletto) in the repository index or .gitmodules and change the
gitlink/commit to a valid HEAD on owletto/main, or adjust your PR order so the
target commit is pushed to the owletto remote branch owletto/main first, then
update the pointer to that commit and re-run git submodule sync/update.