Issues

spec: `fileAccessDelegate`'s `.describe()` and `FileRefusedValueSchema`'s TSDoc still describe the download door only — after #22637 the delegate also decides a refused reader's file metadata

objectstack-ai/objectstack#22698 · opened

on Oct 10, 2026

1

install-local: a cloud install whose hot-register fails answers 200 with `hotLoaded: true` (the lenient path), so a console says the app "should now appear" over a kernel that does not have it

objectstack-ai/objectstack#22695 · opened

on Oct 10, 2026

1

[finding] import: a sandboxed hook's refusal reaches an import row as the debug wrapper (hook NAME threw: Error: SENTENCE), the last REST face of #22588's family and the home of its REST write-route enumeration pin

objectstack-ai/objectstack#22694 · opened

on Oct 10, 2026

1

registry: an app registered through `registerItem` is served without the declared `_packageVersion` (the artifact loader path stamps it), so a console cannot tell an upgrade's old app from its new one

objectstack-ai/objectstack#22689 · opened

on Oct 10, 2026

1

lint: the `approval-approvers-may-resolve-empty` remedy tells authors the admin bulk import does not write `sys_user.manager_id`; it has since PR #18046

objectstack-ai/objectstack#22683 · opened

on Oct 10, 2026

2

spec: catalog references in authoring surfaces become names (approver position binding, decision-output positions, the position form's permissionSets widget), ADR-0131 D4, from #15204

objectstack-ai/objectstack#22682 · opened

on Oct 10, 2026

1

ADR (ruling A on #22590 item 3): one engine-internal semi-join leaf, "the ids of object X this caller may read"; ADR-0055 alternatives row (a) revisited for this one leaf

objectstack-ai/objectstack#22678 · opened

on Oct 10, 2026

lint(flow CEL roots): `record` is still in `ENGINE_BOUND_ROOTS`, so `objectstack validate` passes a `record.X` read in a flow with no record entrance, which faults at run time once #22642 lands; and two texts describe `record` as always bound

objectstack-ai/objectstack#22677 · opened

on Oct 10, 2026

3

[Ruling A on #22649] docs: the skills install command reads the catalog from the installed @objectstack/skills package; the GitHub path is documented as the next (unreleased main) channel only

objectstack-ai/objectstack#22668 · opened

on Oct 10, 2026

skills+docs: governed texts still describe the committed spec-changes.json, its os-regen route and its regeneration lap, which #22485 (PR #22638) retired

objectstack-ai/objectstack#22667 · opened

on Oct 10, 2026

2

security(data, analytics): a lookup target's exposure declaration is not judged when the data door's `$expand`, or the dataset door's dimension-label pass, reads it — detail withheld pending maintainer

objectstack-ai/objectstack#22661 · opened

on Oct 10, 2026

1

[Ruling A on #22649] create-objectstack installs the skills catalog from the installed @objectstack/skills package, not from GitHub main; the scaffolded project depends on it at the spec's version

objectstack-ai/objectstack#22659 · opened

on Oct 10, 2026

[Ruling A on #22649] @objectstack/skills: the published skills catalog ships as a versioned package in the fixed group — the build copies skills/** in and files lists only it; the compatibility line and metadata.version derive from the package version

objectstack-ai/objectstack#22658 · opened

on Oct 10, 2026

4

finding(spec): the shipped JSDoc above `submitBehavior.url` in `view.zod.ts` says the Console's `FormPage` redirects verbatim via `window.location.assign`; at the pinned Console it substitutes, escapes and navigates in-app

objectstack-ai/objectstack#22655 · opened

on Oct 10, 2026

2

[PM seat] domain:cli · seat 2 — 🟢 marchtian · session_01HGa2XMKBRUqPrZFxQavBwH

objectstack-ai/objectstack#22648 · opened

on Oct 10, 2026

1

security(data): the data door's filter and group-by positions do not honour a field's `internal: true` the way its row read does — detail withheld pending maintainer

objectstack-ai/objectstack#22646 · opened

on Oct 10, 2026

2

metadata-protocol: the cross-object search (`searchAll`) skips an object on `searchable` / `apiEnabled` only and never consults the `apiMethods` whitelist, so a whitelist that omits `list` (and so `search`) does not keep an object out of the sweep

objectstack-ai/objectstack#22640 · opened

on Oct 10, 2026

2

rest(/meta read gate): enforce a list view's and a dashboard's `requiredPermissions` on the list read and the by-name read, so each audience is served only its own views and boards (the rest half of #22611)

objectstack-ai/objectstack#22639 · opened

on Oct 10, 2026

3

lint(runtime gate): a flow write's per-write snapshot carries no actions and no other flows, so a flow CEL root rule cannot see the entrances that hand a flow its record (W, from #22565)

objectstack-ai/objectstack#22636 · opened

on Oct 10, 2026

4

cli test: `dev-no-watch.pin.test.ts`'s control folds every failure (a signal, a pnpm failure, a spawn error) into exit code 1 and prints nothing, so a red in the merge queue cannot be diagnosed (ejected PR #22596)

objectstack-ai/objectstack#22618 · opened

on Oct 10, 2026

1

[finding] metadata(residual): a residual top-level object is listed by the metadata door under manifest.id while the data door answers 404, and the boot's warning says every door reports it

objectstack-ai/objectstack#22615 · opened

on Oct 10, 2026

3

verify: `hooks.run(object, 'delete', …)` is typed to resolve with a row (`Promise<EngineRow>`), but the engine answers `true`

objectstack-ai/objectstack#22599 · opened

on Oct 10, 2026

1

runtime (17.7.0): file fields read "no file" for a record reader without sys_file read, flow run summaries report acted 0 while notifying, and the activity read pre-scan caps at 2000 rows fail-closed

objectstack-ai/objectstack#22590 · opened

on Oct 10, 2026

15

release(changesets): four merged pending changesets state behaviour that later PRs on the same v18 train changed; correct them in place through check-empty-changeset's DELIBERATE CORRECTION path before the release

objectstack-ai/objectstack#22586 · opened

on Oct 10, 2026

4

skills(objectstack-automation): SKILL.md still teaches `{$User.<path>}` as a kept value-slot spelling and the text-slot run-user remedy through it, which #19939 pass 2 (PR #22563) refuses

objectstack-ai/objectstack#22585 · opened

on Oct 10, 2026

3

Navigation Menu

Repository navigation

Issues

spec: `fileAccessDelegate`'s `.describe()` and `FileRefusedValueSchema`'s TSDoc still describe the download door only — after #22637 the delegate also decides a refused reader's file metadata

install-local: a cloud install whose hot-register fails answers 200 with `hotLoaded: true` (the lenient path), so a console says the app "should now appear" over a kernel that does not have it

[finding] import: a sandboxed hook's refusal reaches an import row as the debug wrapper (hook NAME threw: Error: SENTENCE), the last REST face of #22588's family and the home of its REST write-route enumeration pin

registry: an app registered through `registerItem` is served without the declared `_packageVersion` (the artifact loader path stamps it), so a console cannot tell an upgrade's old app from its new one

lint: the `approval-approvers-may-resolve-empty` remedy tells authors the admin bulk import does not write `sys_user.manager_id`; it has since PR #18046

spec: catalog references in authoring surfaces become names (approver position binding, decision-output positions, the position form's permissionSets widget), ADR-0131 D4, from #15204

ADR (ruling A on #22590 item 3): one engine-internal semi-join leaf, "the ids of object X this caller may read"; ADR-0055 alternatives row (a) revisited for this one leaf

lint(flow CEL roots): `record` is still in `ENGINE_BOUND_ROOTS`, so `objectstack validate` passes a `record.X` read in a flow with no record entrance, which faults at run time once #22642 lands; and two texts describe `record` as always bound

[Ruling A on #22649] docs: the skills install command reads the catalog from the installed @objectstack/skills package; the GitHub path is documented as the next (unreleased main) channel only

skills+docs: governed texts still describe the committed spec-changes.json, its os-regen route and its regeneration lap, which #22485 (PR #22638) retired

security(data, analytics): a lookup target's exposure declaration is not judged when the data door's `$expand`, or the dataset door's dimension-label pass, reads it — detail withheld pending maintainer

[Ruling A on #22649] create-objectstack installs the skills catalog from the installed @objectstack/skills package, not from GitHub main; the scaffolded project depends on it at the spec's version

[Ruling A on #22649] @objectstack/skills: the published skills catalog ships as a versioned package in the fixed group — the build copies skills/** in and files lists only it; the compatibility line and metadata.version derive from the package version

finding(spec): the shipped JSDoc above `submitBehavior.url` in `view.zod.ts` says the Console's `FormPage` redirects verbatim via `window.location.assign`; at the pinned Console it substitutes, escapes and navigates in-app

[PM seat] domain:cli · seat 2 — 🟢 marchtian · session_01HGa2XMKBRUqPrZFxQavBwH

security(data): the data door's filter and group-by positions do not honour a field's `internal: true` the way its row read does — detail withheld pending maintainer

metadata-protocol: the cross-object search (`searchAll`) skips an object on `searchable` / `apiEnabled` only and never consults the `apiMethods` whitelist, so a whitelist that omits `list` (and so `search`) does not keep an object out of the sweep

rest(/meta read gate): enforce a list view's and a dashboard's `requiredPermissions` on the list read and the by-name read, so each audience is served only its own views and boards (the rest half of #22611)

lint(runtime gate): a flow write's per-write snapshot carries no actions and no other flows, so a flow CEL root rule cannot see the entrances that hand a flow its record (W, from #22565)

cli test: `dev-no-watch.pin.test.ts`'s control folds every failure (a signal, a pnpm failure, a spawn error) into exit code 1 and prints nothing, so a red in the merge queue cannot be diagnosed (ejected PR #22596)

[finding] metadata(residual): a residual top-level object is listed by the metadata door under manifest.id while the data door answers 404, and the boot's warning says every door reports it

verify: `hooks.run(object, 'delete', …)` is typed to resolve with a row (`Promise<EngineRow>`), but the engine answers `true`

runtime (17.7.0): file fields read "no file" for a record reader without sys_file read, flow run summaries report acted 0 while notifying, and the activity read pre-scan caps at 2000 rows fail-closed

release(changesets): four merged pending changesets state behaviour that later PRs on the same v18 train changed; correct them in place through check-empty-changeset's DELIBERATE CORRECTION path before the release

skills(objectstack-automation): SKILL.md still teaches `{$User.<path>}` as a kept value-slot spelling and the text-slot run-user remedy through it, which #19939 pass 2 (PR #22563) refuses