@magnusekdahl/parallix 1.1.1 → 1.2.1

package/config/integration-pipelines.json

@@ -0,0 +1,9 @@
+{
+  "gates": {
+    "lib": {
+      "command": "./scripts/verify-local.sh static-analysis",
+      "order": 1,
+      "run_last": false
+    }
+  }
+}

package/docs/adr/0032-mission-refinement-state-and-usage-budget-signals.md

@@ -55,22 +55,23 @@ Also adopt one explicit place for selection metadata:
 
 `## Refinement Signals` must contain:
 
-- `Estimated agent % usage limit`: one of `0-25%`, `25-50%`, `50-75%`, `75-100%`, `100%+`
+- `Predicted NEL bucket`: one of `Small (0–80)`, `Medium (81–235)`, `Large (235+)` per ADR 0047
 - `Confidence`: `High`, `Medium`, or `Low`
 - `Selection note`: `activate as-is`, `split first`, or `defer`, with one short reason
 - `Main drivers`: the 2-4 factors driving the estimate
 
-Interpretation rule for `% usage limit`:
+Interpretation rule for NEL bucket:
 
-- it is an approximate share of a meaningful AI-assisted execution budget under the current repo workflow
+- it is an approximate measure of engineering change volume (insertions + deletions, whitespace-ignored) for the mission's merge diff against the primary branch
 - it may reflect scope breadth, trust-tier sensitivity, validation burden, review/handoff overhead, context churn, and cross-surface coupling
 - it is a selection aid, not a delivery promise or pseudo-scientific schedule estimate
+- NEL is computed by the reusable `nels` module (`lib/core/nels.js`) which excludes workflow/bookkeeping files per ADR 0047
 
 Default activation guidance:
 
-- `0-25%` or `25-50%`: normally safe to activate as-is when confidence is not low
-- `50-75%`: split first unless the mission is unusually high leverage and already sharply bounded
-- `75-100%` or `100%+`: defer or split before activation under normal conditions
+- `Small (0–80)`: normally safe to activate as-is when confidence is not low
+- `Medium (81–235)`: split first unless the mission is unusually high leverage and already sharply bounded
+- `Large (235+)`: defer or split before activation under normal conditions
 - if confidence is `Low`, keep refining instead of treating the estimate as reliable enough for pickup
 
 Current rollout blocker:
@@ -84,14 +85,14 @@ Current rollout blocker:
 
 - The workflow now distinguishes "not ready yet" from "ready, but not yet started."
 - Mission comparison becomes more deliberate because shovel-ready candidates can be compared without immediately activating them.
-- The `% usage limit` signal is lightweight enough to aid selection without creating a second planning system.
+- The NEL bucket signal is lightweight enough to aid selection without creating a second planning system.
 - `MISSION.md` remains the detailed execution contract while Backlog stays the current-state surface.
 
 ### Negative
 
 - The lifecycle gains one more state conceptually, so operators must learn one more transition.
 - Some older workflow docs and historical artifacts will continue to mention the earlier five-state model.
-- `% usage limit` still depends on judgment and may drift if agents stop recording the main drivers behind the estimate.
+- NEL bucket estimates still depend on judgment and may drift if agents stop recording the main drivers behind the estimate.
 
 ## Alternatives Considered
 
@@ -132,4 +133,5 @@ Negative:
 ## Links
 
 - [ADR 0026](0026-ai-task-state-and-agent-recovery-surface.md)
+- [ADR 0047: Per-Mission Change Size Budget](0047-per-mission-change-size-budget.md) — NEL bucket definitions and exclusion globs
 - [Mission](../missions/2026/task-024-mission-complexity-estimation/MISSION.md)

package/docs/adr/0036-mission-sizing-and-dependency-wave-heuristics.md

@@ -18,21 +18,21 @@ Introduce three sizing tracks and a dependency-wave planning heuristic.
 
 ### 1. Sizing Tracks
 
