Validate app name in templates & add support for validating pear init -y

[lejeunerenard]

Prevents default name property from being invalid for desktop and terminal type applications. With out the validation there are scenarios where default values can error once a user tries to run a Pear app which throws:

Error: The package.json name / pear.name field must be lowercase and one word, and may contain letters, numbers, hyphens (-), underscores (_), forward slashes (/) and asperands (@).

This revealed an issue with pear-api's processing of params when the --yes flag was set as well. So a full fix depends on holepunchto/pear-api#31

[Copilot]

Pull Request Overview

This PR refactors CLI commands to use the shared pear-api terminal interface, adds new flags/commands (e.g. --purge, --only, drop, data manifest, gc interfaces), and streamlines outputters to return arrays rather than async generators.

• Migrate all local iface, errors, parse-link, and constants imports to pear-api
• Introduce new commands/flags: drop, manifest (data), interfaces (gc), --purge & --only (stage & dump)
• Refactor outputters to return arrays and add byte-diff support

Reviewed Changes

Copilot reviewed 198 out of 198 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
cmd/versions.js	Switched import to pear-api/terminal and rewrote outputter to return array of tags
cmd/stage.js	Updated imports, added --purge & --only flags, and appended byteDiff tagger
cmd/dump.js	Updated imports, added --only & --prune flags, stats tag, and byteDiff tagger
cmd/index.js	Extensive command definitions update: new commands, flags, hidden reset, and help text
cmd/gc.js	Abstracted common GC logic into #op, added interfaces command
cmd/data.js	Added manifest output and command, refactored outputter calls

Comments suppressed due to low confidence (5)

cmd/stage.js:36

• Tests should be added to cover the new --purge and --only flags to verify that ignored files are removed and path filtering works as expected.

const { dryRun, bare, json, ignore, purge, name, truncate, only } = cmd.flags

cmd/gc.js:32

• Add unit tests for the new gc interfaces command path (e.g. --age) to confirm it passes the correct data to the IPC layer and formats output properly.

async interfaces (cmd) {

cmd/data.js:42

• Introduce tests for the data manifest output function to ensure it handles both present and missing manifest data as intended.

const manifestOutput = (manifest) => {

cmd/stage.js:4

• The byteDiff tagger is added without a matching tag key; you should map it under the 'byte-diff' tag (e.g. { 'byte-diff': byteDiff }) so byte‐diff events are handled correctly.

const { outputter, ansi } = require('pear-api/terminal')

cmd/dump.js:4

• Similarly, byteDiff must be keyed to the 'byte-diff' tag in the outputter's taggers object; otherwise byte-diff output won't be invoked.

const { outputter, permit, ansi, isTTY, byteSize, byteDiff } = require('pear-api/terminal')