K Fleet now defaults to suitable mainstream libraries and frameworks for general-purpose capabilities and checks existing custom mechanisms during design assessment and code review, even when they have no reported failures.
Changes
- Design and implementation research ecosystem options before selecting or retaining custom mechanisms. Routine technical decisions remain autonomous and current selection evidence is reused.
- Verification and the optional read-only reviewer distinguish defects, supported engineering improvements, and unverified leads. Improvement findings include a concrete alternative, evidence, expected benefits, and adoption costs.
- Test writing applies the same policy to general-purpose test tooling. Review findings do not authorize unrelated migrations or automatically block release.
- Updated method boundaries, setup reminders, and English/Chinese documentation. No new public skill or required agent was added.
Update
After npm publication, run npx --yes k-fleet@3.3.2 update, or use npx --yes github:KeterVM/k-fleet update. Add --all to update registered projects. Explicitly request kf-setup to refresh project reminders (CLI/IDE: $kf-setup).
Skills are downloaded from the repository's default branch; pinning the CLI version does not pin skill contents. GitHub Release creation and npm publication are separate actions.
Validation
Checked metadata for five affected skills, local links, instruction consistency, reviewer TOML and read-only/model-neutral settings, setup's explicit invocation policy, both READMEs, CLI syntax, and git diff --check. Inspected npm pack --dry-run contents (eight expected files, including reviewer configuration).
These checks establish source and packaging consistency, not skill effectiveness. Actual implementation and review behavior has not been evaluated; no evaluation harness was added.