Make Boatstack configuration controls enforce their documented behavior

[bigboateng]

Summary

• make human plan approval, pass-with-gaps, and independent high-risk review authoritative runtime controls
• add schema-v2 human/policy plan locks while retaining schema-v1 compatibility
• replace the exhaustive public configuration guide with a curated user-control surface
• keep the internal serialized schema exhaustive and classify agent-mediated, metadata, and installer-owned fields

Why

The public guide treated every serialized JSON field as a user-facing control, while three workflow flags did not affect Boatstack's controller behavior. This made the configuration surface larger and less trustworthy than intended.

Impact

Repositories can disable human approval without fabricating approval provenance, disallow gap-bearing gate receipts, and require typed reviewer provenance for configured high-risk diffs. Existing schema-v1 human locks remain valid.

Validation

• go test ./...
• python3 -m unittest labs/12-product-engineering-loop/tests/test_product_loop.py
• python3 labs/12-product-engineering-loop/scripts/release_notes.py validate --root labs/12-product-engineering-loop/boatstack-distribution/release-notes
• git diff --check