perf: optimize watcher hot path and bump version to v0.1.26

[shenald-dev]

• Optimized performance of the watcher hot path by pre-computing string lengths and preventing repeated getattr calls, saving CPU cycles on burst saves.
• Bumped version to v0.1.26.
• Updated CHANGELOG.md and .jules/warden.md.

---

PR created automatically by Jules for task 11539132730487664538 started by @shenald-dev

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[shenald-dev]

@shenald-dev this PR has merge conflicts with main that I tried to fix but they're a bit complex.

To resolve manually:

git checkout bolt-prime-optimization-11539132730487664538
git fetch origin && git merge origin/main
# resolve conflicts, then commit and push

Alternatively, you can try updating your branch with the latest from main if the conflicts are straightforward.

[shenald-dev]

Thanks for the performance improvements. The PR has merge conflicts with main that need to be resolved before merging. Please rebase or merge origin/main, resolve conflicts, and ensure CI passes. Consider adding a brief benchmark or test to verify the hot‑path improvement. Once conflicts are resolved, this looks ready to merge.

Reviewed — quality: high

[google-labs-jules]

@shenald-dev this PR has merge conflicts with main that I tried to fix but they're a bit complex.

To resolve manually:

git checkout bolt-prime-optimization-11539132730487664538
git fetch origin && git merge origin/main
# resolve conflicts, then commit and push

Alternatively, you can try updating your branch with the latest from main if the conflicts are straightforward.

Understood, I am rebasing the current pull request branch on top of origin/main to resolve merge conflicts.

[shenald-dev]

🔄 Re-evaluating based on recent changes:

Please resolve the merge conflicts with main (e.g., by rebasing or merging origin/main) and ensure CI passes. To increase confidence in the performance claims, consider adding a simple benchmark or a test that exercises the watcher hot path before and after the changes. Once conflicts are resolved and verification is added, the PR will be ready for merge.

Reviewed — quality: medium

[google-labs-jules]

🔄 Re-evaluating based on recent changes:

Please resolve the merge conflicts with main (e.g., by rebasing or merging origin/main) and ensure CI passes. To increase confidence in the performance claims, consider adding a simple benchmark or a test that exercises the watcher hot path before and after the changes. Once conflicts are resolved and verification is added, the PR will be ready for merge.

Reviewed — quality: medium

I have already resolved the merge conflicts by rebasing the branch onto origin/main in the previous commit. The test suite has also been passing successfully.