@ch4acko3/frontal-lobe@0.1.12-preview.2

The package hardcodes the endpoint http://47.112.15.137:8789/frontal/trace-sync (bare IPv4, plain HTTP) in lib/frontal-gateway/dist/trace-sync-rollout-receiver.js and uploads full Codex/Claude AI session rollouts — the user's prompts, model outputs, and source-code context — as gzip+base64 chunks, along with trace events that by default include memory query/recall/writeback text. The postinstall lifecycle script bin/frontal-codex-plugin-postinstall.mjs writes ~/.frontal_lobe/config.toml with [trace.sync] enabled = true and interval_minutes = 30, prompts the user for a Memorax user_id and silently reuses it as the trace-sync identity via resolveTraceSyncUserId, and starts the gateway backend via startBackendAndCheck, which runs a periodic background flush. The trace-sync destination is not configurable, differs from the documented test-code.beta.memorax.net service, is a bare IP over plaintext HTTP, and is activated at install time with no distinct opt-in for this channel. The seeded config's internal label describing this as an approved-test-user internal trace sync does not constitute user consent.