Issues

SeedLoader: per-record failure diagnostic embeds the composite externalId key, so its U+0000 joiner lands as a raw NUL in the server log

#16488

· os-sam opened

on Sep 7, 2026

cli: `create-objectstack` emits TypeScript `^6.0.0` while `os init` / `os create` emit `^5.3.0` — generate the on-ramp's version policy from the same constants at build time (item 4 of #15531)

#16485

· os-zhuang opened

on Sep 7, 2026

docs(cli): `plugin` means two different things in `os init -t plugin` and `os create plugin` — disambiguate the word and fix the "Which scaffolder?" hint that sends plugin-skeleton readers to the wrong command (item 3 of #15531)

#16484

· os-zhuang opened

on Sep 7, 2026

cli: retire `os create example` — it is a weaker `os init` plus a README; docs point at `os init` (item 2 of #15531)

#16483

· os-zhuang opened

on Sep 7, 2026

ci: heavy CI never runs on a PR whose base is a feature branch — `lint.yml` / `ci.yml` `pull_request` triggers are limited to `branches: [main]`, so six required contexts report nothing on such PRs (item 3 of #16149)

#16482

· os-zhuang opened

on Sep 7, 2026

[finding] `os i18n extract --check --dry-run` exits 0 having compared nothing — a `--check` that passes without checking, i.e. a false green in CI

finding

#16480

· os-litant opened

on Sep 7, 2026

docs(ci, AGENTS.md): two sentences still say the merge queue partitions the full package list — false once PR #16471 merges

#16479

· claude opened

on Sep 7, 2026

[finding] plugin-auth comments still point at `last-admin-ban-guard.ts` — a filename that has not existed since the guard was renamed to `last-admin-guard.ts`

finding

#16477

· os-warren opened

on Sep 7, 2026

[finding] measure-test-shard-timings: a file-sharded package bypasses the median merge rule — one run wins, and slices from different runs are summed as one measurement

#16473

· claude opened

on Sep 7, 2026

[Decision] Must a resume failure reach the CALLER in a shape it can act on? — the family question triage reserved, now that its instance cards have each measured their own half and stopped at the same contract

#16472

· os-warren opened

on Sep 7, 2026

build: stop embedding source text in published source maps (`sourcesContent: false` across the tsup builds) and repair the cli package's dead `sources` references (build half of #15905 question 1)

#16469

· os-zhuang opened

on Sep 7, 2026

ci: a per-package suite-duration ratchet — a PR that makes a suite exceed its measured ceiling is red; ceilings rise only by ruling (maintainer-directed, growth constraint)

#16468

· claude opened

on Sep 7, 2026

Navigation Menu

Uh oh!

All issues

SeedLoader: per-record failure diagnostic embeds the composite externalId key, so its U+0000 joiner lands as a raw NUL in the server log

cli: `create-objectstack` emits TypeScript `^6.0.0` while `os init` / `os create` emit `^5.3.0` — generate the on-ramp's version policy from the same constants at build time (item 4 of #15531)

docs(cli): `plugin` means two different things in `os init -t plugin` and `os create plugin` — disambiguate the word and fix the "Which scaffolder?" hint that sends plugin-skeleton readers to the wrong command (item 3 of #15531)

cli: retire `os create example` — it is a weaker `os init` plus a README; docs point at `os init` (item 2 of #15531)

ci: heavy CI never runs on a PR whose base is a feature branch — `lint.yml` / `ci.yml` `pull_request` triggers are limited to `branches: [main]`, so six required contexts report nothing on such PRs (item 3 of #16149)

[finding] `os i18n extract --check --dry-run` exits 0 having compared nothing — a `--check` that passes without checking, i.e. a false green in CI

docs(ci, AGENTS.md): two sentences still say the merge queue partitions the full package list — false once PR #16471 merges

[finding] plugin-auth comments still point at `last-admin-ban-guard.ts` — a filename that has not existed since the guard was renamed to `last-admin-guard.ts`

[finding] measure-test-shard-timings: a file-sharded package bypasses the median merge rule — one run wins, and slices from different runs are summed as one measurement

[Decision] Must a resume failure reach the CALLER in a shape it can act on? — the family question triage reserved, now that its instance cards have each measured their own half and stopped at the same contract

build: stop embedding source text in published source maps (`sourcesContent: false` across the tsup builds) and repair the cli package's dead `sources` references (build half of #15905 question 1)

ci: a per-package suite-duration ratchet — a PR that makes a suite exceed its measured ceiling is red; ceilings rise only by ruling (maintainer-directed, growth constraint)

Uh oh!

Search results