Ship base-bash init and a production project scaffold

[codeforester]

Parent: #214

Train position: 16 of 26
Phase: P2 — Project kit and deterministic distribution

Problem

The repository offers modules and cookbooks but no five-minute path from an empty directory to a professional, pinned, tested Bash application. A framework needs a generator that makes the safe path the easy path.

Acceptance criteria

• Generate an executable entrypoint, application modules, declarative command definition, configuration and lifecycle wiring, tests, CI, lint and format configuration, README, release metadata, and an immutable framework pin.
• Offer coherent minimal and standard profiles without fragmenting the application contract.
• Demonstrate logging, safe diagnostics, dry-run, cleanup, signals, help, version, subcommands, and failure handling through supported public APIs.
• Make output deterministic, refuse silent overwrites, support safe repeated invocation, and work offline once the framework is installed or vendored.
• Ensure a generated project passes its own conformance checks, BATS suite, ShellCheck warnings, shfmt, and CI on Linux and macOS.
• Measure and document a reproducible under-five-minute install-to-tested-executable quickstart.

Dependencies

• Publish a machine-readable API and module manifest #225
• Make base-bash a conventional, stable application launcher #227
• Provide a declarative CLI contract with help, validation, and subcommands #228
• Define configuration, environment, signal, and shutdown conventions #229