Skip to content

fix: suppress {{#noTask}} prompt path during scoped wakes#119

Draft
prabhatnagaraj-max wants to merge 15 commits into
NousResearch:mainfrom
prabhatnagaraj-max:fix/scoped-wake-notask-guard
Draft

fix: suppress {{#noTask}} prompt path during scoped wakes#119
prabhatnagaraj-max wants to merge 15 commits into
NousResearch:mainfrom
prabhatnagaraj-max:fix/scoped-wake-notask-guard

Conversation

@prabhatnagaraj-max

Copy link
Copy Markdown

Summary

  • add scoped-wake detection helpers for wake payload markers and scoped wake reasons
  • suppress {{#noTask}} rendering whenever a wake is scoped (even when taskId is absent)
  • inject a scoped-wake contract section instructing the agent not to check unassigned backlog
  • add fail-loud console.error guards for scoped-wake contract violations

Why

This upstreams the local hotfix currently applied in a volatile node_modules/.../dist/server/execute.js path.

Root-cause provenance: VER-204 and VER-205 tracked drift caused by the old {{#noTask}} path on scoped wakes.

Verification

  • npm run typecheck
  • npm run build

Notes

This repo currently has no prompt-assembly unit test harness in-tree, so this PR focuses on source-level parity with the deployed patch and compiler verification.

Prabhat Nagaraj and others added 15 commits May 13, 2026 16:10
Detect scoped wake markers/reasons, suppress {{#noTask}} during scoped wakes, inject explicit scoped contract instructions, and log fail-loud contract violations for missing scoped issue identifiers.
Suppress non-assistant quiet-mode pipe lines in response cleaning and transcript fallback parsing to avoid exposing wrapped tool command bodies in summaries/UI output.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
Add max-session-age rotation, inbox-lite sanity validation for resumed outputs, and one retry without --resume when synthetic ID/P-priority task lists appear.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
Author ADR-001 through ADR-010 for entity scope, API surface, auth, sync, and operational decisions.
Each ADR includes context, decision, consequences, alternatives, and relevant gate links.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
Map all current CRM-DQ engineering and QA gates with live-env dependency flags, unblock owners, and next actions. Includes a pre-env execution sequence and explicit Eng-6 scope-gap note for FoundingEngineer follow-up.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
Add three GitHub Actions workflows for non-env build/test gates and deploy placeholders.\n\nBuild/test workflows use repo-local npm scripts without D365 credentials. Deploy workflow is triggerable but marks environment-bound authentication/deploy/smoke steps as explicit TODOs for day-one hookup.
Define canonical CRM DQ entities, relationships, field constraints, and validation rules aligned to ADR extract/score/publish boundaries for VER-288.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
Update the Eng-3 tracker reference to VER-296 and fix the source-set link anchor to VER-307 for consistent issue traceability.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
Capture unresolved observability risks and required ownership decisions to satisfy Eng-1 gate acceptance and review readiness.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
Implement extract/score/publish adapter surface with deterministic stub data and failure injection rules for CI-safe contract testing.\n\nAdd adapter usage docs and focused unit tests for success/error paths.\n\nCo-Authored-By: Paperclip <noreply@paperclip.ing>
Add explicit contract-to-adapter mapping tables, parity notes, and migration open questions for VER-300 acceptance closure.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
Add OpenAPI 3.1 contracts for extract/score/publish, deterministic stub handlers with realistic fixtures, and a focused node:test suite. Include documented Redocly lint command for contract validation.
Constrain CRM-DQ workflows to relevant paths and add explicit stub test execution with deterministic, secretless gating. Include inline env-wiring guidance for future live-validation lanes.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
Add CRM-DQ QA-1 PLAN artifact with scope boundaries, pre-env vs env-dependent lanes, gate-to-verification mapping, entry/exit criteria, execution strategy, and risk ownership.
Execute both CRM-DQ unit test files via Node's test runner and align the test lane runtime to Node 24 so .ts and .mjs tests run consistently.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
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