Skip to content

pullrequests Search Results · language:Edge language:Python language:JavaScript language:Python language:Python language:Python

Filter by

35.6M results  (2 s)

35.6M results

Summary Introduces an adaptive grid-state predictor that compensates for powermeter latency without per-meter tuning. The controller now acts on a predicted grid estimate instead of the raw meter reading, ...

Closes #283. Follow-up to 8.1c-3 (#281): make the multi-agent flow followable live in the chat. Problem Tool/reasoning steps streamed into the auto-open Details panel, but planner plan and critic critique ...

Summary - Implements risk-guard usecase layer (Issue #42) - CheckOrderRisk use case with full 7-step pipeline - SyncKillSwitch use case for kill-switch state changes - Idempotency deduplication ...

Phase 9B fast publish: incremental publishable_pool.json update.

🤖 AI Security Remediation 🚨 Human approval required — please review before merging. 📊 Analysis - Severity: HIGH - Confidence: 90% - Auto-fix allowed: False 📝 Summary The application uses subprocess.call ...
ai-remediation
needs-human-review
severity-high

Why A follow-up to the merged PR #8 — closing the **3 stack layers I d treated as later/covered-by-a-note ** instead of giving them real skills. No deferral: every layer of the target AI-native commerce ...

Summary - add --include support for narrowing catalog scans - add repeated and comma-separated --exclude support for custom excludes - preserve safe default excludes when custom excludes are provided ...

Implements #204. Closes #204. Task summary: The COR system has a PKG→USR→PRJ layering, and projects sometimes create a PRJ doc that instantiates or overlays a COR doc (TRN-1209 ← COR-1622; CLD-1800 ← ...
clearance-3-ready-for-approval

Bumps eslint-config-next from 15.1.0 to 16.2.9. details summary Release notes /summary p em Sourced from a href= https://github.com/vercel/next.js/releases eslint-config-next s releases /a . /em /p blockquote ...

What this builds The Weekly Brief now generates automatically every Monday at 09:00 in each company s configured timezone instead of firing every ~6 hours regardless of day/time/tz. Each company s timezone ...