[dnth]

Summary

Supervisor notification path after this change:

wake candidate
├─ check / stale / heartbeat / decision-owned / afk
│  └─ deliver now  (+ flush pending echo batch into the same queue)
├─ signal with needs-decision|blocked|done|failed in the new span
│  └─ deliver now  (+ flush pending echo batch)
└─ signal echo (status-only or bare turn-end)
   ├─ state/.echo-batch   window: config/wake-echo-batch
   │                      (default 120s; 60-300; or off)
   ├─ window due / immediate wake -> one `signal:` wake, one row per file
   └─ wholly turn-ended batch + active blocking pane
      ├─ every gate key decided for its current run -> drop (answered-gate)
      └─ every crew-state line identical to the last delivered wake and no
         steer since -> drop (no-change)

Upstream attribution:

• Adapted from upstream fix(bin): absorb turn-end wakes during bounded pane churn kunchenguid/firstmate#2877, "absorb turn-end wakes during bounded pane churn" (cherry picked from commit a56a78a).
• Adapted from upstream feat(bin): defer the wedge escalation for a lane parked at a supervisor-owed gate kunchenguid/firstmate#4974, "defer the wedge escalation for a lane parked at a supervisor-owed gate" (cherry picked from commit 9aabe3b).

Evidence

• Before: every turn-end boundary woke the supervisor; the 2026-11-06 replay measured 53 turn-ended-only wakes, 40 of which produced nothing.
  After: three echoes in one window produce exactly one delivered wake with three durable rows; a restart inherits and flushes the same batch.
• Before: a lane parked at an unanswered supervisor gate kept climbing the wedge ladder, and a payload-wide ask-user substring minted the human-owed verdict from free text.
  After: the gate's action column is read by position, the verdict is bound to its current nm-<run>-<step>, and only an open decision for that run takes the bounded recheck. Crewmate-owned, answered, reopened, wrong-run, and unrelated-key gates keep the ladder.
• Deterministic coverage: tests/fm-watch-triage.test.sh 117 ok / 0 not ok, including batching, restart persistence, immediate classes, both drop rules with near misses, and the parked-gate ladder; tests/fm-crew-state.test.sh covers the real producer and the action-column counterexamples.
• Live OMP on the final head: a real fm_watch_arm_omp primary with two spawned OMP workers deferred two real turn-end echoes and delivered them in one wake (entries=2, one primary watcher-wake message); a Discord-shaped ext-request was delivered in 0s while the batch was pending (window 120s).
• Test exception: the pipeline's two live parked-gate scenarios were inconclusive and approved as an exception; their deterministic coverage drives the real producer. CI: 18/18 checks green.

Merge Danger

Door: two-way

Blast Radius: supervision-only

Watcher-only behavior; no project, model, or network path changes. Both upstream ports remain opt-in (config/turnend-churn-absorb, config/wedge-defer-parked-gate); batching is default-on at 120s and can be disabled with config/wake-echo-batch = off. Drops are limited to wholly turn-ended batches with positive evidence and are logged with their rule name.

Pipeline

Updates from git push no-mistakes

✅ **Intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

🔧 **Review** - 6 issues found → auto-fixed (5) ✅

