Problem
Kimaki keeps immutable author identity on each queued message, but the WordPress bridge only registers session/thread/channel attribution. Mixed-speaker Discord or Slack-backed threads therefore cannot propagate the authenticated current-turn actor independently from the stable conversation/session owner.
Treating the first thread author or shared session as the current actor would allow one participant to inherit another participant's credentials, approvals, private context, or asynchronous job authority.
Contract
Consume Kimaki's invocation-scoped transport metadata when present:
KIMAKI_ACTOR_TYPE=discord_userKIMAKI_ACTOR_ID=<opaque provider user id>KIMAKI_ACTOR_NAME=<display-only name>
Session, channel, and thread identifiers remain conversation attribution. Actor metadata is audit/context only until a host explicitly maps the opaque account to a canonical person and resolves that person's grants.
Acceptance criteria
- Register and document the supported Kimaki actor metadata without teaching Data Machine or Homeboy about Discord.
- Preserve actor type/id as one explicit current-turn context when invoking WordPress/Agents API surfaces.
- Map actor type/id only into additive execution-principal actor fields; never into acting WordPress user, conversation owner, audience, capabilities, credentials, approvals, or run ownership.
- Omitted actor metadata remains compatible and does not reuse stale values from a previous turn.
- Concurrent sessions and sequential mixed-speaker turns cannot cross-contaminate actor context.
- Deterministic tests cover propagation, omission, and no-authority behavior.
Related
AI assistance
OpenAI GPT-5.6 Sol via OpenCode traced the mixed-speaker identity boundary across Kimaki, wp-coding-agents, and Agents API and drafted this issue under Chris Huber's direction. Chris remains responsible for the report and repair.
Problem
Kimaki keeps immutable author identity on each queued message, but the WordPress bridge only registers session/thread/channel attribution. Mixed-speaker Discord or Slack-backed threads therefore cannot propagate the authenticated current-turn actor independently from the stable conversation/session owner.
Treating the first thread author or shared session as the current actor would allow one participant to inherit another participant's credentials, approvals, private context, or asynchronous job authority.
Contract
Consume Kimaki's invocation-scoped transport metadata when present:
KIMAKI_ACTOR_TYPE=discord_userKIMAKI_ACTOR_ID=<opaque provider user id>KIMAKI_ACTOR_NAME=<display-only name>Session, channel, and thread identifiers remain conversation attribution. Actor metadata is audit/context only until a host explicitly maps the opaque account to a canonical person and resolves that person's grants.
Acceptance criteria
Related
AI assistance
OpenAI GPT-5.6 Sol via OpenCode traced the mixed-speaker identity boundary across Kimaki, wp-coding-agents, and Agents API and drafted this issue under Chris Huber's direction. Chris remains responsible for the report and repair.