Diamond Owner Getter - Symmio Core v0.8.6

Summary

Both the core and AccountLayer ViewFacets renamed owner() to getOwner(). No alias is kept, so the old selector no longer resolves on either diamond.

Why

owner() shared its name with the address owner parameters on several AccountLayer view functions. The parameters shadowed the getter and produced compiler warnings. Renaming it makes the name unambiguous on both diamonds.

ABI-derived facet cuts pick up the new selector from the compiled interface. Hand-written ABI fragments are not type checked, however, so a stale owner() fragment fails only when the call reaches the upgraded diamond.

Effect on callers

owner() is the ERC-173 signature explorers use to detect ownership. Neither diamond registers ERC-173 through supportsInterface, so the rename does not break a declared interface. A call to the old selector, however, no longer reaches a facet and reverts through the Diamond fallback. Block explorers, admin dashboards, and monitoring must handle that revert and move to getOwner().

Current repository scripts call getOwner() for the core and AccountLayer diamonds; the separately deployed ExpressProvider still exposes owner(). External tooling that must support both pre-rename and post-rename core or AccountLayer deployments can try getOwner() first and explicitly fall back to owner() only for the older ABI.

The rename applies to both diamonds; the pending-owner getter is unchanged.
Diamond	Before	After
Symmio core ViewFacet	`owner()`	`getOwner()`
AccountLayer ViewFacet	`owner()`	`getOwner()`
both	`pendingOwner()`	`pendingOwner()` (unchanged)