MHR| Changes to QS Account Info Made in Auth Do Not Propagate to MHR

### Problem Statement
Updates to Qualified Supplier account information in Auth do not update the agreement data used by MHR.
Registrations continue to use outdated agreement fields such as name and address.
Users cannot view the agreement after approval to verify stored values.

### Current State
The QS agreement is treated as the authoritative data source for MHR registrations. After approval, the agreement is not viewable by suppliers or staff. Profile changes in Auth, such as mailing or plant address, do not update the agreement record. MHR continues to pull data from the original, now outdated agreement. Corrections require IT OPS to update backend agreement data by ticket.
No system indicator alerts users that Auth updates are not applied to MHR transactions.

### Potential Risks
Incorrect name and address details appear on registrations. Multiple records are issued with outdated data before the issue is detected. Staff effort increases due to manual investigation and IT OPS tickets. Client confidence is reduced when issued documents must be corrected. Potentially, there are possible audit and compliance exposure due to inconsistent source data across systems.

### Desired Outcomes
Agreement driven data is visible to authorized users after approval.
Material changes made in Auth to QS identity fields are reconciled with agreement data or flagged for action.
A controlled re acceptance flow is triggered when critical agreement fields change, such as name or address.
MHR registrations use current, approved agreement data.
Operational reliance on IT OPS tickets is reduced.

No files, tests, or entry points are identified in the issue. Start by mapping how Auth account changes, approved QS agreements, and MHR registrations exchange data; done means authorized users can view approved agreement data, material changes are reconciled or flagged, critical changes trigger re-acceptance, and registrations use current approved values.

Written by the indexing model from the issue text.