-| Track | Scope | Process | Agent Budget |
-|-------|-------|---------|--------------|
-| **Quick Flow** | < 3 files, < 2h estimated, or docs-only. | Minimal `MISSION.md` (Goal, Why Now, Refinement Signals, Gates). Skip detailed checkpoints if straightforward. | < 10% of agent limit |
-| **Full Method** | > 3 files, complex logic, or > 2h. | Standard `MISSION.md` with all sections. Detailed checkpoints. Mandatory external review (C2 review remains required for sensitive scopes per AGENTS.md). | 10-50% of agent limit |
-| **Multi-Wave** | Very large, high risk, or complex dependencies. | Split into multiple `Full Method` missions (waves). | Total > 50% (requiring split) |
+| Track | Scope | Process | NEL Budget |
+|-------|-------|---------|------------|
+| **Quick Flow** | < 3 files, < 2h estimated, or docs-only. | Minimal `MISSION.md` (Goal, Why Now, Refinement Signals, Gates). Skip detailed checkpoints if straightforward. | 0–80 NEL (Small) |
+| **Full Method** | > 3 files, complex logic, or > 2h. | Standard `MISSION.md` with all sections. Detailed checkpoints. Mandatory external review (C2 review remains required for sensitive scopes per AGENTS.md). | 81–235 NEL (Medium) |
+| **Multi-Wave** | Very large, high risk, or complex dependencies. | Split into multiple `Full Method` missions (waves). | 235+ NEL (Large) |
 
-### 2. "Too Large" Thresholds by Agent
+### 2. "Too Large" Thresholds
 
-A mission is "Too Large" if its `Estimated agent % usage limit` exceeds the following thresholds per session/work-unit:
+A mission is "Too Large" for single-wave execution when its predicted NEL bucket exceeds the following thresholds:
 
-- **Claude**: > 50% of daily limit.
-- **Codex**: > 25% of weekly limit.
-- **Gemini**: > 50% of the reasonable session/context budget (approx. 50k-100k tokens for execution).
+- **Small (0–80 NEL)**: suitable for Quick Flow; no decomposition needed.
+- **Medium (81–235 NEL)**: suitable for Full Method; consider splitting if dependencies are complex.
+- **Large (235+ NEL)**: MUST be split into dependency waves before activation.
 
-Missions exceeding these thresholds MUST be split into dependency waves before activation.
+These thresholds are derived from empirical terciles in task-1355 data (n=29 missions) as documented in ADR 0047. Missions exceeding these thresholds MUST be split into dependency waves before activation.
 
 ### 3. Dependency-Wave Heuristic
 
@@ -70,10 +70,12 @@ Agents MUST assign themselves to a task in `Backlog.md` before beginning work in
 - Improved visibility of parallel work via mandatory assignment.
 
 ### Negative
+
 - Requires upfront estimation effort during the `draft` phase.
-- Agents must learn to judge their own usage limits accurately.
+- Agents must estimate NEL buckets, which requires understanding the exclusion rules from ADR 0047.
 
 ## Links
 - [ADR 0032](0032-mission-refinement-state-and-usage-budget-signals.md)
+- [ADR 0047: Per-Mission Change Size Budget](0047-per-mission-change-size-budget.md) — NEL bucket definitions and exclusion globs
 - [MISSION_FLOW.md](../../MISSION_FLOW.md)
 - [AGENTS.md](../../AGENTS.md)

package/docs/adr/0041-integration-pipeline-gates.md

@@ -145,7 +145,7 @@ Option B (Forgejo Actions) would require runner credentials for docker push and
 
 ## Deliverables
 
-1. **Repo-side config:** `config/integration-pipelines.json` with entries for `server`, `auth-server`, `web-client`, `web-e2e`; `web-e2e` carries `run_last: true`
+1. **Repo-side config:** `config/integration-pipelines.json` with entries for `server`, `auth-server`, `web-client`, `web-e2e`; `web-e2e` carries `run_last: true`. Task-1362 added a `lib` entry mapping to `./scripts/verify-local.sh static-analysis` as a required gate for `lib/` changes.
 2. **Change detection:** Compute the set of top-level dirs touched by `mission/<slug>` vs the primary branch
 3. **Dispatch in `scripts/verify-local.sh`:** New `gate_integrate()` function and `integrate` area in the case statement
 4. **`node workflow integrate` preflight:** Calls the new `integrate` area as part of `printIntegrationPreflight`