v4.1.0-rc2 — Project Delegation Policy Alignment

v4.1.0-rc2 — Project Delegation Policy Alignment

This release candidate fixes a repository-level delegation policy conflict discovered during the v4.1 RC soak period.

What was fixed

The repository root AGENTS.md previously treated the repository-local .var/daily-profile.json as the authority for Luna delegation.

That development profile could become stale and incorrectly block otherwise valid Global Luna delegation.

RC2 removes that second authority.

Actual project delegation now follows the inherited installed Global selector policy:

Project AGENTS
        ↓
Inherited Global policy
        ↓
Installed selector
        ↓
Current Beijing-day Daily Profile
        ↓
Selected native Luna role

Repository-local .var state remains available for selector development, but it is explicitly non-authoritative for actual Codex project delegation.

Regression validation

The fix was validated in a fresh repository-context Codex session while the repository-local profile was intentionally still stale.

Observed state:

Repository .var profile:
2026-08-11

Current Global Daily Profile:
2026-08-13

Repository .var authority:
NO

Installed selector authority:
YES

Automatic delegation succeeded:

• 3 native Luna children were used.
• The children ran in parallel.
• All 3 used the role selected by the current Global Daily Profile.
• Actual model: GPT-5.6 Luna.
• No direct model override was used.
• No direct reasoning-effort override was used.
• Luna remained native leaf workers with no secondary spawn.
• Sol independently verified the child results and retained final acceptance authority.

Result:

STALE_REPO_VAR_BLOCKED_DELEGATION = NO
FRESH_REPO_CONTEXT_DELEGATION_PASS

Important runtime note

v4.1.0-rc2 is a repository-policy release candidate.

The installed Global runtime payload is unchanged from v4.1.0-rc1.

RC2 does not change:

• the ModelDial selector
• Official API v1 source handling
• Full Snapshot fallback
• LKG behavior
• Daily Profile schema
• installer behavior
• manifest schema
• Global AGENTS template
• Luna custom-agent configuration
• native leaf behavior
• concurrency limit
• legacy migration behavior

Therefore:

Users who already installed the v4.1.0-rc1 Global runtime do not need to reinstall or upgrade their Global runtime for RC2.

Selection architecture remains unchanged

Valid same-day Daily Profile
        ↓
ModelDial Official API v1
        ↓ invalid / unavailable
Official Full Snapshot JSON
        ↓ invalid / unavailable
Valid LKG
        ↓
NO_LUNA_PROFILE_AVAILABLE

Luna efforts remain:

• low
• medium
• high
• xhigh
• max

ultra remains excluded.

Validation

Source validation for commit:

a2e805cdf838d2bce44df1d20ffced645252d5a3

• Windows CI: PASS
• Ubuntu CI: PASS
• macOS CI: PASS
• Full unit-test suite: PASS
• Selector regression suite: PASS
• Installer lifecycle suite: PASS
• Policy regression suite: PASS
• Documentation validation: PASS

Fresh repository-context delegation validation:

PASS

Compatibility

No migration is required for:

• Daily Profile
• LKG
• manifest
• Global runtime
• Luna agent configuration

Upgrade guidance

Already using v4.1.0-rc1

No Global runtime reinstall is required.

Pull or update the repository source to obtain the corrected Project AGENTS.md policy.

New installation

Use the repository's documented immutable setup contract for the Global runtime, then use the current repository source for the Project policy.

Release status

This is a prerelease.

v4.0.0 remains the current stable release.

Attribution

ModelDial-derived test data remains attributed under CC BY 4.0 as documented in fixtures/modeldial/README.md.

Community project

This is an independent community project and is not affiliated with, sponsored by, or endorsed by OpenAI or ModelDial.