docs: sync documentation with Phase 29 progress#15
Merged
Conversation
- README: update test counts 602→604, expect calls 1495→1686 - AGENTS.md: Phase 29 'next' → 'in progress' - Roadmap: check off all 10 Phase 29 exit gates, fix P30 progress bar - ADR 0017: check off all 11 CI validation checklist items - Prompt library: add 4 built-in templates (code-review, refactor, explain, test-gen) - README stubs: flesh out ui, config, dashboard, benchmarks, cli templates - Remove deprecated IMPLEMENTATION_PHASE_CHECKLIST.md
- package.json: update drizzle-orm overrides 0.45.0→0.45.2 (match direct dep) - package.json: add packageManager field (bun@1.3.14) for GitHub detection - CodeQL: disable default setup (conflicted with custom codeql.yml workflow) - The health check runs npm on a Bun project — npm has arborist bugs with this workspace structure. packageManager field may help GitHub detect Bun.
- Replace all workspace:* with * across 18 package.json files - Bun generates package-lock.json alongside bun.lock automatically - Fixes npm EUNSUPPORTEDPROTOCOL error in GitHub health check - Bun resolution identical — no dependency changes
- GitHub health check runs npm ci which validates peer deps strictly - @opentui/solid@0.4.2 requires solid-js@1.9.12 creating ERESOLVE - legacy-peer-deps=true tells npm to warn instead of error on peer conflicts
- packageManager caused health check to try bun → exit 127 - Revert to npm path with .npmrc + package-lock.json in place
- Bun generates it with platform-specific optional deps as required - Causes EBADPLATFORM on Linux (darwin-arm64 can't install) - Without lockfile, npm install resolves deps directly (workspace:* already fixed)
- npm install runs prepare (husky) as lifecycle script - Husky detects bun.lock and tries to use bun → bun: not found → exit 127 - husky || true: fails gracefully when bun isn't available (e.g. health check runner)
- Health check runs npm test after npm install - Root test script called bun → bun: not found → exit 127 - CI uses bun test directly, not npm test — no impact on CI
- Health check runs npm run build after npm test - build-all.sh calls bun → bun: not found → exit 1 - CI uses bash scripts/build-all.sh directly, not npm run build
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documentation catch-up after Phase 29 commits (prompt library, playground, ModelComparer).
Changes
IMPLEMENTATION_PHASE_CHECKLIST.mdVerification