• 🚨 bin/fm-watch.sh:2338 - R2 does not bind answer evidence to the current gate. After run A's review is answered, a turn-end at run B's unanswered gate can reuse A's latest status key and historical resolution, causing the batch to be dropped. Reopening the same key also retains the earlier resolution as proof. Validate the current run/step and latest decision occurrence before dropping. Related sites: bin/fm-watch.sh:2262 selects an unbound historical key; :2287 accepts any historical resolution; :2291-2293 accepts substring matches in handled messages; :2336-2340 combines these proofs.
• 🚨 bin/fm-watch.sh:2372 - R3 misses steers sent within the delivery's second. A delivery at 1000.1 followed by fm-send at 1000.5 gives both records epoch 1000; the strict greater-than comparison allows an unchanged blocked echo to be dropped despite that steer. Treat equal timestamps as an ambiguous near miss and deliver. Related sites: bin/fm-watch.sh:2233 and :2446 create second-resolution baselines; :2369-2372 checks pending and handled inbox records.
• 🚨 bin/fm-watch.sh:2412 - A persisted ordinary-mode batch can survive into away mode, then be dropped by R2/R3 before the daemon receives it. New signals correctly bypass batching under .afk, but inherited batches do not. Apply the away-mode ownership guard at the shared flush boundary and promptly deliver inherited batches without watcher-side drops. Related sites: bin/fm-watch.sh:2199-2201 retains the normal deadline; :2412-2427 applies both drops; :3015 flushes before away-mode classification; :3294-3298 guards only new signals.
• ⚠️ bin/fm-crew-state.sh:455 - The findings parser still mistakes commas inside file paths for column separators. With the normal header, an auto-fix finding for "src/a,b,ask-user,c.ts" places ask-user at the raw fifth comma field and incorrectly mints the human-decision marker. Parse quoted fields correctly or reject ambiguous rows. Related sites: bin/fm-crew-state.sh:442 incorrectly treats file values as comma-free; :459-460 accepts the shifted field; :677 emits the incorrect marker consumed by bin/fm-classify-lib.sh:2171.
• ⚠️ bin/fm-watch.sh:2091 - Numeric configuration is validated as decimal but retained for shell arithmetic: 060 passes the range check and becomes a 48-second window, while 090 causes an invalid-octal arithmetic error. Oversized digit strings can also survive failed range comparisons. Normalize bounded decimal input or reject noncanonical values in the resolver. Related sites: bin/fm-watch.sh:2087 validates; :2091 retains the raw value; :2106 checks enablement; :2196 performs arithmetic.
• ⚠️ bin/fm-watch.sh:2078 - Simplification: the additional OFF/false/FALSE/no/NO disable aliases are unnecessary for the requested configurable batching window and exceed the documented off spelling. Remove these aliases and retain the narrower documented configuration surface unless broader spellings are explicitly desired.

🔧 Fix applied.
10 issues (5 errors, 5 warnings) still open:

• 🚨 bin/fm-watch.sh:2338 - R2 does not bind answer evidence to the current gate. After run A's review is answered, a turn-end at run B's unanswered gate can reuse A's latest status key and historical resolution, causing the batch to be dropped. Reopening the same key also retains the earlier resolution as proof. Validate the current run/step and latest decision occurrence before dropping. Related sites: bin/fm-watch.sh:2262 selects an unbound historical key; :2287 accepts any historical resolution; :2291-2293 accepts substring matches in handled messages; :2336-2340 combines these proofs.
• 🚨 bin/fm-watch.sh:2372 - R3 misses steers sent within the delivery's second. A delivery at 1000.1 followed by fm-send at 1000.5 gives both records epoch 1000; the strict greater-than comparison allows an unchanged blocked echo to be dropped despite that steer. Treat equal timestamps as an ambiguous near miss and deliver. Related sites: bin/fm-watch.sh:2233 and :2446 create second-resolution baselines; :2369-2372 checks pending and handled inbox records.
• 🚨 bin/fm-watch.sh:2412 - A persisted ordinary-mode batch can survive into away mode, then be dropped by R2/R3 before the daemon receives it. New signals correctly bypass batching under .afk, but inherited batches do not. Apply the away-mode ownership guard at the shared flush boundary and promptly deliver inherited batches without watcher-side drops. Related sites: bin/fm-watch.sh:2199-2201 retains the normal deadline; :2412-2427 applies both drops; :3015 flushes before away-mode classification; :3294-3298 guards only new signals.
• ⚠️ bin/fm-crew-state.sh:455 - The findings parser still mistakes commas inside file paths for column separators. With the normal header, an auto-fix finding for "src/a,b,ask-user,c.ts" places ask-user at the raw fifth comma field and incorrectly mints the human-decision marker. Parse quoted fields correctly or reject ambiguous rows. Related sites: bin/fm-crew-state.sh:442 incorrectly treats file values as comma-free; :459-460 accepts the shifted field; :677 emits the incorrect marker consumed by bin/fm-classify-lib.sh:2171.
• ⚠️ bin/fm-watch.sh:2091 - Numeric configuration is validated as decimal but retained for shell arithmetic: 060 passes the range check and becomes a 48-second window, while 090 causes an invalid-octal arithmetic error. Oversized digit strings can also survive failed range comparisons. Normalize bounded decimal input or reject noncanonical values in the resolver. Related sites: bin/fm-watch.sh:2087 validates; :2091 retains the raw value; :2106 checks enablement; :2196 performs arithmetic.
• ⚠️ bin/fm-watch.sh:2078 - Simplification: the additional OFF/false/FALSE/no/NO disable aliases are unnecessary for the requested configurable batching window and exceed the documented off spelling. Remove these aliases and retain the narrower documented configuration surface unless broader spellings are explicitly desired.
• 🚨 bin/fm-watch.sh:2429 - A pending echo batch deadlocks process-event delivery. procevent_surface_queued holds FM_WAKE_QUEUE_LOCK until its post-output callback, but the new pre-output hook calls echo_batch_flush, which calls fm_wake_append and waits indefinitely for that same non-reentrant lock. Neither the immediate check nor subsequent wakes can print. Flush before acquiring the process-event lock, or append under its existing ownership. Related sites: bin/fm-push-transition-lib.sh:102 invokes the hook; bin/fm-watch.sh:2461 flushes; :2537 acquires the lock; :2549 installs its deferred release.
• 🚨 bin/fm-crew-state.sh:677 - The required parked-gate deferral and answered-gate drop are unreachable with the real producer. This hunk adds only the human-decision marker; fm-crew-state never emits a 'run: <id>' component. Both bin/fm-classify-lib.sh:2167-2169 and bin/fm-watch.sh:2320-2324 require it and therefore always reject real parked gates. This omits the required 'defer the wedge escalation ... supervisor-owed gate' behavior and R2's 'drop the echo' behavior. Round 1's R1 fix moved the drop onto this nonexistent field and left the producer and original deferral sibling inconsistent. Supply the attributed run identity through the shared producer boundary for both consumers; the watcher tests currently manufacture that component themselves.
• ⚠️ bin/fm-watch.sh:2068 - Simplification: FM_ECHO_BATCH_SECS introduces a second configuration surface and precedence rule beyond the requested config-file window ('Configuration lives in config/'). Remove the environment override and use config/wake-echo-batch, including in test fixtures. Related definitions: docs/configuration.md:197 and :1400.
• ⚠️ bin/fm-watch.sh:645 - Simplification: remove the unused signal_statuses array and status-specific bookkeeping (:623, :645-647), plus the uncalled echo_batch_window wrapper (:2100-2103). No intent requirement needs either component: status files already return at :630, and all window consumers call echo_batch_resolve directly.

