Go 1.24 Synctest and Chi Middleware Context Tree Propagation Boundary | AgentRules.org

Rules Stacks Clients Auditor Pruner Self-Heal RFCs Benchmark CLI CI/CD Authors Submit

This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →

backendcritical PriorityID: go-synctest-chi-context-propagation-boundary

Go 1.24 Synctest and Chi Middleware Context Tree Propagation Boundary

Enforces strict context-tree lifetime propagation across nested Chi HTTP middleware chains and async background routines. Precludes orphaned goroutines and silent request cancellation leaks by requiring structured context derivation and verifying deterministic termination via Go 1.24 testing/synctest virtual bubbles.

Prohibited Anti-Pattern: Spawning Unbound Asynchronous Goroutines with Request Context or Raw context.Background Inside Chi Middleware

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Go 1.24 Synctest and Chi Middleware Context Tree Propagation Boundary - Enforces strict context-tree lifetime propagation across nested Chi HTTP middleware chains and async background routines. Precludes orphaned goroutines and silent request cancellation leaks by requiring structured context derivation and verifying deterministic termination via Go 1.24 testing/synctest virtual bubbles.
globs: **/*.go
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/go-synctest-chi-context-propagation-boundary"
---

# Go 1.24 Synctest and Chi Middleware Context Tree Propagation Boundary

> **Severity**: CRITICAL | **Category**: backend
> **Anti-Pattern Warning**: Spawning Unbound Asynchronous Goroutines with Request Context or Raw context.Background Inside Chi Middleware

## System Constraints
You are a Principal Engineer enforcing Go 1.24 Synctest and Chi context propagation boundaries. Mandate strict context inheritance, zero goroutine leakage, explicit lifecycle decoupling via structured workers, and deterministic verification in synctest.Run bubbles.

## Strict Guidelines
- Engineers MUST ALWAYS propagate the request context down Chi middleware chains using `r.WithContext(ctx)` rather than mutating or creating unbounded root contexts.
- Engineers MUST NOT invoke `go func()` directly inside Chi middleware or HTTP handlers with `r.Context()`, as context cancellation on HTTP connection teardown causes race conditions and broken downstream I/O.
- Engineers MUST NOT use unmanaged `context.Background()` or `context.TODO()` in handlers to escape cancellation; asynchronous side-effects MUST be dispatched to worker pools or supervisors with application-lifetime contexts.
- Code SHOULD leverage Go 1.21+ `context.WithoutCancel` combined with bounded work queues when background operations intentionally outlive the incoming HTTP transaction boundary.
- Services MUST verify asynchronous Chi middleware pipelines within Go 1.24 `synctest.Run(func() { ... })` bubbles to guarantee deterministic goroutine resolution and prevent test deadlock or leak regressions.
- Components NEVER drop context cancellation errors without structured telemetry and MUST gracefully handle `ctx.Err()` in long-running I/O operations.

## Bad vs Good Implementations
### Asynchronous Audit Logging in Chi Middleware with Synctest Verification

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Launching a background goroutine tied to the transient HTTP request context causes non-deterministic failures when the request lifecycle ends. The goroutine is orphaned, cannot be tracked, and escapes synctest bubbles in Go 1.24.
```go
package middleware

import (
	"context"
	"net/http"
	"time"
)

func AuditLogger(next http.Handler) http.Handler {
	return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
		// ANTI-PATTERN: Launching an untracked goroutine bound to r.Context().
		// When the client disconnects or request finishes, r.Context() cancels,
		// corrupting asynchronous writes or leaking goroutines on blocked I/O.
		go func() {
			time.Sleep(50 * time.Millisecond)
			_ = writeAuditLog(r.Context(), r.URL.Path)
		}()
		next.ServeHTTP(w, r)
	})
}

func writeAuditLog(ctx context.Context, path string) error {
	return nil
}
```

#### Production Standard (Correct)
> **Standard**: Decouples the asynchronous side-effect from the request context into a supervised worker using the application boundary context. Concurrency and goroutine termination are deterministically verified inside a Go 1.24 synctest.Run bubble.
```go
package middleware

import (
	"context"
	"net/http"
	"sync"
	"testing"
	"testing/synctest"
	"time"
)

type AsyncAuditor struct {
	appCtx context.Context
	wg     sync.WaitGroup
	logs   chan string
}

func NewAsyncAuditor(appCtx context.Context, buffer int) *AsyncAuditor {
	a := &AsyncAuditor{
		appCtx: appCtx,
		logs:   make(chan string, buffer),
	}
	a.wg.Add(1)
	go a.worker()
	return a
}

func (a *AsyncAuditor) worker() {
	defer a.wg.Done()
	for {
		select {
		case <-a.appCtx.Done():
			return
		case path := <-a.logs:
			_ = writeAuditLog(a.appCtx, path)
		}
	}
}

func (a *AsyncAuditor) Middleware(next http.Handler) http.Handler {
	return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
		select {
		case a.logs <- r.URL.Path:
		case <-r.Context().Done():
			http.Error(w, r.Context().Err().Error(), http.StatusRequestTimeout)
			return
		}
		next.ServeHTTP(w, r)
	})
}

func writeAuditLog(ctx context.Context, path string) error {
	return nil
}

// Deterministic Go 1.24 Synctest verification
func TestAuditMiddleware_Synctest(t *testing.T) {
	synctest.Run(func() {
		ctx, cancel := context.WithCancel(context.Background())
		auditor := NewAsyncAuditor(ctx, 1)

		req, _ := http.NewRequestWithContext(ctx, http.MethodGet, "/health", nil)
		handler := auditor.Middleware(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
			w.WriteHeader(http.StatusOK)
		}))

		handler.ServeHTTP(nil, req)
		synctest.Wait()

		cancel()
		auditor.wg.Wait()
	})
}
```

Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

GitHub Context Inspector

Inspects git diffs and commits to verify context and goroutine handling against standard Go guidelines.

Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Runs static analysis linters including contextcheck, govet, and noctx to catch context leaks.

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Go 1.24 Synctest and Chi Middleware Context Tree Propagation Boundary

Go 1.24 Synctest and Chi Middleware Context Tree Propagation Boundary defines an industrial-grade behavioral standard for backend engineering. Enforces strict context-tree lifetime propagation across nested Chi HTTP middleware chains and async background routines. Precludes orphaned goroutines and silent request cancellation leaks by requiring structured context derivation and verifying deterministic termination via Go 1.24 testing/synctest virtual bubbles. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Spawning Unbound Asynchronous Goroutines with Request Context or Raw context.Background Inside Chi Middleware Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Spawning Unbound Asynchronous Goroutines with Request Context or Raw context.Background Inside Chi Middleware	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Engineers MUST ALWAYS propagate the request context down Chi middleware chains using `r.WithContext(ctx)` rather than mutating or creating unbounded root contexts.

Engineers MUST ALWAYS propagate the request context down Chi middleware chains using `r.WithContext(ctx)` rather than mutating or creating unbounded root contexts.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

2

Engineers MUST NOT invoke `go func()` directly inside Chi middleware or HTTP handlers with `r.Context()`, as context cancellation on HTTP connection teardown causes race conditions and broken downstream I/O.

Engineers MUST NOT invoke `go func()` directly inside Chi middleware or HTTP handlers with `r.Context()`, as context cancellation on HTTP connection teardown causes race conditions and broken downstream I/O.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

3

Engineers MUST NOT use unmanaged `context.Background()` or `context.TODO()` in handlers to escape cancellation

Engineers MUST NOT use unmanaged `context.Background()` or `context.TODO()` in handlers to escape cancellation; asynchronous side-effects MUST be dispatched to worker pools or supervisors with application-lifetime contexts.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

4

Code SHOULD leverage Go 1.21+ `context.WithoutCancel` combined with bounded work queues when background operations intentionally outlive the incoming HTTP transaction boundary.

Code SHOULD leverage Go 1.21+ `context.WithoutCancel` combined with bounded work queues when background operations intentionally outlive the incoming HTTP transaction boundary.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

5

Services MUST verify asynchronous Chi middleware pipelines within Go 1.24 `synctest.Run(func() { ... })` bubbles to guarantee deterministic goroutine resolution and prevent test deadlock or leak regressions.

Services MUST verify asynchronous Chi middleware pipelines within Go 1.24 `synctest.Run(func() { ... })` bubbles to guarantee deterministic goroutine resolution and prevent test deadlock or leak regressions.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

6

Components NEVER drop context cancellation errors without structured telemetry and MUST gracefully handle `ctx.Err()` in long-running I/O operations.

Components NEVER drop context cancellation errors without structured telemetry and MUST gracefully handle `ctx.Err()` in long-running I/O operations.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Go 1.24 Synctest and Chi Middleware Context Tree Propagation Boundary critical for AI coding assistants?

Enforces strict context-tree lifetime propagation across nested Chi HTTP middleware chains and async background routines. Precludes orphaned goroutines and silent request cancellation leaks by requiring structured context derivation and verifying deterministic termination via Go 1.24 testing/synctest virtual bubbles. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Spawning Unbound Asynchronous Goroutines with Request Context or Raw context.Background Inside Chi Middleware) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related BACKEND Rules

View all rules →

Fastify 5 Schema Compilers & Encapsulation Production Standard

Fastify relies on lexical encapsulation contexts to sandbox decorators, hooks, and compiled validation/serialization schemas without memory leaks or cross-tenant bleed. In Fastify 5, misuse of global compilers or failing to encapsulate plugin boundaries causes compiled `fast-json-stringify` serializers and Ajv validators to either crash on duplicate IDs, leak private data across sibling scopes, or bypass JIT compilation optimizations. Production services must enforce strict encapsulation hierarchies and type-safe schema compilation across every routing subtree.

Bun Embedded SQLite WAL Mode & Transaction Synchronization Standard

Production database standard for bun:sqlite. Mandates enabling Write-Ahead Logging (PRAGMA journal_mode = WAL), busy timeouts, and using db.transaction() for atomic operations without lock starvation.

Drizzle ORM Batch API & Interactive Transaction Isolation Standard

Production database standard for Drizzle ORM (PostgreSQL & MySQL). Mandates using db.batch() over HTTP drivers to prevent round-trip waterfalls, explicit db.transaction() with serializable/read-committed isolation, and strictly avoids unawaited query promises.

1 Rule in Stack

Go