[lifi-contracts-tron-sync]

Automated sync from lifinance/contracts@da1ebbcd hit merge conflicts.

This branch carries upstream's history as-is - the conflict markers were NOT
committed - so every commit on it is already signed. Resolve by merging
main into the branch and pushing a signed resolution:

git fetch origin
git checkout sync/upstream-2026-10-07-28-1
git merge origin/main   # resolve the conflicts listed below in your editor
git add -u              # required: git commit refuses while paths are unmerged
git commit -S --no-edit
git push

git add -u stages every resolved path, including deletions, without sweeping
in the .orig backups git mergetool leaves behind - this repo's
.gitignore does not cover them, so git add -A would commit them.

Conflicting paths:

script/deploy/resources/buildAttestations.json

Important

Merge this PR with a merge commit. Squash and rebase drop the upstream
parent, so the merge base never advances and every later sync re-conflicts
on the entire fork delta.

See the Notion 'Tron deployments' page (section: The contracts-tron Fork) and
EXSC-587/EXSC-603 for the sync rules.

[github-actions]

🩺 Health-check invariants reminder

This PR changes a facet or periphery contract but does not touch
script/deploy/healthCheckInvariants.ts. Please confirm whether the daily
health-check registry needs an invariant added, adjusted, or removed
(new binding/authorization/owner relationship, a removed contract, or changed
struct/owner semantics). See rule 601-healthcheck-invariants for the checklist.

If no invariant change is needed, you can ignore this — it is a reminder, not a gate.