🔧 Fix applied.
9 issues (5 errors, 4 warnings) still open:

• 🚨 bin/fm-watch.sh:2338 - R2 does not bind answer evidence to the current gate. After run A's review is answered, a turn-end at run B's unanswered gate can reuse A's latest status key and historical resolution, causing the batch to be dropped. Reopening the same key also retains the earlier resolution as proof. Validate the current run/step and latest decision occurrence before dropping. Related sites: bin/fm-watch.sh:2262 selects an unbound historical key; :2287 accepts any historical resolution; :2291-2293 accepts substring matches in handled messages; :2336-2340 combines these proofs.
• 🚨 bin/fm-watch.sh:2372 - R3 misses steers sent within the delivery's second. A delivery at 1000.1 followed by fm-send at 1000.5 gives both records epoch 1000; the strict greater-than comparison allows an unchanged blocked echo to be dropped despite that steer. Treat equal timestamps as an ambiguous near miss and deliver. Related sites: bin/fm-watch.sh:2233 and :2446 create second-resolution baselines; :2369-2372 checks pending and handled inbox records.
• 🚨 bin/fm-watch.sh:2412 - A persisted ordinary-mode batch can survive into away mode, then be dropped by R2/R3 before the daemon receives it. New signals correctly bypass batching under .afk, but inherited batches do not. Apply the away-mode ownership guard at the shared flush boundary and promptly deliver inherited batches without watcher-side drops. Related sites: bin/fm-watch.sh:2199-2201 retains the normal deadline; :2412-2427 applies both drops; :3015 flushes before away-mode classification; :3294-3298 guards only new signals.
• ⚠️ bin/fm-watch.sh:2091 - Numeric configuration is validated as decimal but retained for shell arithmetic: 060 passes the range check and becomes a 48-second window, while 090 causes an invalid-octal arithmetic error. Oversized digit strings can also survive failed range comparisons. Normalize bounded decimal input or reject noncanonical values in the resolver. Related sites: bin/fm-watch.sh:2087 validates; :2091 retains the raw value; :2106 checks enablement; :2196 performs arithmetic.
• ⚠️ bin/fm-watch.sh:2078 - Simplification: the additional OFF/false/FALSE/no/NO disable aliases are unnecessary for the requested configurable batching window and exceed the documented off spelling. Remove these aliases and retain the narrower documented configuration surface unless broader spellings are explicitly desired.
• 🚨 bin/fm-watch.sh:2429 - A pending echo batch deadlocks process-event delivery. procevent_surface_queued holds FM_WAKE_QUEUE_LOCK until its post-output callback, but the new pre-output hook calls echo_batch_flush, which calls fm_wake_append and waits indefinitely for that same non-reentrant lock. Neither the immediate check nor subsequent wakes can print. Flush before acquiring the process-event lock, or append under its existing ownership. Related sites: bin/fm-push-transition-lib.sh:102 invokes the hook; bin/fm-watch.sh:2461 flushes; :2537 acquires the lock; :2549 installs its deferred release.
• ⚠️ bin/fm-watch.sh:2068 - Simplification: FM_ECHO_BATCH_SECS introduces a second configuration surface and precedence rule beyond the requested config-file window ('Configuration lives in config/'). Remove the environment override and use config/wake-echo-batch, including in test fixtures. Related definitions: docs/configuration.md:197 and :1400.
• ⚠️ bin/fm-watch.sh:645 - Simplification: remove the unused signal_statuses array and status-specific bookkeeping (:623, :645-647), plus the uncalled echo_batch_window wrapper (:2100-2103). No intent requirement needs either component: status files already return at :630, and all window consumers call echo_batch_resolve directly.
• 🚨 bin/fm-watch.sh:2348 - Round 1's R2 timestamp fix leaves an acknowledgment race. Both globs expand before iteration; if a worker then moves a newer steer from the inbox into handled/, the expanded pending path disappears and is skipped, while its handled path was never enumerated. With unchanged crew state and a blocking pane, R3 incorrectly drops the echo despite that steer. Treat disappearing enumerated records and failed timestamp reads as ambiguous evidence requiring delivery. Related sites: bin/fm-watch.sh:2347 expands both inbox locations; :2348 skips disappeared records; :2349-2350 ignores timestamp-read failure.

