20 行
1.1 KiB
Markdown
20 行
1.1 KiB
Markdown
# 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.
|
|
|
|
## Architecture constraints
|
|
|
|
- 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.
|
|
|
|
## Delivery constraints
|
|
|
|
- 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.
|
