# H11.0-P4.3 — Exact SID Branch Connection Closure

## Root cause proven by the user's successful SQL Developer screenshots

The application `.env` used:

- JCKH: `DB_JCKH_CONNECT_TYPE=service`
- MNH: `DB_MNH_CONNECT_TYPE=service`

But the working database connections are:

- NJCH: `10.10.12.10:1521`, SID `ORANJC`
- JCKH: `10.11.42.10:1521`, SID `orajck`
- MNH: `10.20.104.20:1521`, SID `oramnh`

Therefore `ORA-12514` was caused by asking the Oracle listener for a SERVICE_NAME
when these confirmed connections use SID.

## Root correction

The patch atomically changes only non-secret Oracle transport values in `.env`:

- all three branches use `CONNECT_TYPE=sid`;
- the confirmed host, port and SID values are enforced;
- existing usernames, passwords, schemas, application tokens and unrelated
  environment settings are preserved unchanged.

The original `.env` is backed up under the private Patch Center backup area and
is included in the normal rollback manifest without ever being published in Evidence.

## Architectural simplification

The previous runtime discovery resolver is removed from the active path because
the exact working endpoints are now known.

The new policy is:

`STRICT_CONFIGURED_SID_DIRECT`

There is no:

- DB-link guessing,
- TNS crawling,
- filesystem scanning,
- long discovery loop.

Each branch must connect directly and prove its Oracle identity.

## Acceptance

1. NJCH direct SID connection PASS.
2. JCKH direct SID connection PASS.
3. MNH direct SID connection PASS.
4. Three distinct Oracle identity fingerprints.
5. GMOV year mode: 36/36 exact branch-month values.
6. GMOV date-range mode: 36/36 exact branch-month values.
7. Total exact checks: 72/72.
8. `max_difference = 0`.
9. `write_operations = NONE`.