Branch: ai/ecosystem-audit
Depends on: steps 9-29 β
(all named-consumer migrations complete; the audit checks what's NOT yet covered)
Blocks: steps 31-37 (which act on the audit's findings)
Audit every SugarCraft lib NOT explicitly migrated in steps 9-29 against the 8 new shared packages (candy-ansi, candy-buffer, candy-layout, candy-testing, candy-mouse, candy-input, candy-fuzzy, candy-async). Produce a per-lib opportunity matrix; this drives steps 31-37. No code is written this step β output is documentation only.
Reference: docs/repo_map_update.md doesn't enumerate every lib; the analysis only names the most-cited ones. The unnamed-but-adoptable libs are the gap this step closes.
docs/repo_map_update_followups.mdβ structured per-lib opportunity matrix.
docs/repo_map_updates.mdβ append a summary entry pointing at the new followups file.
- Audit covers EVERY lib not already touched in steps 9-29.
- For each lib, the report lists: which of the 8 shared packages it could adopt, why (one-line), and effort estimate (S / M / L).
- Report groups libs by which step (31-37) will tackle them.
- No code or composer.json changes.
-
git statusclean on master.
- Delegate everything to an Explore subagent β the supervisor pattern: keep coder context lean. Brief:
"List every directory at /home/sites/sugarcraft matching
candy-*,sugar-*,honey-*,super-*. For each, exclude those already migrated in steps 9-29 (covered list: candy-core, candy-sprinkles, candy-shine, candy-vt, candy-mosaic, candy-palette, sugar-bits, candy-forms, sugar-prompt, sugar-charts, sugar-table, candy-shell, sugar-spark, candy-hermit, candy-freeze, sugar-readline, sugar-veil, sugar-crumbs, candy-lister, super-candy, candy-query, sugar-boxer, sugar-dash, sugar-crush, sugar-stickers, candy-vcr, sugar-glow, candy-wish β confirm against the actual ai/* branch list in git for accuracy). For each remaining lib, briefly scansrc/and identify which of these 8 shared packages could be adopted with reasonable effort: candy-ansi (any byte-loop ANSI parsing?), candy-buffer (any cell-grid rendering / string composition?), candy-layout (any constraint sizing?), candy-mouse (any mouse hit-testing?), candy-input (any input decoding?), candy-fuzzy (any filter/search?), candy-async (any ReactPHP / async?), candy-testing (any view() output that lacks snapshot tests?). Output a structured per-lib report β markdown table per lib with package | benefit | effort (S/M/L)." - Block on Explore findings.
- Write
docs/repo_map_update_followups.mdstructured as:# Ecosystem-wide adoption opportunities _Generated by step-30 of the shared-foundation refactor. Drives steps 31-37._ ## Coverage map (steps 31-37) - Step 31 (candy-pty): ... - Step 32 (candy-tetris, candy-mines): ... - Step 33 (sugar-skate, sugar-wishlist, sugar-stash): ... - Step 34 (sugar-calendar, sugar-toast): ... - Step 35 (sugar-tick, sugar-post, candy-serve): ... - Step 36 (candy-flip, candy-kit, honey-bounce, honey-flap): ... - Step 37 (catch-all): any remaining lib not above ## Per-lib opportunities ### <lib-slug> | Package | Benefit | Effort | |---|---|---| ...
- Append summary to
docs/repo_map_updates.mdso steps 31-37 know to consult the followups file.
No tests β documentation-only step. The "test" is the followups file is well-formed markdown and includes every uncovered lib.
The Coder already wrote the followups file. Scribe verifies markdown lints (table syntax, headings), nothing more.
- PR title:
docs: ecosystem audit β adoption opportunity matrix - PR body:
## Summary - Per-lib audit of every SugarCraft package NOT touched in steps 9-29. - Output: docs/repo_map_update_followups.md with structured opportunity matrix. - Drives steps 31-37 of the shared-foundation refactor. - No code changes β documentation only. ## Test plan - [x] Followups file covers every uncovered lib - [x] Markdown table syntax valid Refs: docs/repo_map_step_30.md - Commit subject:
docs: ecosystem audit β adoption opportunity matrix.