Fix owner-controlled production boundary

[suyog19]

Closes #5

Summary

Corrects a latent mismatch between the canonical human production boundary and its GitHub-native adapter.

The policy has always intended that:

• production authorization and promotion remain human-controlled;
• automation and agents cannot authorize or promote production;
• fresh-context independent review remains mandatory;
• the implementation context cannot issue the independent verdict.

The former adapter fields required_human_reviewer: true and prevent_self_review: true accidentally converted that intent into an unconditional two-human requirement. This patch explicitly permits manual owner authorization and promotion while allowing repositories with multiple authorized maintainers to configure a stronger reviewer gate.

Changes

• release version 1.0.1;
• clarify executable human-production-boundary semantics;
• separate independent-review semantics in evaluated obligations;
• replace unconditional second-human native-enforcement fields;
• document owner-controlled and stronger multi-human modes;
• add regression tests for manual owner authority, prohibited automation, and preserved fresh-context review.

Validation

• python -m pytest -q: 49 passed
• python tests/verify.py: 19 acceptance checks passed
• source distribution and wheel build: passed
• git diff --check: passed

Production boundary

This PR must be merged manually by the repository owner. Automation and agents must not merge it.