Sweep both deploy inputs for option NAMES and VALUE TYPES: clean, and proven able to fail
The two extensions owed after the ruling, now run:
  dc0  75 assignments / 20 schemas / 0 unknown name / 0 type mismatch / 0 note
  dc1  75 assignments / 20 schemas / 0 unknown name / 0 type mismatch / 0 note
Both EXIT 0. dc1 introduces no new charm@channel pair -- checked, not assumed.

PROOF OF TEETH, because a clean sweep across two inputs is exactly the
implausibly-uniform result this repo has been burned by. Three defects planted
in a THROWAWAY copy, all three caught, EXIT 1:
  [FAIL name] barbican  does not declare option 'prefer-ipv6'   (attempt-1 defect)
  [FAIL type] keystone  'prefer-ipv6': declared boolean, got str ('true')
  [note]      glance    'vip': declared string, value is unquoted float

Type judgement is deliberately conservative: a mismatch is reported only where
juju's own coercion cannot save it. A scalar where a STRING is declared is a
NOTE, not a failure -- but it is still surfaced, because an unquoted value is
how a version string silently becomes a float. An UNRECOGNISED declared type
REFUSES rather than passing.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HvCyrwvYTTcDYnRErfMsNf
1 parent fbe7b31 commit 7205466c3fcca47317e6c9b9502e30022b7fa34a
@JANeumatrix JANeumatrix authored 11 hours ago
Showing 3 changed files
View
docs/CURRENT-STATE.md
View
docs/audit/stage5-prefer-ipv6-charm-research-20260731.txt
View
docs/changelog-20260731-prefer-ipv6-research.md