chore(lifecycle): assure, prune, and sync docs

[shenald-dev]

This commit wraps up the lifecycle duties for version 0.1.26 by finalizing all project files and metadata updates following the event loop optimization.

---

PR created automatically by Jules for task 7864003689726115417 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 jules-7864003689726115417-0379e8fa
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]

The PR updates documentation, changelog, and bumps the version in pyproject.toml for release 0.1.26. However, there are reported merge conflicts with the main branch that need to be resolved manually. Once conflicts are fixed and CI passes, the changes look safe to merge.

Reviewed — quality: medium

[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 jules-7864003689726115417-0379e8fa
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.

I have successfully merged origin/main into this branch and resolved the merge conflicts in CHANGELOG.md and .jules/warden.md manually. The test suite and linter still pass cleanly.

[google-labs-jules]

The PR updates documentation, changelog, and bumps the version in pyproject.toml for release 0.1.26. However, there are reported merge conflicts with the main branch that need to be resolved manually. Once conflicts are fixed and CI passes, the changes look safe to merge.

Reviewed — quality: medium

Thank you for the review. I have resolved the merge conflicts with the main branch. CI looks green locally, so this should be safe to merge now.

[shenald-dev]

🔄 Re-evaluating based on recent changes:

The PR updates documentation, changelog, and bumps the version for release 0.1.26. Changes appear safe and CI passes, but there are reported merge conflicts with main that must be resolved before merging. Please follow the instructions to fetch origin/main, resolve conflicts, commit, and push. After conflicts are cleared and CI remains passing, the PR can be merged.

Reviewed — quality: medium

[shenald-dev]

🔄 Re-evaluating based on recent changes:

Please resolve the merge conflicts with main branch as described in the comments, then ensure CI passes again. After conflicts are fixed, the changes (version bump, doc updates, and minor watcher.py tweak) look safe to merge.

Reviewed — quality: medium

[google-labs-jules]

🔄 Re-evaluating based on recent changes:

Please resolve the merge conflicts with main branch as described in the comments, then ensure CI passes again. After conflicts are fixed, the changes (version bump, doc updates, and minor watcher.py tweak) look safe to merge.

Reviewed — quality: medium

I have successfully merged origin/main into this branch, resolved the merge conflicts in CHANGELOG.md and .jules/warden.md manually, and submitted the final commit. The test suite and linter pass cleanly.

[shenald-dev]

@shenald-dev I went through the conflicts and resolved them — merged the changes from main into your branch. Resolved 1 file(s).

⏳ CI needs to run on the new commits before merging. Will auto-merge on the next cycle if checks pass.

🔧 Used 3-way merge with ancestor context for more accurate resolution.

📦 A backup ref was created: refs/heads/conflict-backup-jules-7864003689726115417-0379e8fa-1779369565032 — you can restore from this if needed.

Take a look and let me know if anything looks off 👍

[shenald-dev]

The PR updates documentation, changelog, and bumps the version for release 0.1.26. Changes look safe and CI is passing, but there are reported merge conflicts with main that must be resolved before merging. Please follow the instructions to resolve conflicts, then re-run CI.

Reviewed — quality: medium

[google-labs-jules]

The PR updates documentation, changelog, and bumps the version for release 0.1.26. Changes look safe and CI is passing, but there are reported merge conflicts with main that must be resolved before merging. Please follow the instructions to resolve conflicts, then re-run CI.

Reviewed — quality: medium

I have successfully merged origin/main into this branch and resolved the merge conflicts in CHANGELOG.md and .jules/warden.md manually. The test suite and linter still pass cleanly.

[shenald-dev]

@shenald-dev I went through the conflicts and resolved them — merged the changes from main into your branch. Resolved 1 file(s) (2 identical/safe files skipped).

⏳ CI needs to run on the new commits before merging. Will auto-merge on the next cycle if checks pass.

🔧 Used 3-way merge with ancestor context for more accurate resolution.

📦 A backup ref was created: refs/heads/conflict-backup-jules-7864003689726115417-0379e8fa-1779416097258 — you can restore from this if needed.

Take a look and let me know if anything looks off 👍

[google-labs-jules]

@shenald-dev I went through the conflicts and resolved them — merged the changes from main into your branch. Resolved 1 file(s) (2 identical/safe files skipped).

⏳ CI needs to run on the new commits before merging. Will auto-merge on the next cycle if checks pass.

🔧 Used 3-way merge with ancestor context for more accurate resolution.

📦 A backup ref was created: refs/heads/conflict-backup-jules-7864003689726115417-0379e8fa-1779416097258 — you can restore from this if needed.

Take a look and let me know if anything looks off 👍

Thank you for resolving the conflicts! I've pulled the latest changes, and both the test suite and linter pass cleanly locally. Looking forward to the CI results.

[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 jules-7864003689726115417-0379e8fa
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.

[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 jules-7864003689726115417-0379e8fa
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.

I have successfully merged origin/main into this branch, resolving the merge conflicts manually. The test suite and linter pass cleanly.