Skip to content

feat: bridge Kimaki context to Homeboy notifications#261

Open
chubes4 wants to merge 1 commit into
mainfrom
feat/260-kimaki-homeboy-notification-context
Open

feat: bridge Kimaki context to Homeboy notifications#261
chubes4 wants to merge 1 commit into
mainfrom
feat/260-kimaki-homeboy-notification-context

Conversation

@chubes4

@chubes4 chubes4 commented Jul 12, 2026

Copy link
Copy Markdown
Member

Summary

  • add an invocation-scoped OpenCode-to-wrapper boundary for Homeboy commands on managed Kimaki installs
  • map validated Kimaki thread or channel snowflakes to generic Homeboy notification context without a guild ID or fallback route
  • sync the managed plugin and wrapper through install/upgrade, and register the same Kimaki signature contract for DMC attribution
  • cover package-upgrade survival, absent-attribution omission, and concurrent thread isolation in the managed Kimaki rig

Validation

  • for test_file in tests/*.sh; do bash "$test_file"; done
  • node tests/effective-prompt/run.mjs
  • git diff --check
  • bash -n bridges/kimaki.sh bridges/kimaki/homeboy-notification-context.sh bridges/kimaki/post-upgrade.sh runtimes/opencode.sh
  • python3 -m py_compile lib/repair-opencode-json.py

Homeboy review audit ran, but its lint/test stages are unavailable because this component has no extension provider configured.

Closes #260.
Depends on remorses/kimaki#137.
Related to Extra-Chill/homeboy#7804.

AI disclosure

AI assistance: OpenCode using openai/gpt-5.6-terra.

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.

Map Kimaki thread attribution into generic Homeboy notification context

1 participant