chore: integrate proman scaffold #32
Reference in New Issue
Block a user
Delete Branch "chore/27-proman-integration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Integrate proman as the unified dev toolchain.
Why
Standardize build/test/check/format across all Shazhou monorepos with one CLI (#27).
Changes
proman.yaml— 8 packages in dependency order (protocol → util → util-agent → agents → cli → dashboard)@shazhou/promanas devDependencybuild,test,check,formattypecheckscript for standalonetsc --buildfalse/to .gitignore (pnpm metadata cache leak)Verification
proman build✅proman test— 627/627 pass ✅proman check✅Ref
Fixes #27
Review — chore: integrate proman scaffold
✅ LGTM
proman.yaml— 8 packages in dependency order, types correct (libfor protocol/util/util-agent,clifor agents+cli,webuifor dashboard). Release config matches existing npm setup.Root scripts — clean delegation:
build/test/check/format→ proman, kepttypecheckfor standalone tsc, kepttest:cifor per-package CI runs. Good.Cleanup —
false/in .gitignore + biome ignores for pnpm metadata leak. biome schema bumped to 2.4.16.Formatting changes — bulk of the 30 files is biome auto-format (import ordering, single→double quotes). No logic changes.
627/627 tests pass ✅
📝 Note
proman.yamlhasprivate: trueon@united-workforce/dashboard— this field isn't in proman'sPackageEntrytype. It's silently ignored now, but if proman ever adds strict validation it'll break. Consider opening an issue on proman to supportprivatepackages (skip them during publish).Reviewed by 小墨