Skip to content

#280/#283: bootstrap profile context-limit and reasoning-effort - #304

Closed
acoliver wants to merge 2 commits into
mainfrom
branch4-issue283-reasoning-effort
Closed

acoliver wants to merge 2 commits into
mainfrom
branch4-issue283-reasoning-effort

Conversation

@acoliver

@acoliver acoliver commented Sep 22, 2026 •

Copy link
Copy Markdown
Contributor

Recreated after the llxprt account suspension removed original PRs #284 (base) and #287 (stacked). Heads: branch4-issue280-context-limit at 95c8c0f1 and branch4-issue283-reasoning-effort at 589e81ad.

These unblock non-Codex-keyed profile loading and reasoning configuration. Do not merge pending re-verification on the restored head.

@acoliver acoliver changed the title restored: branch4-issue283-reasoning-effort #280/#283: bootstrap profile context-limit and reasoning-effort Sep 22, 2026
@acoliver

acoliver commented Oct 2, 2026

Copy link
Copy Markdown
Contributor Author

Closing as superseded by merged #309, following the open-PR remediation request. Current main already implements positive explicit u64 context and low/medium/high or disabled reasoning, including request projection. The old profile parser must not replace main’s newer policies.

Unique test witnesses have been accounted for in branch-2/evalwork/results/pr-remediation-20261002/superseded304306.json: the complete parse→resolved profile→serialized reasoning chain for all efforts/disabled omission will be retained in the #300 residual candidate. That port’s verification is still in progress and is not claimed as passed here. Existing main parser/draft/backend tests remain registered. Original head 589e81adeaa839b9b202fb81b5627b35b2a3de93, remote branch and fetched preservation refs remain intact; no branch deletion or history rewrite. This closure removes the duplicated production implementation, not the retained test work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant