Skip to content

Use the selected profile input budget for Curated stories - #144

Merged
R055LE merged 1 commit into
mainfrom
issue-143-context-budget
Nov 8, 2026
Merged

R055LE merged 1 commit into
mainfrom
issue-143-context-budget

Conversation

@R055LE

@R055LE R055LE commented Nov 7, 2026

Copy link
Copy Markdown
Owner

Closes #143.

Curated rejected seven of the eight scheduled inputs from October 31 through November 7 before making a provider call. The story builder still enforced an 18,000-character limit after the selected writer/reviewer profile introduced a 32,768 conservative input-token bound. The first failure exceeded the old limit by just 24 characters; all reconstructed requests fit the selected profile allowance.

Use the selected profile's existing UTF-8/JSON/schema admission calculation for drafting, validation revision, semantic revision and review. Preserve full source evidence and prior-post history. Distinguish local request rejection from model-response failure, and version the selected input fingerprint so previously rejected observations can be reconsidered without clearing database records. Legacy limits and fingerprints remain unchanged. Daily spending, token, workflow and attempt limits, model pins, schedule and delivery destination are unchanged.

Validation:

  • Full suite: 771 passed, 88.45% coverage against the 75% gate; Ruff and diff checks passed.
  • Independent coordinator run: 11 focused regression cases passed. Independent read-only review found no blockers.
  • Real SDK with mocked transport: both roles accept exactly 32,768 and reject one over before reservation or I/O; UTF-8 and escaped JSON are included.
  • Complete fake-provider workflows preserve eight full sources and four prior deliveries through both revision paths and independent review.
  • Offline replay of all eight historical first requests: baseline seven failures/one success; candidate eight successes, every source and prior-post record preserved. The previously successful request is byte-identical. The candidate ran with networking disabled and read-only data mounts, with no model spend or production-state changes.

Historical replay establishes first-request admission only; it does not establish live editorial quality or delivery acceptance. The paid evaluation adapter retains its existing input boundary. Production merge/deployment awaits approval.

@R055LE
R055LE merged commit 58c03ad into main Nov 8, 2026
2 checks passed
@R055LE
R055LE deleted the issue-143-context-budget branch November 8, 2026 01:10

R055LE commented Nov 8, 2026

Copy link
Copy Markdown
Owner Author

The owner explicitly approved merging this PR and its normal deployment. PR #144 merged as 58c03ad5b94ef99252c14285b3acc6c348df3522; the merged tree exactly matches reviewed head 5254be28be3fbb91c3c3301399b2da42838c560c.

Release: https://github.com/R055LE/roger/actions/runs/42433093042. Following the existing signed-image deployment timer, with no configuration changes or extra inference. Runtime acceptance will be recorded after the normal reconciliation cycle.

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.

Use the selected Curated profile input budget for story requests

1 participant