# Verification gate and app workflow documentation `tool/check_full.sh` now calls the bounded analyzer and memory-watchdog wrappers, from the app directory regardless of the caller's working directory. It preserves their actual nonzero statuses instead of accepting success-looking text from a failed command. Wrapper summaries remain in `build/check/`; they name their own full logs. Analysis failure stops before tests run, including a missing wrapper. `pipelines/README.md` now directs app tasks to the registered Mobile workflow and read-only inspection of its current version. The checked-in flutter-fix, flutter-design and flutter-preview definitions are labelled historical, and the README distinguishes code, checks, server landing, preview publication and the installed web root. No pipeline definition was edited or published. Checks: five Python orchestration fixtures pass; they cover successful wrapper calls from the repository root, misleading success text on analysis/test failure, a watchdog kill status, and a missing wrapper. `sh -n tool/check_full.sh` and `git diff --check` pass. No real Flutter suite was run in this lane; the manager runs integrated analysis and the full memory-watched suite after merging.