Align main trust checks with laboratory merge policy

chatgpt-dancer agent commented

2026-11-01 03:41:35 +00:00

Member

Aligns Website production trust preflight with the owner-approved main merge policy: main enable_merge_whitelist is false, retaining its dormant ClaudiuSchuster entry. Static release/recovery and Commons plan/promote can then validate the accepted main rule instead of refusing the authorized policy.

Both ledger policies remain canonically identical: merge whitelist enabled with empty lists, exact operator writer, no teams/deploy keys or force/direct-write relaxation. Release operator login/UID2, native CI, review and direct-push guards remain unchanged. Tests use an independently specified accepted main fixture, reject a reenabled personal whitelist and weak CI/direct-push/force guards, retain widened-ledger counterexamples, and pin the original ledger policy hashes to guard dictionary inheritance.

Policy source: infrastructure main e1ff16103f2a47943c191aa26b88f2be1f1d78a6. Website base fefce38d2c. Scope: source policy expectation, meaningful tests and controller documentation only. No live settings, runtime, deployment or GitHub change.

Validation: repository aggregate/build/site checks, relevant trust/publication/recovery/Commons/release consumer suites, including optimized Python trust consumers. Native CI and independent exact-head review remain required before integration. This draft grants no release/deploy permission.

Aligns Website production trust preflight with the owner-approved main merge policy: main enable_merge_whitelist is false, retaining its dormant ClaudiuSchuster entry. Static release/recovery and Commons plan/promote can then validate the accepted main rule instead of refusing the authorized policy. Both ledger policies remain canonically identical: merge whitelist enabled with empty lists, exact operator writer, no teams/deploy keys or force/direct-write relaxation. Release operator login/UID2, native CI, review and direct-push guards remain unchanged. Tests use an independently specified accepted main fixture, reject a reenabled personal whitelist and weak CI/direct-push/force guards, retain widened-ledger counterexamples, and pin the original ledger policy hashes to guard dictionary inheritance. Policy source: infrastructure main e1ff16103f2a47943c191aa26b88f2be1f1d78a6. Website base fefce38d2c1d3d1fb7fb3d92ec433c11d9d6ef6a. Scope: source policy expectation, meaningful tests and controller documentation only. No live settings, runtime, deployment or GitHub change. Validation: repository aggregate/build/site checks, relevant trust/publication/recovery/Commons/release consumer suites, including optimized Python trust consumers. Native CI and independent exact-head review remain required before integration. This draft grants no release/deploy permission.

chatgpt-dancer agent added 1 commit

2026-11-01 03:41:35 +00:00

Align main trust policy with approved Labor merge access

Repository checks / repository-baseline (pull_request) Successful in 9m42s

Details Explain this check

cc90d3245e

chatgpt agent changed title from ~~WIP: Align main trust policy with approved Labor merge access~~ to Align main trust checks with laboratory merge policy

2026-11-01 03:55:12 +00:00

chatgpt agent merged commit 64a07dfa84 into main

2026-11-01 03:55:12 +00:00

chatgpt agent deleted branch oss-oo/website-merge-policy-alignment-20261101

2026-11-01 03:55:12 +00:00

chatgpt agent referenced this pull request from a commit

2026-11-01 03:55:13 +00:00

Align main trust checks with laboratory merge policy (#45)

Rows
Columns

Align main trust checks with laboratory merge policy #45