🔧 Fix applied.
11 issues (7 errors, 4 warnings) still open:

• 🚨 bin/fm-watch.sh:2338 - R2 does not bind answer evidence to the current gate. After run A's review is answered, a turn-end at run B's unanswered gate can reuse A's latest status key and historical resolution, causing the batch to be dropped. Reopening the same key also retains the earlier resolution as proof. Validate the current run/step and latest decision occurrence before dropping. Related sites: bin/fm-watch.sh:2262 selects an unbound historical key; :2287 accepts any historical resolution; :2291-2293 accepts substring matches in handled messages; :2336-2340 combines these proofs.
• 🚨 bin/fm-watch.sh:2372 - R3 misses steers sent within the delivery's second. A delivery at 1000.1 followed by fm-send at 1000.5 gives both records epoch 1000; the strict greater-than comparison allows an unchanged blocked echo to be dropped despite that steer. Treat equal timestamps as an ambiguous near miss and deliver. Related sites: bin/fm-watch.sh:2233 and :2446 create second-resolution baselines; :2369-2372 checks pending and handled inbox records.
• 🚨 bin/fm-watch.sh:2412 - A persisted ordinary-mode batch can survive into away mode, then be dropped by R2/R3 before the daemon receives it. New signals correctly bypass batching under .afk, but inherited batches do not. Apply the away-mode ownership guard at the shared flush boundary and promptly deliver inherited batches without watcher-side drops. Related sites: bin/fm-watch.sh:2199-2201 retains the normal deadline; :2412-2427 applies both drops; :3015 flushes before away-mode classification; :3294-3298 guards only new signals.
• ⚠️ bin/fm-watch.sh:2091 - Numeric configuration is validated as decimal but retained for shell arithmetic: 060 passes the range check and becomes a 48-second window, while 090 causes an invalid-octal arithmetic error. Oversized digit strings can also survive failed range comparisons. Normalize bounded decimal input or reject noncanonical values in the resolver. Related sites: bin/fm-watch.sh:2087 validates; :2091 retains the raw value; :2106 checks enablement; :2196 performs arithmetic.
• ⚠️ bin/fm-watch.sh:2078 - Simplification: the additional OFF/false/FALSE/no/NO disable aliases are unnecessary for the requested configurable batching window and exceed the documented off spelling. Remove these aliases and retain the narrower documented configuration surface unless broader spellings are explicitly desired.
• 🚨 bin/fm-watch.sh:2429 - A pending echo batch deadlocks process-event delivery. procevent_surface_queued holds FM_WAKE_QUEUE_LOCK until its post-output callback, but the new pre-output hook calls echo_batch_flush, which calls fm_wake_append and waits indefinitely for that same non-reentrant lock. Neither the immediate check nor subsequent wakes can print. Flush before acquiring the process-event lock, or append under its existing ownership. Related sites: bin/fm-push-transition-lib.sh:102 invokes the hook; bin/fm-watch.sh:2461 flushes; :2537 acquires the lock; :2549 installs its deferred release.
• ⚠️ bin/fm-watch.sh:2068 - Simplification: FM_ECHO_BATCH_SECS introduces a second configuration surface and precedence rule beyond the requested config-file window ('Configuration lives in config/'). Remove the environment override and use config/wake-echo-batch, including in test fixtures. Related definitions: docs/configuration.md:197 and :1400.
• ⚠️ bin/fm-watch.sh:645 - Simplification: remove the unused signal_statuses array and status-specific bookkeeping (:623, :645-647), plus the uncalled echo_batch_window wrapper (:2100-2103). No intent requirement needs either component: status files already return at :630, and all window consumers call echo_batch_resolve directly.
• 🚨 bin/fm-watch.sh:2348 - Round 1's R2 timestamp fix leaves an acknowledgment race. Both globs expand before iteration; if a worker then moves a newer steer from the inbox into handled/, the expanded pending path disappears and is skipped, while its handled path was never enumerated. With unchanged crew state and a blocking pane, R3 incorrectly drops the echo despite that steer. Treat disappearing enumerated records and failed timestamp reads as ambiguous evidence requiring delivery. Related sites: bin/fm-watch.sh:2347 expands both inbox locations; :2348 skips disappeared records; :2349-2350 ignores timestamp-read failure.
• 🚨 bin/fm-watch.sh:2347 - R3 treats inbox history as complete steer history, but fm-send explicitly routes slash commands, Codex dollar invocations, explicit endpoint messages, and keys through its typed plane without creating inbox records (bin/fm-send.sh:1020-1031, :1069-1078). After a delivered baseline, a typed steer can start another turn that leaves the crew-state line unchanged and blocks again; its echo is then incorrectly dropped. The prior rounds' inbox timestamp fixes leave these sibling delivery paths uncovered. Invalidate the existing delivered baseline at the shared task-bound send boundary for every steering plane, so typed steering cannot authorize a no-change drop.
• 🚨 bin/fm-watch.sh:634 - The new marker parsers truncate valid task IDs at the first '.turn-ended' occurrence. For tasks alpha and alpha.turn-ended.beta, the live marker alpha.turn-ended.beta.turn-ended.g1 passes incarnation filtering correctly, but this parser resolves it to alpha. With churn absorption enabled, alpha's working verdict can swallow the stopped task's wake; batching can likewise use alpha's answered-gate or unchanged-state evidence to drop it. The same invariant is violated at bin/fm-watch.sh:2232 (delivery baselines) and :2385 (both batch drop rules). Strip only the final marker suffix, matching the existing parsers at :2471 and bin/fm-classify-lib.sh:2294.

