# H11.0-P4.1 — Multi-Branch Connectivity & QA Hotfix

## Root cause from the failed H11.0-P4 Evidence

Apply succeeded and version `11.0.4` was installed. Every previous business and
Oracle regression gate remained PASS. The only functional failure was the new
multi-branch GMOV gate.

The endpoint reported:

- Oracle `ORA-12514`
- direct branch service unavailable to the listener
- no parity payload was produced

The PowerShell wrapper then masked that original Oracle error with a secondary
`property 'modes' cannot be found` message.

Two additional static checks were false negatives:

1. historical SQL token comparison was case-sensitive;
2. independence check treated class names in comments as executable coupling.

## R4.1 correction

### Branch access
For NJCH/JCKH/MNH:

1. Prefer the configured direct Oracle connection.
2. Only for Oracle connectivity/listener failures on JCKH or MNH, fall back to
   the established read-only DB links from the NJCH connection:
   - `rcpmaster_jck`
   - `rcpmaster_mnh`

No fallback occurs for SQL/business-rule errors.

### Evidence
The parity output now records the actual access path used for every branch and
for both independent implementations.

### QA
- historical contract scan is case-insensitive;
- executable independence is checked without being confused by comments;
- endpoint failure is preserved verbatim in Evidence;
- no missing `modes` masking error.

## Safety
- Oracle writes: NONE
- SQL DDL/DML: NONE
- Existing calculations changed: NONE
- GMOV acceptance remains exact zero difference.
