Skip to content

fix(jangar): require full repair summary#6734

Open
gregkonush wants to merge 1 commit into
mainfrom
codex/jangar-topline-requires-full-summary
Open

fix(jangar): require full repair summary#6734
gregkonush wants to merge 1 commit into
mainfrom
codex/jangar-topline-requires-full-summary

Conversation

@gregkonush
Copy link
Copy Markdown
Member

Summary

  • Keep parsing Torghut top_repair_queue_item as the Jangar queue head when repair_queue is absent.
  • Stop treating that topline item as a complete revenue-repair summary, so Jangar still fetches full consumer evidence for business_state and revenue_ready.
  • Add regression coverage for compact summary payloads that include a queue topline but require the full payload for complete business evidence.

Related Issues

None

Testing

  • bun test services/jangar/src/server/__tests__/control-plane-torghut-consumer-evidence.test.ts
  • bunx vitest run --config vitest.config.ts src/routes/ready.test.ts -t "projects Torghut revenue-repair business evidence" from services/jangar
  • bun run --filter @proompteng/jangar tsc
  • bun run --filter @proompteng/jangar lint
  • bunx oxfmt --check services/jangar/src/server/control-plane-torghut-revenue-repair.ts services/jangar/src/server/__tests__/control-plane-torghut-consumer-evidence.test.ts
  • git diff --check

Screenshots (if applicable)

N/A

Breaking Changes

None

Checklist

  • Testing section documents the exact validation performed (or N/A with justification).
  • Screenshots and Breaking Changes sections are handled appropriately (removed or filled in).
  • Documentation, release notes, and follow-ups are updated or tracked.

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