DebugBundle AGENTS.md changelog

https://raw.githubusercontent.com/debugbundle/debugbundle/HEAD/AGENTS.md

+ ### SDK Capability, Safety and Reliability Parity+ For every SDK or SDK-evidence change, evaluate all maintained SDKs, framework adapters, relays, wrappers and native bridges before implementation. Follow [the mandatory SDK parity rule](rules/sdk-capability-parity.md), [the universal SDK contract](contracts/sdk-interface.md) and [the SDK testing strategy](rules/sdk-testing-strategy.md); record each surface's applicability, implementation or verified equivalence, runtime limitations and tests. Implement applicable improvements within the authoris+ ### CocoaPods Trunk Transition+ Before planning an affected release, read [the CocoaPods distribution checklist](spec/cocoapods-trunk-transition.md) and refresh the provider schedule. The refreshed announcement is 2–6 November 2026 testing and permanent read-only on 2 December 2026. Swift 3.1.2 and React Native 3.1.1 qualify immutable Git-pod distribution with public SPM, bare RN and Expo runtime checks; retain those exact-artifact gates for future releases. Preserve existing Trunk installations and the supported native floor.

https://raw.githubusercontent.com/debugbundle/debugbundle/HEAD/AGENTS.md

+ ### Product Scope and Separate Consent+ - This workspace's authorized product is **DebugBundle only**, including its own SDKs, plugins and distribution repositories when they are within the requested change.+ - Approval to fix, publish or deploy DebugBundle never authorizes changing another product, even when the same owner controls it or its telemetry exposed the bug. General approval such as "proceed with the releases" stays within DebugBundle.+ - Do not update dependencies, edit files, commit, push, publish, deploy, change infrastructure/access rules, mutate data, or run production canaries in consumer products such as SayCheese, Afipal, Sava, Healthbrain, TaskTime or LOADVOID without separate explicit consent naming that product and action.+ - Publishing the DebugBundle WordPress plugin is a DebugBundle distribution action; installing or updating it on an existing WordPress site requires separate explicit consent for that site.+ - When a consumer needs adoption, report the available DebugBundle version and leave the consumer unchanged until consent is given. Shared ownership, available credentials, access to a repository and a release-verification procedure do not confer authorization.+ - An unauthorized change is not permission to perform a rollback or any further consumer mutation. Disclose the action and obtain explicit instructions before further changes.