Skip to content

post-audit: close remaining Tiny Actor, council integration, and build-doc drift gaps #1298

Description

@JeremyDev87

Background

A fresh audit after the recent fixes found that the project is much healthier overall: build, typecheck, and hook tests are green, and earlier runtime issues around mode detection, data-dir consistency, and standalone behavior appear to be in much better shape.

However, the audit also found a small set of remaining gaps that matter because they affect visible behavior rather than internal plumbing.

These fall into three groups:

  • Tiny Actor terminal output is partially implemented but still not fully width-safe or fully wired into real Claude Code terminal surfaces.
  • The new council preset / consensus work exists in isolation but is not yet integrated into the main parse_mode response path.
  • The plugin build still regenerates a README that drifts away from the current standalone-aware product behavior.

This parent issue tracks those remaining gaps.

Scope

In scope:

  • Claude Code terminal-rendered plugin output, not the separate TUI
  • Tiny Actor width safety, runtime integration, and persona fidelity
  • MCP response integration for council preset / consensus data
  • Build-generated plugin documentation drift

Out of scope:

  • The command namespace migration work already tracked elsewhere
  • Replacing every existing Buddy surface in one pass
  • Large visual redesign beyond the Tiny Actor rollout

Why this matters

The remaining problems are subtle because many tests already pass. The issue is not that the codebase is unstable; it is that some newly added features are still incomplete at the final integration layer.

That means users can still run into:

  • crooked Tiny Actor layouts with multilingual text
  • a feature-flagged preview path that does not show up in normal Claude Code terminal output
  • generic actor faces instead of the actual agent personas already defined in the repo
  • council building blocks that exist in code but do not affect the real parse_mode response yet
  • a build step that rewrites docs back to an older MCP-only stance

Acceptance criteria

This parent issue is complete when all of the following are true:

  • Tiny Actor terminal output remains aligned under CJK, emoji, and ANSI cases
  • Tiny Actor rendering uses the width-safe card/grid path instead of ad-hoc preview formatting
  • Tiny Actor output is reachable from actual Claude Code terminal plugin surfaces behind an explicit flag or rollout gate
  • Tiny Actor cards use real agent visual.eye metadata where available
  • council preset / consensus data is emitted from the main MCP workflow in a way clients can actually consume
  • the generated plugin README no longer reintroduces outdated MCP-required messaging

Sub-issues

Recommended order

  1. fix(plugin): make Tiny Actor Grid layout truly display-width-safe for CJK and ANSI text #1304
  2. fix(plugin): make Tiny Actor preview use the width-safe renderer and grid pipeline #1303
  3. feat(plugin): wire feature-flagged Tiny Actor output into real Claude Code terminal surfaces #1302
  4. feat(plugin): derive Tiny Actor faces from each agent's visual.eye metadata #1301
  5. feat(mcp): emit council preset and consensus data from the main parse_mode response path #1300
  6. fix(plugin): stop build-generated README from reverting to outdated MCP-required messaging #1299

Metadata

Metadata

Assignees

No one assigned

    Labels

    parent-issue하위 이슈를 포함하는 상위 이슈priority:mediumMedium priority

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions