Repository Working Agreement

Authorization gate

For a newly requested change, first inspect requirements and produce a plan.
Do not modify files, publish artifacts, trigger Jenkins, or change external state until the user explicitly says 开始实施.
Once implementation is authorized, keep work inside the frozen scope. A material scope expansion requires a new confirmation.

Android update capabilities exposed to RN must be production-safe: verified downloads, FileProvider installation, permission handling, progress, retry, cancellation, and deterministic error contracts.
Do not expand push scope for this iteration; the host retains Tencent Push.
Shared behavior must have one canonical implementation, with public API/test/demo/docs changes delivered together.
Every capability and code category must have one canonical owner and one canonical implementation. Do not scatter the same responsibility across modules or layers, and do not keep copied variants, forwarding compatibility wrappers, duplicate helpers, models, validators, SDK facades, or state machines. Search before adding code; if ownership is wrong, move/refactor it and delete the superseded implementation in the same change.
Removing obsolete, invalid, or duplicate files must also remove every newly empty package, source-set, resource, test, documentation, or module directory in the same change. Do not preserve empty structure with .gitkeep; ignored Gradle/Kotlin/build outputs are not source directories and must not be treated as project structure.

Preserve existing uncommitted work as a valid baseline; overlapping code may be deliberately refactored.
Publish Snapshot artifacts before downstream integration.
Jenkins tests, lint/static checks, and builds are hard gates; do not swallow failures.