Compare commits

..
4 changed files with 2 additions and 125 deletions
@@ -1,31 +0,0 @@
# Codex Authorization: V2R1 Personal Weixin Foundation Minimum Scope
Date: 2026-07-15
## User-approved Foundation minimum scope
The following Foundation work is authorized:
- runtime package discovery;
- Django bootstrap;
- durable challenge contract;
- image build contract.
The durable challenge may proceed only to contract and test design. Any database schema or migration work requires further explicit authority.
## Explicitly prohibited without separate approval
- B6 and B7;
- QR flow;
- WeChat binding;
- canary;
- production;
- database schema or migrations;
- runtime or secrets;
- `scripts/wechat_send_backend.py`.
No controller, ChatGPT, or OpenClaw modifications are authorized. No secrets or OAuth material are authorized.
## Release state
Production remains at V1R4C6 and release is paused. This authorization does not authorize production or release changes.
@@ -1,25 +0,0 @@
# Codex Personal-Weixin Foundation Scope Amendment 1
```yaml
owner_approved: true
amends: AUTH-CODEX-V2R1-PERSONAL-WEIXIN-FOUNDATION-MIN-SCOPE-20260715
previous_blocked_result_commit: 3a3c9cf71be647f9b19935fba9f383887ad48a56
added_allowed_path: tests/test_v2r1_package_identity.py
changed_paths_contract: exact_18
production_baseline: V1R4C6
release_status: paused
```
## Authorized scope
This amendment authorizes one additional implementation path only:
`tests/test_v2r1_package_identity.py`. It may update the package-discovery
contract to require recursive `aios_v2r1*` discovery and to prove that the
built wheel contains `aios_v2r1.personal_weixin` and imports from outside the
repository after installation.
The implementation commit must be recreated directly from
`d5b51e1342541bf51887782f530c3d2971155996`, change exactly 18 authorized
paths, and retain the production baseline and paused release state above.
## Boundaries retained
@@ -1,67 +0,0 @@
# Owner Authorization: Retry 10 Foundation and Conditional R10 Continuation
```yaml
authorization_id: AUTH-CODEX-V2R1-PERSONAL-WEIXIN-RETRY10-R10-LINEAGE-20260716
owner_approved: true
executor: Codex isolated runner
production_baseline: V1R4C6
release_status: paused
force_push_authorized: false
```
## Retry 10 Foundation
Codex is authorized to apply the owner-authored Retry 10 materializer.
The materializer must evaluate each PEP 508 marker before active dependency
allowlist validation, freeze the marker environment once with `extra` set to
the empty string, fingerprint METADATA/WHEEL/installed RECORD/marker decisions,
and fail if trusted metadata changes during wheel construction.
Inactive optional-extra dependencies are retained in evidence but are not
active inputs. Active dependencies remain limited to asgiref and sqlparse.
Retry 10 Foundation remains limited to the existing exact 18 implementation
paths. No nineteenth implementation path is authorized.
## R10 lineage
After Retry 10 Foundation has a PASS implementation commit and immutable image
digest, Codex is authorized to create a separate control-plane lineage
amendment that inserts:
```yaml
node: F0_PERSONAL_WEIXIN_FOUNDATION
precedes: [B3, B4, B5, B6, B7]
```
The amendment must contain the actual full implementation/result commits and
actual immutable image digest. Placeholders are forbidden. It must not be
cherry-picked into the Foundation implementation commit.
## B3-B7
B3-B7 are conditionally authorized only after F0 is PASS and committed in the
lineage. Each stage must use an isolated worktree, an exact committed allowlist,
one non-merge implementation commit, and an independent RESULT.
This authorization does not invent missing B3-B5 paths. If an exact allowlist
is absent, the stage must stop as BLOCKED_SCOPE.
## Release Preflight, canary, and production
Release Preflight is authorized only after F0 and B3-B7 all have qualifying
PASS commits and results.
One canary is authorized only after immutable image, rollback, security,
offline, and integration gates are PASS. Canary failure requires rollback and
does not authorize production promotion.
Codex is not authorized to directly mutate production. It may prepare a
production deployment request after Release Preflight and canary PASS. A single
V2R1C0 production deployment may be executed only by the owner/admin GitOps
release action after all lineage, image, canary, rollback, and go-live evidence
is committed and verified.
Until that release action, production remains V1R4C6 and release remains
paused.
@@ -2,11 +2,11 @@
"task_id": "TASK-CODEX-V2R1-PERSONAL-WEIXIN-B6B7-BOOTSTRAP-AND-CANARY-20260715T120000UTC8",
"phase": "A",
"type": "branch",
"branch": "patch/v2r1-personal-weixin-b6b7-impl-20260715T115309UTC8",
"branch": "patch/v2r1-personal-weixin-b6b7-impl-20260715T034720Z",
"base_ref": "design/v2r1-personal-weixin-golden-contract-20260715",
"base_commit": "d74229927b2dadca7719455984aea10d010c5123",
"created_by": "aiman",
"created_at": "2026-07-15T03:53:09Z",
"created_at": "2026-07-15T03:47:20Z",
"direct_main_push": false,
"owner_approval_required": false,
"owner_approved": true,