fix: restore owner-scoped gateway startup

[henrypark133]

Summary

• fix the E2E startup harness so server boot failures report the real stderr instead of masking it with ProcessLookupError
• keep the single-user gateway authenticated as the durable owner scope while preserving GATEWAY_USER_ID as the sender/routing identity
• align the startup workspace with the owner scope so owner-scoped routines and gateway flows stay consistent

Validation

• cargo fmt --all
• cargo clippy --no-default-features --features libsql --all-targets -- -D warnings
• cargo test --lib --no-default-features --features libsql tunnel --no-run
• pytest scenarios/test_connection.py::test_page_loads_and_connects -v -s
• pytest scenarios/test_owner_scope.py::test_http_channel_created_routine_is_visible_in_web_routines_tab -v -s
• pytest scenarios/test_owner_scope.py::test_web_created_routine_is_listed_from_http_channel_across_senders -v -s

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the application's startup process and gateway behavior by enhancing error reporting in end-to-end tests and standardizing authentication and workspace scoping. It ensures that server startup failures provide more actionable feedback and that single-user gateways consistently operate within the defined owner scope, improving overall reliability and predictability.

Highlights

• Improved E2E Test Error Reporting: The E2E startup harness now reports the real stderr on server boot failures, preventing ProcessLookupError from masking the actual cause.
• Owner-Scoped Gateway Authentication: Single-user gateways are now authenticated with the durable owner scope, while still preserving GATEWAY_USER_ID for sender/routing identity.
• Consistent Workspace Alignment: The startup workspace is aligned with the owner scope, ensuring consistency for owner-scoped routines and gateway flows.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[Copilot]

Pull request overview

This PR restores “owner-scoped” behavior for gateway startup and E2E harnessing, ensuring that durable state (workspace/routines) aligns to IRONCLAW_OWNER_ID while keeping GATEWAY_USER_ID as the sender/routing identity, and improving boot failure diagnostics in E2E tests.

Changes:

• Improve E2E startup failure handling to surface server stderr without being masked by process lookup errors.
• Re-scope gateway single-user auth to the durable owner scope while preserving sender/routing identity.
• Resolve the startup workspace (and memory tooling workspace) against owner_id instead of the gateway sender id.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
tests/e2e/conftest.py	Adjusts subprocess shutdown behavior on startup timeout to better capture stderr.
src/main.rs	Applies owner-scope rebinding for single-user gateway at startup.
src/config/mod.rs	Resolves the startup workspace config using owner_id instead of gateway user_id.
src/channels/web/server.rs	Sets IncomingMessage.sender_id explicitly to preserve routing identity.
src/channels/web/mod.rs	Adds GatewayChannel::with_owner_scope() to rebind single-user auth identity.
src/app.rs	Uses owner_id for workspace initialization used by memory tools.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[gemini-code-assist]

Code Review

This pull request refactors workspace and authentication logic to consistently use the owner_id for the base runtime workspace, particularly when multi-user tokens are not configured. This involves introducing a with_owner_scope method for GatewayChannel and applying it during initialization, as well as explicitly assigning a sender_id to incoming messages. Additionally, the end-to-end test fixtures have been improved for more robust process termination and error reporting. A review comment points out that the use of the unstable Rust let-chain feature in src/channels/web/mod.rs violates the project's Minimum Supported Rust Version (MSRV) compatibility goals and suggests refactoring it to a stable nested if statement.

[Copilot]

Pull request overview

Copilot reviewed 13 out of 13 changed files in this pull request and generated 2 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 13 out of 13 changed files in this pull request and generated 3 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 13 out of 13 changed files in this pull request and generated 2 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 13 out of 13 changed files in this pull request and generated 2 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 13 out of 13 changed files in this pull request and generated no new comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.