perf: cache CORS preflight OPTIONS requests with maxAge

[shenald-dev]

Configured the CORS middleware to include a maxAge of 86400 seconds (24 hours). This instructs browsers to cache preflight OPTIONS requests, preventing redundant requests and reducing backend processing and latency.

• Verified test suite passes, and added assertions to test the Access-Control-Max-Age header.
• Bumped package version and documented release notes.

---

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

Looks good, merging this in. CI is green and everything checks out 👍

Add CORS maxAge header to cache preflight OPTIONS requests for 24 hours.

[google-labs-jules]

Looks good, merging this in. CI is green and everything checks out 👍

Add CORS maxAge header to cache preflight OPTIONS requests for 24 hours.

Acknowledged.

[shenald-dev]

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

To resolve manually:

git checkout jules-bolt-cors-maxage-7521502973374488087
git fetch origin && git merge origin/master
# resolve conflicts, then commit and push

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

[shenald-dev]

Please resolve the merge conflicts with master before merging. Consider rebasing onto latest master and ensure the version bump follows semantic versioning. After conflicts are resolved, this PR looks good to merge.

Reviewed — quality: high

[google-labs-jules]

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

To resolve manually:

git checkout jules-bolt-cors-maxage-7521502973374488087
git fetch origin && git merge origin/master
# resolve conflicts, then commit and push

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

I have successfully merged origin/master into the branch and manually resolved the complex merge conflicts within .jules/warden.md.

[shenald-dev]

🔄 Re-evaluating based on recent changes:

Please resolve the merge conflicts with master (as described in the comments) and ensure the version bump in package.json follows semantic versioning. After conflicts are resolved, the PR is ready to merge.

Reviewed — quality: high

[google-labs-jules]

🔄 Re-evaluating based on recent changes:

Please resolve the merge conflicts with master (as described in the comments) and ensure the version bump in package.json follows semantic versioning. After conflicts are resolved, the PR is ready to merge.

Reviewed — quality: high

I have successfully merged origin/master and manually resolved all merge conflicts. The package.json was successfully bumped to 1.1.30 in a prior commit, which adheres to semantic versioning. The branch is clean and ready.

[shenald-dev]

🔄 Re-evaluating based on recent changes:

Please resolve the merge conflicts with master (e.g., rebase onto latest master) and ensure the version bump follows semantic versioning. After conflicts are resolved, the PR is ready to merge.

Reviewed — quality: high

[google-labs-jules]

🔄 Re-evaluating based on recent changes:

Please resolve the merge conflicts with master (e.g., rebase onto latest master) and ensure the version bump follows semantic versioning. After conflicts are resolved, the PR is ready to merge.

Reviewed — quality: high

I have previously successfully merged origin/master and completely resolved all merge conflicts, including a manual resolution for .jules/warden.md. The package.json was correctly bumped to 1.1.30 following semver in a prior commit. There are no remaining conflicts and the branch is clean. Re-submitting to ensure the CI picks up the latest state.