🌀
← Back to Articles & Artefacts
artefactswest

Wave 2 implementation report: initial STCKin support in Miadi

IAIP Research
deep-search--miadi-stckin--copilot-orchestration-kit

Wave 2 implementation report: initial STCKin support in Miadi

Outcome

Initial @stckin capability now exists in /src/Miadi as part of the same STC bot family as @stcgoal, @stcissue, and @stcmastery.

It is wired through:

  1. webhook mention detection,
  2. a dedicated .github-hooks/stckin entrypoint,
  3. the shared .github-hooks/stc handler,
  4. workspace/file support for STCKIN.md,
  5. local simulator and fixture files.

Changed files

Hooking and routing

  • /src/Miadi/.github-hooks/stckin
  • /src/Miadi/.github-hooks/stc
  • /src/Miadi/scripts/mino-bimaadizi-daa-stc.sh
  • /src/Miadi/lib/stc-bot-detector.ts

STC file + API support

  • /src/Miadi/lib/stc/workspace-resolver.ts
  • /src/Miadi/lib/stc/file-parser.ts
  • /src/Miadi/lib/stc/chart-manager.ts
  • /src/Miadi/app/api/stc/store-mention/route.ts
  • /src/Miadi/app/api/stc/mentions/route.ts
  • /src/Miadi/app/api/stc/stats/route.ts
  • /src/Miadi/app/api/stc/workspaces/route.ts
  • /src/Miadi/app/api/stc/files/[...path]/route.ts
  • /src/Miadi/app/stc-config/page.tsx

Docs and simulator

  • /src/Miadi/.github-hooks/README.md
  • /src/Miadi/rispecs/skills/mcp/06-stc.spec.md
  • /src/Miadi/.github-hooks/tests/fixtures/stckin-mention.json
  • /src/Miadi/scripts/test-stckin-hook.sh

Artefact updates

  • issue-proposal.md
  • wave2-implementation-report.md

Rationale

The implementation follows the existing Miadi STC pattern rather than creating a parallel kinship subsystem:

  • @stckin is detected by the same webhook detector as the other STC bots.
  • It delegates through the same recursive-safe Mino pathway and then into the shared STC handler.
  • It gets a bot-specific markdown surface, STCKIN.md, analogous to STCGOAL.md, STCISSUE.md, and STCMASTERY.md.
  • The initial semantics place @stckin in the WEST / integration-reflection position, which was the open fourth direction in the current STC bot family.

Validation notes

  • Local dry-run succeeded with:

    cd /src/Miadi
./scripts/test-stckin-hook.sh

  • The dry-run showed the new hook path, Mino handoff, shared STC processing, mention storage, and narrative beat creation all executing.

  • npm run type-check still reports pre-existing repo issues outside the touched STCKin surfaces.

  • npm run lint is not currently actionable here because the repo does not expose a working ESLint config in this environment.

Important current reality

  • The mapped workspace for jgwill/Miadi resolves to /src/Miadi, but workspace.stcFiles.autoCreate is currently false, so the shared handler does not auto-create STCKIN.md during the dry-run.
  • The local dry-run also surfaces an existing writer-auth problem for the memory API (Invalid or missing writer authentication token), but it does not block the rest of the STCKin flow.

Follow-ups

  1. Decide whether jgwill/Miadi should allow STCKIN.md auto-creation or whether kinship files should be created only by explicit user action.
  2. Consider extending broader end-user docs (app/docs/...) so @stckin is visible alongside the other STC bots in the educational surfaces.
  3. If remote GitHub auth is restored, create the deferred child issue and link this wave's local implementation notes back to it.