release: bump socket surfaces to 6.3.4#34
Conversation
docs: audit skills against current surfaces
Why: Move the SpeakSwiftly final-reply TTS hook to the plugin-managed install surface while keeping .codex as a development-only harness. Verification: - sh scripts/repo-maintenance/validate-all.sh - jq empty .codex-plugin/plugin.json hooks/hooks.json .codex/hooks.json - node --check hooks/stop-tts.mjs - node --check .codex/hooks/stop-tts.mjs - node --check scripts/codex-hooks-doctor.mjs - node scripts/codex-hooks-doctor.mjs - git diff --check
Why: Keep README product-focused while making CONTRIBUTING the accurate contributor path for setup, validation, plugin hook work, and live E2E preflight. Verification: - maintain-project-contributing check-only - maintain-project-readme check-only - git diff --check
Why: Capture the planned split between the Swift package source of truth and a smaller socket-owned Codex plugin distribution unit before releasing the hook migration. Verification: - git diff --check
Move Codex TTS hook into plugin lifecycle
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ff4071dcd6
ℹ️ 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 address that feedback".
| "hooks": [ | ||
| { | ||
| "type": "command", | ||
| "command": "node ./hooks/stop-tts.mjs", |
There was a problem hiding this comment.
This command is resolved relative to the session working directory, not the plugin bundle location, so installed users will run node ./hooks/stop-tts.mjs from their project cwd and the script will be missing unless their repo happens to contain that path. Because plugin installs are loaded from ~/.codex/plugins/cache/..., this relative command breaks the core plugin-managed TTS hook flow for typical usage outside the SpeakSwiftlyServer repo.
Useful? React with 👍 / 👎.
1 participant
Summary
Subtree accounting
Verification