reference-apps

Reference applications

These three applications are production-shaped fixtures for the v2 framework. They intentionally remain small enough to audit and each application policy is one physical lib/app.sh file.

Application	Workflow exercised
installer	verified install/update/rollback, typed paths, redaction, idempotent file state, dry-run and cleanup
release-helper	CI/release planning, Git inspection, explicit GitHub mutation boundary, sensitive token handling, rollback guidance
ops-cli	multi-command operations, completion, Git synchronization, optional tool probes, diagnostics, signals/cleanup

Run an application through the repository launcher so the framework path is explicit:

BASE_BASH_LIBS_DIR="$PWD/lib/bash" \
  "$PWD/bin/base-bash" examples/reference-apps/ops-cli/bin/app status

Each fixture has failure-path BATS coverage. The apps use only supported public APIs; optional network and GitHub operations are never performed by tests. Release inputs remain immutable pins and are verified by the repository bundle and vendor checks.

The RC→GA and rollback rehearsal is explicit and networkless. Given two independently verified unpacked framework roots, run:

examples/reference-apps/release-rehearsal.sh \
  --candidate /path/to/v2-candidate \
  --rollback /path/to/previous-v2-release \
  --report /tmp/base-reference-release.tsv

The required evidence schema and platform matrix live in release-evidence.yaml. It records the verified canonical v2.0.0 asset, checksum, and provenance; the repository never treats a moving checkout as release evidence.