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

[shenald-dev]

QA Status: Verified. Full test suite (16 tests) and ruff linter passed.
Entropy Pruned: Minor CPU overhead eliminated in the watchdog event handler hot loop by caching prefix string lengths and utilizing direct attribute access for FileSystemEvent.
Dependencies Bumped: None.
Docs Updated: None.
Release: Not applicable for this minor hot path optimization.

---

PR created automatically by Jules for task 221691734101623780 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]

Hey @shenald-dev, heads up — this PR has merge conflicts with main.

To fix:

git checkout jules-221691734101623780-e086f08e
git fetch origin && git merge origin/main

[shenald-dev]

The optimization looks sound and passes all tests. Please resolve the merge conflicts with main (e.g., git fetch origin && git merge origin/main) before proceeding.

Reviewed — quality: high

[google-labs-jules]

Hey @shenald-dev, heads up — this PR has merge conflicts with main.

To fix:

git checkout jules-221691734101623780-e086f08e
git fetch origin && git merge origin/main

I have successfully merged origin/main and resolved the conflicts. The tests and linter have passed after the merge.

[shenald-dev]

🔄 Re-evaluating based on recent changes:

Good performance improvement; consider adding a brief benchmark or comment to highlight the impact of the caching change.

Reviewed — quality: high

[google-labs-jules]

🔄 Re-evaluating based on recent changes:

Good performance improvement; consider adding a brief benchmark or comment to highlight the impact of the caching change.

Reviewed — quality: high

Acknowledged.

[shenald-dev]

🔄 Re-evaluating based on recent changes:

Consider adding a brief benchmark or comment to highlight the performance impact of the caching change for future reference.

Reviewed — quality: high

[google-labs-jules]

🔄 Re-evaluating based on recent changes:

Consider adding a brief benchmark or comment to highlight the performance impact of the caching change for future reference.

Reviewed — quality: high

I have added comments highlighting the performance impact of the caching change in the hot path.