🔧 Fix applied.
1 error still open:

• 🚨 bin/fm-send.sh:1004 - Round 4's typed-steer fix leaves concurrent baseline access unsynchronized. The watcher can read a baseline, fm-send can delete it and deliver a typed steer, and the watcher can still drop the batch using its cached values because typed steering creates no inbox record. Conversely, fm-send deletes the baseline before actual transport; a concurrent wake can recreate it before the steer lands, allowing subsequent echoes to drop despite that steer. Coordinate invalidation, baseline publication, and the final drop decision at a shared task boundary. Related sites: bin/fm-watch.sh:2333-2355 reads and accepts invalidated evidence; bin/fm-watch.sh:2203-2211 publishes replacement evidence; bin/fm-watch.sh:2403-2408 commits the drop; bin/fm-send.sh:1004 invalidates before transport.

🔧 Fix applied.
✅ Re-checked - no issues remain.

⚠️ **Test** - 1 warning

• ⚠️ live validation verdict: inconclusive (10 of 12 scenarios were driven live against the product); untested: A real answered parked gate drops its echo while wrong-run, reopened, and unanswered gates deliver, A real supervisor-owned parked gate defers wedge escalation while worker-owned and unrelated decisions retain escalation
• Live validation: ⚠️ inconclusive - 10 of 12 scenarios driven live against the product

