Finalize HTTP gateway token wiring for single-package layout

[rjcorwin]

Summary

• ensure the gateway reuses generated tokens for HTTP participants and annotates bundled templates so human participants expose the REST transport
• resolve the mew-bridge executable from the new monorepo layout and point scenario setup scripts at the consolidated package paths
• keep scenario automation aligned with the new structure so HTTP smoke tests succeed end-to-end

Testing

• npm run build
• ./tests/run-all-tests.sh --no-llm

---

https://chatgpt.com/codex/tasks/task_e_68da8deb346c83258ba0c74f017b927f

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting

• @codex fix this CI failure
• @codex address that feedback

[chatgpt-codex-connector]

[P1] Replace subpath dependency with published package

The scenario template now declares a dependency on "@mew-protocol/mew/agent", but npm dependencies must reference published packages, not subpath exports. No package with that name exists, so npm install for the template will fail with “No matching version found for @mew-protocol/mew/agent”. Installers should depend on @mew-protocol/mew and import from @mew-protocol/mew/agent at runtime.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

[P1] Use root MEW package in proposals scenario dependencies

The package manifest now lists "@mew-protocol/mew/agent" as a dependency. Because that subpath is not a publishable npm package, npm install in this scenario workspace will fail, preventing the TypeScript proposals scenario from running. The dependency should remain on @mew-protocol/mew and the code should import from @mew-protocol/mew/agent instead.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

[P1] Fix participant dependency to target published package

The multi-agent scenario now depends on "@mew-protocol/mew/participant". Npm will treat that as a separate package which is not published, causing dependency installation to fail. To resolve, depend on @mew-protocol/mew and import the participant module via @mew-protocol/mew/participant at runtime.

Useful? React with 👍 / 👎.