Skip to content

Fix Wax audit remediation issues#70

Closed
christopherkarani wants to merge 2 commits into
codex/zigfrom
codex/audit-remediation-2026-05-12
Closed

Fix Wax audit remediation issues#70
christopherkarani wants to merge 2 commits into
codex/zigfrom
codex/audit-remediation-2026-05-12

Conversation

@christopherkarani
Copy link
Copy Markdown
Owner

Summary

  • fixes audit blockers across iOS availability, WAL payload validation, mmap durability, vector decode overflow, stale vector refill, and pending preview behavior
  • hardens MCP/CLI broker behavior around bounded daemon envelopes, doctor timeout cleanup, JSON null validation, hidden flush rejection, and no-trait imports
  • aligns public docs, demo package baselines, npm architecture metadata, launcher behavior, and release scripts

Stacking

Verification

  • swift build --disable-automatic-resolution
  • xcodebuild -quiet -scheme Wax -destination 'generic/platform=iOS' -derivedDataPath .build-codex/FixAuditIOSDerivedData build
  • swift test --filter 'CrashRecoveryTests|FDFileTests|VectorSerializerTests|UnifiedSearchTests' --disable-automatic-resolution (64 tests)
  • swift test --traits default,MCPServer --filter WaxMCPServerTests --disable-automatic-resolution (75 tests)
  • focused CLI/MCP/package/docs regressions
  • swift build --package-path Resources/WaxDemo --disable-automatic-resolution
  • (cd Resources/npm/waxmcp && npm pack --dry-run)
  • git diff --check

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 52c0d9ccd2

ℹ️ 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".

Comment on lines 117 to 121
requireVector: false,
embedderTuning: embedderTuning
)
let brokerStarted = try await AgentBrokerClient.ensureAvailable(configuration: brokerConfiguration)
let structuredMemoryEnabled = memoryConfig.enableStructuredMemory
defer {
if brokerStarted {
try? AgentBrokerClient.shutdownOwnedBrokerIfReachable(configuration: brokerConfiguration)
}
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Restore broker shutdown for brokers started by wax-mcp

This refactor removed the startup/teardown ownership tracking for the broker in runServer, so when wax-mcp starts a broker on demand via AgentBrokerClient.perform (the default path for tool calls), that broker is no longer shut down when the MCP server exits. In short-lived stdio sessions this leaves the broker process and store lock alive until idle timeout, which can block subsequent direct store access and make follow-up commands fail intermittently after server exit.

Useful? React with 👍 / 👎.

@christopherkarani
Copy link
Copy Markdown
Owner Author

Closing as stale/superseded. This branch was stacked on codex/zig, which has since landed, and current main contains newer follow-up work. The PR is now conflicting, so any remaining useful pieces should be reapplied selectively from a fresh branch off main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant