Issues

[finding] a liveness ledger `status` is free text — a typo'd value is classified and counted by the walk, then dropped by `foldStateCounts`, so state-counts.md publishes an understated total and CI stays green

#13083

· os-trump opened

on Aug 29, 2026

[finding] check-adr-0087-registration has no honest disposition for a published TYPE-surface narrowing — every category is refused, so the class is pushed to drop the `BREAKING` token instead

#13080

· os-litant opened

on Aug 29, 2026

`client.analytics.query` / `meta` / `explain` and `automation.trigger` hand callers the RAW dispatcher envelope while every sibling unwraps it — one SDK, two calling conventions

#13079

· os-litant opened

on Aug 29, 2026

Two `packages/spec` route response schemas declare a `data` NARROWER than the contract their route relays — `AnalyticsResultResponseSchema` and `TriggerFlowResponseSchema`

#13078

· os-litant opened

on Aug 29, 2026

Two docs pages and one lint gate epilogue still teach the retired "no `current_user` at section level" claim (prose half, split from #13072)

#13077

· huangyiirene opened

on Aug 29, 2026

finding: driver-mongodb still lowers `array_agg` / `string_agg` — retired from `AggregationFunction` at #6188, refused by both SQL faces

#13075

· os-zhuang opened

on Aug 29, 2026

Three more consumers of the "no `current_user` at section level" claim go stale the moment #12914 lands — one of them is a live runtime detector, not prose

#13072

· os-trump opened

on Aug 29, 2026

The body sanitizer deletes an exclamation mark before a bracket with NO preceding less-than — so a quoted TypeScript non-null assertion is silently corrupted, and the recorded rule says the trigger needs a less-than

#13071

· os-trump opened

on Aug 29, 2026

Three broken-sweep mentions in `packages/spec/src/automation` still call the predicate an alert / a query that can tell — the residue outside the fences of #12722 and #12900

#13063

· os-trump opened

on Aug 29, 2026

[finding] `os serve` publishes the REQUESTED port, not the bound one — with `--port 0` it announces a port nothing is listening on, and the code comment asserts the opposite

#13062

· os-litant opened

on Aug 29, 2026

driver-sql: dropping an orphaned hash-shadow-carried index leaves its generated column behind forever, contradicting the cleanup contract isHashShadowColumn states

#13056

· os-zhuang opened

on Aug 29, 2026

finding(lint): a runtime-gate test fixture spells `reference: { object: ... }`, a carrier `ObjectSchema` refuses and the rule's own reader ignores

#13053

· os-sales opened

on Aug 29, 2026

Navigation Menu

Uh oh!

All issues

[finding] a liveness ledger `status` is free text — a typo'd value is classified and counted by the walk, then dropped by `foldStateCounts`, so state-counts.md publishes an understated total and CI stays green

[finding] check-adr-0087-registration has no honest disposition for a published TYPE-surface narrowing — every category is refused, so the class is pushed to drop the `BREAKING` token instead

`client.analytics.query` / `meta` / `explain` and `automation.trigger` hand callers the RAW dispatcher envelope while every sibling unwraps it — one SDK, two calling conventions

Two `packages/spec` route response schemas declare a `data` NARROWER than the contract their route relays — `AnalyticsResultResponseSchema` and `TriggerFlowResponseSchema`

Two docs pages and one lint gate epilogue still teach the retired "no `current_user` at section level" claim (prose half, split from #13072)

finding: driver-mongodb still lowers `array_agg` / `string_agg` — retired from `AggregationFunction` at #6188, refused by both SQL faces

Three more consumers of the "no `current_user` at section level" claim go stale the moment #12914 lands — one of them is a live runtime detector, not prose

The body sanitizer deletes an exclamation mark before a bracket with NO preceding less-than — so a quoted TypeScript non-null assertion is silently corrupted, and the recorded rule says the trigger needs a less-than

Three broken-sweep mentions in `packages/spec/src/automation` still call the predicate an alert / a query that can tell — the residue outside the fences of #12722 and #12900

[finding] `os serve` publishes the REQUESTED port, not the bound one — with `--port 0` it announces a port nothing is listening on, and the code comment asserts the opposite

driver-sql: dropping an orphaned hash-shadow-carried index leaves its generated column behind forever, contradicting the cleanup contract isHashShadowColumn states

finding(lint): a runtime-gate test fixture spells `reference: { object: ... }`, a carrier `ObjectSchema` refuses and the rule's own reader ignores

Uh oh!

Search results