Scenario	Result	Live	Evidence
Local OMP groups two synthetic task turn-end markers into one native notification after the real 60-second window	✅ pass	live	omp-notification-oracle.json; omp-session.jsonl; omp-live.log
A local Discord-shaped ext-request check reaches real OMP immediately and flushes pending echoes	✅ pass	live	omp-result.json; omp-notification-oracle.json; captain-live.log
The local watcher preserves a synthetic batch across restart and groups status-only records with turn-end echoes	✅ pass	live	restart.txt; mixed-status.txt
Synthetic decision, blocked, done, and failed events bypass the local batch and flush pending echoes	✅ pass	live	immediate-needs-decision.txt; immediate-blocked.txt; immediate-done.txt; immediate-failed.txt
Local checks, a real idle tmux pane, and a process-event publication immediately flush pending echoes without deadlock	✅ pass	live	immediate-check.txt; immediate-stale.txt; procevent-live.txt
Entering away mode delivers an inherited local batch without watcher-side drops	✅ pass	live	afk-inherited.txt
Local configuration disables batching, selects 300 seconds, and safely rejects malformed numeric windows	✅ pass	live	config-off.txt; config-090.txt; config-9999999999999999999999999999.txt; config-300.txt
An opted-in changing tmux pane absorbs a synthetic turn-end only within the configured churn bound	✅ pass	live	churn.txt
An unchanged local echo drops under a real OMP blocking display, but a typed steer forces subsequent delivery	✅ pass	live	blocking-drop-result.txt; omp-active-blocking-pane.txt; typed-steer-result.txt
Captain input reaches local OMP while an echo batch is still pending	✅ pass	live	captain-input-result.json; captain-live.log
A real answered parked gate drops its echo while wrong-run, reopened, and unanswered gates deliver	⏸️ untested	no	Ran targeted producer and watcher regressions, but their no-mistakes boundary is mocked. Preparing a real parked run requires initialization or pipeline control expressly forbidden in this phase. The…
A real supervisor-owned parked gate defers wedge escalation while worker-owned and unrelated decisions retain escalation	⏸️ untested	no	Targeted behavioral regressions passed with synthetic gate responses. No isolated real parked run was available, and creating or advancing one would violate the assigned phase boundary. Supply a prepa…

• TMPDIR="$PWD/.validation/tmp" FM_WATCH_TRIAGE_TEST=test_echo_review_regressions bash tests/fm-watch-triage.test.sh
• TMPDIR="$PWD/.validation/tmp" FM_WATCH_TRIAGE_TEST=test_wedge_threshold_defers_to_a_parked_gate_awaiting_a_human bash tests/fm-watch-triage.test.sh
• TMPDIR="$PWD/.validation/tmp" bash tests/fm-send-inbox.test.sh
• TMPDIR="$PWD/.validation/tmp" bash tests/fm-crew-state.test.sh
• python3 .validation/watcher-live.py
• python3 .validation/churn-live.py
• python3 .validation/stale-live.py
• python3 .validation/block-live.py
• python3 .validation/omp-live.py
• python3 .validation/captain-live.py
• Verified native OMP session records contain exactly one combined task notification and a separate ext-request notification.
• Reviewed other supported primary integration paths and backend capture interfaces; details retained in validation-notes.txt.
• Exported the OMP session and attempted Chrome rendering; closed the temporary tab after the export viewer's Highlight dependency failed.
• Collected child exit statuses, stopped disposable processes, removed temporary homes, and confirmed a clean worktree.

✅ **Document** - passed

✅ No issues found.

🔧 **Lint** - 1 issue found → auto-fixed ✅

• ⚠️ linter found issues (exit code 1)

🔧 Fix applied.
✅ Re-checked - no issues remain.

✅ **Push** - passed

✅ No issues found.