Mark/mesh-seed
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

integration test: drive synthetic MeshIntentResult through full delivery pipeline #280

New issue
Closed
opened 2026-08-14 17:27:00 +00:00 by Mark · 2 comments
Mark commented 2026-08-14 17:27:00 +00:00
Owner
Copy link

Wire a single integration test that drives a synthetic MeshIntentResult payload through DiscordBotService._run_intent for each of the four result shapes:

  • short — inline text, no split, no embed, no attachment
  • long prose — split() produces multiple ResponseParts (each <= 2000 chars), no file
  • code blocks — fence integrity preserved across the split stream
  • with file — attachment_threshold triggers _format_chat_attachment, file uploaded via discord.File, summary message references the attachment

Plus a research intent scenario where every component participates (typing + run-intent + embed + the splitter/attachment paths when applicable).

References the sibling component work:

  • #234 — base response delivery formatter
  • #270 — split() API + list continuity + nested-fence tests
  • #271 — typed MeshIntentResult + EmbedBuilder + 6000-char budget
  • #272 — ProgressReporter + typing-indicator bot wiring
  • #273 — oversize-output attachment path with allowlist + 8MB cap

Acceptance: pytest tests/unit/test_delivery_pipeline_integration.py passes; ruff clean; the verifier profile (kanban task t_b702138a) can read the merged PR and confirm all four components were present and exercised end-to-end.

Wire a single integration test that drives a synthetic MeshIntentResult payload through `DiscordBotService._run_intent` for each of the four result shapes: - **short** — inline text, no split, no embed, no attachment - **long prose** — `split()` produces multiple ResponseParts (each <= 2000 chars), no file - **code blocks** — fence integrity preserved across the split stream - **with file** — `attachment_threshold` triggers `_format_chat_attachment`, file uploaded via `discord.File`, summary message references the attachment Plus a **research intent** scenario where every component participates (typing + run-intent + embed + the splitter/attachment paths when applicable). References the sibling component work: - #234 — base response delivery formatter - #270 — `split()` API + list continuity + nested-fence tests - #271 — typed `MeshIntentResult` + `EmbedBuilder` + 6000-char budget - #272 — `ProgressReporter` + typing-indicator bot wiring - #273 — oversize-output attachment path with allowlist + 8MB cap Acceptance: `pytest tests/unit/test_delivery_pipeline_integration.py` passes; ruff clean; the verifier profile (kanban task `t_b702138a`) can read the merged PR and confirm all four components were present and exercised end-to-end.
Mark commented 2026-08-19 19:31:53 +00:00
Author
Owner
Copy link

Feature Triage — Escalated

Scope: medium | Risk: medium | Spec: partial
Summary: integration test: drive synthetic MeshIntentResult through full delivery pipeline
Rationale:

Not clear-cut enough for auto-approval. Labeled blocked:needs-decision — review and decide: approve (add triage-approved) or close.

## Feature Triage — Escalated **Scope:** medium | **Risk:** medium | **Spec:** partial **Summary:** integration test: drive synthetic MeshIntentResult through full delivery pipeline **Rationale:** Not clear-cut enough for auto-approval. Labeled `blocked:needs-decision` — review and decide: approve (add `triage-approved`) or close.
Mark closed this issue 2026-08-20 10:14:33 +00:00
Mark commented 2026-08-20 10:14:48 +00:00
Author
Owner
Copy link

Resolved: PR #283 merged (merge commit 350478c2) into master. Full-file integration test (tests/unit/test_delivery_pipeline_integration.py) lands all five scenarios (short, long-prose, code-block, with-file, research-intent) covering #234/#270/#271/#272/#273. Verification green: 8 passed in one invocation, ruff 0.3.0 clean on PR files. Janitor unblock qa-caught-unlanded-fix -> fix landed.

Resolved: PR #283 merged (merge commit 350478c2) into master. Full-file integration test (tests/unit/test_delivery_pipeline_integration.py) lands all five scenarios (short, long-prose, code-block, with-file, research-intent) covering #234/#270/#271/#272/#273. Verification green: 8 passed in one invocation, ruff 0.3.0 clean on PR files. Janitor unblock qa-caught-unlanded-fix -> fix landed.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
mesh-seed#142-gate-verify-pass-07b1f89
Labels
Clear labels   
blocked:children

   
blocked:commit-ready-failed

   
blocked:depends-231

Depends on #231 (Discord Bot Foundation) landing first. Do not pick until #231 is closed.

  
blocked:depends-236

Depends on #236 (Phase 1) landing first. Do not pick until #236 is closed.

  
blocked:depends-237

Depends on #237 (Phase 2) landing first. Do not pick until #237 is closed.

  
blocked:depends-238

Depends on #238 (Phase 3) landing first. Do not pick until #238 is closed.

  
blocked:depends-239

Depends on #239 (Phase 4) landing first. Do not pick until #239 is closed.

  
blocked:gate-fetch

   
blocked:gate-fetch

   
blocked:gate-lint

   
blocked:gate-research

   
blocked:needs-attention

Janitor escalated: pipeline terminated without producing expected changes. Human review required.

  
blocked:needs-decision

   
blocked:no-changes

   
blocked:no-procedure

   
blocked:preflight

Preflight check failed

  
blocked:verify-failed

   
bug

Something is broken

  
enhancement

New feature or request

  
feature-request

   
high-priority

Critical path items

  
in-progress

Issue is currently being worked on by a quickfix runner

  
lint-cleanup

Repo lint baseline is dirty

  
needs-decompose

   
needs-triage

   
ops-retry

   
ops-task

Operations task — install, configure, deploy, API calls

  
phase-5

Phase 5 Self-Building Infrastructure

  
quickfix

Pipe to opencode for direct fix

  
security/medium

Medium severity security issue

  
self-building

Autonomous code generation and self-improvement

  
triage-approved

Approved by triage — queued for fixer pipeline

No labels
blocked:children
blocked:commit-ready-failed
blocked:depends-231
blocked:depends-236
blocked:depends-237
blocked:depends-238
blocked:depends-239
blocked:gate-fetch
blocked:gate-fetch
blocked:gate-lint
blocked:gate-research
blocked:needs-attention
blocked:needs-decision
blocked:no-changes
blocked:no-procedure
blocked:preflight
blocked:verify-failed
bug
enhancement
feature-request
high-priority
in-progress
lint-cleanup
needs-decompose
needs-triage
ops-retry
ops-task
phase-5
quickfix
security/medium
self-building
triage-approved
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Mark/mesh-seed#280
No description provided.