View Tasks GitHub Settings Review Candidates Promote to PR Lane PR Status Completion Audit
Environment: HTTP · OpenAI not ready · GitHub not ready
Generation status: openai_not_configured using gpt-5-codex
Current next step: Review PR v1, compare the four candidates, confirm or override Top 1 and Top 2, then promote one candidate to the PR lane.
This task keeps PR v1 as the anchor brief. One of v1/v2/v3/v4 becomes the active PR-lane path after review.
GOALS 1. Preserve effective-source precedence during contract map construction. The next PR must ensure that effective authoritative Typhoon data is not overwritten, downgraded, or bypassed by later nested/compat/container reads when valid effective truth is already present. 2. Keep one selected-map architecture. The next PR must preserve the current intended architecture: - select one authoritative Typhoon contract map - consume that selected map - normalize/finalize once It must not reintroduce mixed-source per-field reconstruction. 3. Support feature_flags / features only as bounded selected-map readers. If Typhoon caps or horizons are stored under feature_flags / features inside the already-selected map, the PR may read them only as bounded fill-only support. They must not become a new source-selection path. 4. Preserve canonical-first ordering. Direct canonical contract keys must always win first. Direct compat aliases may fill only when canonical keys are absent. Nested feature_flags / features reads may fill only when both direct canonical and direct compat paths are absent. 5. Preserve effective-first source selection. The resolver must continue to prefer effective authority when it is valid and not isolated-false. Compat remains secondary and bounded. 6. Prevent isolated-false suppression of richer compat truth. If effective is isolated-false, compat may only be consulted in the bounded richer-truth case already defined. This exception must remain narrow and must not widen into general compat promotion. 7. Keep fail-closed behaviour intact. If no authoritative Typhoon contract truth exists after the bounded source-selection path completes, WO must fail closed. 8. Preserve valid forecast entitlements already carried in effective/nested payloads. The next PR must not silently drop: - typhoon_forecast_points - typhoon_visible_comparisons_cap - forecast_horizons when those are present in valid selected/effective payload structures. 9. Keep Typhoon boolean truth tied to explicit contract truth. No new inference from caps, horizons, windows, plan names, or UI state may be introduced. 10. Stay single-file and WO-only. The next PR must remain confined to includes/class-wo-entitlements.php.
Repo Owner: DavidB-DnD
Repo Name: codex-projects
Base Branch: main
Codex Review Required: yes
Protected Branch Required: yes
Status Checks Required: yes
Promoted Candidate:
Promoted Branch:
PR Ready: no
GitHub PR Number:
GitHub PR URL:
GitHub Review Status:
GitHub Checks Status:
Merge Ready: no
Merge Block Reason:
Candidate
Strategy: Implement the narrowest possible safe patch. Minimize file changes and avoid scope creep.
Rank Position:
Summary:
Strengths:
Risks:
Selection Reason:
Non-selection Reason:
Candidate
Strategy: Implement the safest maintainable path. Stay tightly scoped but favor clarity and durability.
Rank Position:
Summary:
Strengths:
Risks:
Selection Reason:
Non-selection Reason:
Candidate
Strategy: Implement the strongest conservative behavior-preserving path. Minimize UX and integration risk while remaining robust.
Rank Position:
Summary:
Strengths:
Risks:
Selection Reason:
Non-selection Reason:
Candidate
Strategy: Implement the strongest approval-likely path under the authority docs. Be conservative, review-friendly, and structurally strong.
Rank Position:
Summary:
Strengths:
Risks:
Selection Reason:
Non-selection Reason: