Skip to content

[finding] packages/spec cloud docblock lists sys_metadata as a control-plane table "(with environment_id)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts #13664

Closed
Bug
#13749
Closed
[finding] packages/spec cloud docblock lists sys_metadata as a control-plane table "(with environment_id)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts#13664
Bug
#13749
Assignees
os-warren
Labels
domain:specpriority:p2Medium: important, M3

Description

@claude
claude
bot
opened on Aug 31, 2026

Surfaced while correcting the stale environment_id JSDoc sites for #13434. Filed unassigned — recording only, not claimed, and deliberately NOT fixed in that PR: the fix lands in packages/spec, a different package from that card's three files, and the correct wording depends on a fact this tree cannot settle (see "What is NOT claimed").

The reading

packages/spec/src/cloud/environment.zod.ts:26-31 — the module docblock — lists sys_metadata among the Control-Plane tables "(with environment_id)", on origin/main at eaba72e48c:

 * Split of concerns:
* - **Control Plane**: `sys_environment` (includes physical DB addressing),
* `sys_package_installation` (with `environment_id`), `sys_environment_credential`,
* `sys_environment_member`, `sys_metadata` (with `environment_id`).
* - **Data Plane**: each environment DB contains only business objects
* (account, task, …). No system tables, no `environment_id` columns.

It reaches two audiences beyond the source file:

  • The published docs site, verbatim: content/docs/references/cloud/environment.mdx:26-31. That page carries AUTO-GENERATED — DO NOT EDIT at line 6, so the docblock above is its only editable source.
  • The published .d.ts: packages/spec/dist/cloud/index.d.ts:1688 (and the .d.mts twin), so it is also an editor tooltip for consumers of @objectstack/spec/cloud.

What contradicts it

On the metadata tables, environment_id is retired, not live:

  • AGENTS.md:8 — "DB column environment_id [control-plane tables; on the metadata tables since deprecated in favour of organization_id, ADR-0006 v4]".
  • packages/metadata-core/src/objects/sys-metadata.object.ts:138-148 — @deprecated … "no longer written by saveMetaItem and not consulted by overlay reads. Kept for legacy rows; new writes leave it NULL."
  • packages/metadata/src/loaders/database-loader.ts:82-89 — @deprecated … "accepted for back-compat but ignored — writes do not set environment_id and filters do not constrain on it."
  • packages/metadata/src/loaders/database-loader.test.ts pins it: the create call carries organization_id and notenvironment_id, and no findOne where-clause has the property.
  • Card [finding] four JSDoc sites still say saveMetaItem stamps the environment_id column and loadMetaFromDb filters on it — the code carries zero non-comment occurrences #13434 itself: the JSDoc sites that taught the same retired stamp/filter, now corrected.

So the parenthetical reads as a live tenancy column to anyone deciding whether to write it — the same defect class as #13434 and #13433, one surface further out (published docs plus published types, rather than an in-repo docstring).

What is NOT claimed

  • Not claimed that the whole line is wrong. The sys_package_installation parenthetical on the previous line is correct — that IS a control-plane table keyed by environment_id (ADR-0003, UNIQUE (environment_id, package_id)), and ADR-0002 lists it the same way.
  • Not claimed which way the correction goes, and this is why it was not repaired inline. Whether the CLOUD control plane's own sys_metadata still carries a live environment_id is a fact about the cloud deployment's schema, not about this tree. Two readings, needing different wording:
    1. The column is retired everywhere, so drop the parenthetical or restate it as deprecated / legacy-rows-only.
    2. The cloud control-plane copy of sys_metadata genuinely still keys by it while the per-environment metadata tables do not, in which case the line needs to SAY that — as written a reader cannot tell the two apart.
  • Not claimed that the generated page should be edited. It is auto-generated; the docblock is the source.

Re-check

git grep -n 'sys_metadata` (with `environment_id`)' -- packages content
sed -n '26,31p' packages/spec/src/cloud/environment.zod.ts
sed -n '1,10p' content/docs/references/cloud/environment.mdx
git grep -n 'environment_id' -- packages/metadata-core/src/objects/sys-metadata.object.ts packages/metadata/src/loaders/database-loader.ts

Duplicate check

Full enumeration of all 366 open non-PR issues via the REST list endpoint (4 pages, page 5 empty — complete, not truncated), grepped locally. Positive control in the same pass: 33 open cards contain "AGENTS.md", so the instrument is not returning a false zero. Five open cards mention environment_id: #13434 (the JSDoc sites this fell out of), #13433 (sys_activity's live-looking twin), and #12412 / #12036 / #3739 (control-plane casing and dead request fields — a different subject). Nearest neighbour on the same FILE is #12485, which reports environment.mdx:20's "sys_environment was renamed to sys_environment" tautology — the same generated page and plausibly the same generator-source repair, but a different sentence and a different defect. No open card covers this parenthetical.

Generated by Claude Code

Metadata

Metadata

Assignees

Labels

domain:specpriority:p2Medium: important, M3

Type

Bug

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    , 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
     blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
[finding] `packages/spec` cloud docblock lists `sys_metadata` as a control-plane table "(with `environment_id`)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts · Issue #13664 · objectstack-ai/objectstack · GitHub
    Skip to content
    [finding] packages/spec cloud docblock lists sys_metadata as a control-plane table "(with environment_id)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts #13664
    Closed
    Bug
    #13749
    Closed
    [finding] packages/spec cloud docblock lists sys_metadata as a control-plane table "(with environment_id)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts#13664
    Bug
    #13749
    Assignees
    os-warren
    Labels
    domain:specpriority:p2Medium: important, M3
    Description
    @claude
    claude
    bot
    opened on Aug 31, 2026
    Surfaced while correcting the stale environment_id JSDoc sites for #13434. Filed unassigned — recording only, not claimed, and deliberately NOT fixed in that PR: the fix lands in packages/spec, a different package from that card's three files, and the correct wording depends on a fact this tree cannot settle (see "What is NOT claimed").
    The reading
    packages/spec/src/cloud/environment.zod.ts:26-31 — the module docblock — lists sys_metadata among the Control-Plane tables "(with environment_id)", on origin/main at eaba72e48c:
     * Split of concerns:
* - **Control Plane**: `sys_environment` (includes physical DB addressing),
* `sys_package_installation` (with `environment_id`), `sys_environment_credential`,
* `sys_environment_member`, `sys_metadata` (with `environment_id`).
* - **Data Plane**: each environment DB contains only business objects
* (account, task, …). No system tables, no `environment_id` columns.

    It reaches two audiences beyond the source file:
    • The published docs site, verbatim: content/docs/references/cloud/environment.mdx:26-31. That page carries AUTO-GENERATED — DO NOT EDIT at line 6, so the docblock above is its only editable source.
    • The published .d.ts: packages/spec/dist/cloud/index.d.ts:1688 (and the .d.mts twin), so it is also an editor tooltip for consumers of @objectstack/spec/cloud.
    What contradicts it
    On the metadata tables, environment_id is retired, not live:
    • AGENTS.md:8 — "DB column environment_id [control-plane tables; on the metadata tables since deprecated in favour of organization_id, ADR-0006 v4]".
    • packages/metadata-core/src/objects/sys-metadata.object.ts:138-148 — @deprecated … "no longer written by saveMetaItem and not consulted by overlay reads. Kept for legacy rows; new writes leave it NULL."
    • packages/metadata/src/loaders/database-loader.ts:82-89 — @deprecated … "accepted for back-compat but ignored — writes do not set environment_id and filters do not constrain on it."
    • packages/metadata/src/loaders/database-loader.test.ts pins it: the create call carries organization_id and notenvironment_id, and no findOne where-clause has the property.
    • Card [finding] four JSDoc sites still say saveMetaItem stamps the environment_id column and loadMetaFromDb filters on it — the code carries zero non-comment occurrences #13434 itself: the JSDoc sites that taught the same retired stamp/filter, now corrected.
    So the parenthetical reads as a live tenancy column to anyone deciding whether to write it — the same defect class as #13434 and #13433, one surface further out (published docs plus published types, rather than an in-repo docstring).
    What is NOT claimed
    • Not claimed that the whole line is wrong. The sys_package_installation parenthetical on the previous line is correct — that IS a control-plane table keyed by environment_id (ADR-0003, UNIQUE (environment_id, package_id)), and ADR-0002 lists it the same way.
    • Not claimed which way the correction goes, and this is why it was not repaired inline. Whether the CLOUD control plane's own sys_metadata still carries a live environment_id is a fact about the cloud deployment's schema, not about this tree. Two readings, needing different wording:

      1. The column is retired everywhere, so drop the parenthetical or restate it as deprecated / legacy-rows-only.
      2. The cloud control-plane copy of sys_metadata genuinely still keys by it while the per-environment metadata tables do not, in which case the line needs to SAY that — as written a reader cannot tell the two apart.
    • Not claimed that the generated page should be edited. It is auto-generated; the docblock is the source.
    Re-check
    git grep -n 'sys_metadata` (with `environment_id`)' -- packages content
sed -n '26,31p' packages/spec/src/cloud/environment.zod.ts
sed -n '1,10p' content/docs/references/cloud/environment.mdx
git grep -n 'environment_id' -- packages/metadata-core/src/objects/sys-metadata.object.ts packages/metadata/src/loaders/database-loader.ts

    Duplicate check
    Full enumeration of all 366 open non-PR issues via the REST list endpoint (4 pages, page 5 empty — complete, not truncated), grepped locally. Positive control in the same pass: 33 open cards contain "AGENTS.md", so the instrument is not returning a false zero. Five open cards mention environment_id: #13434 (the JSDoc sites this fell out of), #13433 (sys_activity's live-looking twin), and #12412 / #12036 / #3739 (control-plane casing and dead request fields — a different subject). Nearest neighbour on the same FILE is #12485, which reports environment.mdx:20's "sys_environment was renamed to sys_environment" tautology — the same generated page and plausibly the same generator-source repair, but a different sentence and a different defect. No open card covers this parenthetical.
    Generated by Claude Code
    Metadata
    Metadata
    Assignees
    Labels
    domain:specpriority:p2Medium: important, M3
    Type
    Bug
    Projects
    No projects
      Milestone
      No milestone
      Relationships
      None yet
      Development
      No branches or pull requests
      Issue actions
      
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
[finding] `packages/spec` cloud docblock lists `sys_metadata` as a control-plane table "(with `environment_id`)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts · Issue #13664 · objectstack-ai/objectstack · GitHub
      Skip to content
      [finding] packages/spec cloud docblock lists sys_metadata as a control-plane table "(with environment_id)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts #13664
      Closed
      Bug
      #13749
      Closed
      [finding] packages/spec cloud docblock lists sys_metadata as a control-plane table "(with environment_id)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts#13664
      Bug
      #13749
      Assignees
      os-warren
      Labels
      domain:specpriority:p2Medium: important, M3
      Description
      @claude
      claude
      bot
      opened on Aug 31, 2026
      Surfaced while correcting the stale environment_id JSDoc sites for #13434. Filed unassigned — recording only, not claimed, and deliberately NOT fixed in that PR: the fix lands in packages/spec, a different package from that card's three files, and the correct wording depends on a fact this tree cannot settle (see "What is NOT claimed").
      The reading
      packages/spec/src/cloud/environment.zod.ts:26-31 — the module docblock — lists sys_metadata among the Control-Plane tables "(with environment_id)", on origin/main at eaba72e48c:
       * Split of concerns:
* - **Control Plane**: `sys_environment` (includes physical DB addressing),
* `sys_package_installation` (with `environment_id`), `sys_environment_credential`,
* `sys_environment_member`, `sys_metadata` (with `environment_id`).
* - **Data Plane**: each environment DB contains only business objects
* (account, task, …). No system tables, no `environment_id` columns.

      It reaches two audiences beyond the source file:
      • The published docs site, verbatim: content/docs/references/cloud/environment.mdx:26-31. That page carries AUTO-GENERATED — DO NOT EDIT at line 6, so the docblock above is its only editable source.
      • The published .d.ts: packages/spec/dist/cloud/index.d.ts:1688 (and the .d.mts twin), so it is also an editor tooltip for consumers of @objectstack/spec/cloud.
      What contradicts it
      On the metadata tables, environment_id is retired, not live:
      • AGENTS.md:8 — "DB column environment_id [control-plane tables; on the metadata tables since deprecated in favour of organization_id, ADR-0006 v4]".
      • packages/metadata-core/src/objects/sys-metadata.object.ts:138-148 — @deprecated … "no longer written by saveMetaItem and not consulted by overlay reads. Kept for legacy rows; new writes leave it NULL."
      • packages/metadata/src/loaders/database-loader.ts:82-89 — @deprecated … "accepted for back-compat but ignored — writes do not set environment_id and filters do not constrain on it."
      • packages/metadata/src/loaders/database-loader.test.ts pins it: the create call carries organization_id and notenvironment_id, and no findOne where-clause has the property.
      • Card [finding] four JSDoc sites still say saveMetaItem stamps the environment_id column and loadMetaFromDb filters on it — the code carries zero non-comment occurrences #13434 itself: the JSDoc sites that taught the same retired stamp/filter, now corrected.
      So the parenthetical reads as a live tenancy column to anyone deciding whether to write it — the same defect class as #13434 and #13433, one surface further out (published docs plus published types, rather than an in-repo docstring).
      What is NOT claimed
      • Not claimed that the whole line is wrong. The sys_package_installation parenthetical on the previous line is correct — that IS a control-plane table keyed by environment_id (ADR-0003, UNIQUE (environment_id, package_id)), and ADR-0002 lists it the same way.
      • Not claimed which way the correction goes, and this is why it was not repaired inline. Whether the CLOUD control plane's own sys_metadata still carries a live environment_id is a fact about the cloud deployment's schema, not about this tree. Two readings, needing different wording:

        1. The column is retired everywhere, so drop the parenthetical or restate it as deprecated / legacy-rows-only.
        2. The cloud control-plane copy of sys_metadata genuinely still keys by it while the per-environment metadata tables do not, in which case the line needs to SAY that — as written a reader cannot tell the two apart.
      • Not claimed that the generated page should be edited. It is auto-generated; the docblock is the source.
      Re-check
      git grep -n 'sys_metadata` (with `environment_id`)' -- packages content
sed -n '26,31p' packages/spec/src/cloud/environment.zod.ts
sed -n '1,10p' content/docs/references/cloud/environment.mdx
git grep -n 'environment_id' -- packages/metadata-core/src/objects/sys-metadata.object.ts packages/metadata/src/loaders/database-loader.ts

      Duplicate check
      Full enumeration of all 366 open non-PR issues via the REST list endpoint (4 pages, page 5 empty — complete, not truncated), grepped locally. Positive control in the same pass: 33 open cards contain "AGENTS.md", so the instrument is not returning a false zero. Five open cards mention environment_id: #13434 (the JSDoc sites this fell out of), #13433 (sys_activity's live-looking twin), and #12412 / #12036 / #3739 (control-plane casing and dead request fields — a different subject). Nearest neighbour on the same FILE is #12485, which reports environment.mdx:20's "sys_environment was renamed to sys_environment" tautology — the same generated page and plausibly the same generator-source repair, but a different sentence and a different defect. No open card covers this parenthetical.
      Generated by Claude Code
      Metadata
      Metadata
      Assignees
      Labels
      domain:specpriority:p2Medium: important, M3
      Type
      Bug
      Projects
      No projects
        Milestone
        No milestone
        Relationships
        None yet
        Development
        No branches or pull requests
        Issue actions
        
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
[finding] `packages/spec` cloud docblock lists `sys_metadata` as a control-plane table "(with `environment_id`)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts · Issue #13664 · objectstack-ai/objectstack · GitHub
        Skip to content
        [finding] packages/spec cloud docblock lists sys_metadata as a control-plane table "(with environment_id)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts #13664
        Closed
        Bug
        #13749
        Closed
        [finding] packages/spec cloud docblock lists sys_metadata as a control-plane table "(with environment_id)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts#13664
        Bug
        #13749
        Assignees
        os-warren
        Labels
        domain:specpriority:p2Medium: important, M3
        Description
        @claude
        claude
        bot
        opened on Aug 31, 2026
        Surfaced while correcting the stale environment_id JSDoc sites for #13434. Filed unassigned — recording only, not claimed, and deliberately NOT fixed in that PR: the fix lands in packages/spec, a different package from that card's three files, and the correct wording depends on a fact this tree cannot settle (see "What is NOT claimed").
        The reading
        packages/spec/src/cloud/environment.zod.ts:26-31 — the module docblock — lists sys_metadata among the Control-Plane tables "(with environment_id)", on origin/main at eaba72e48c:
         * Split of concerns:
* - **Control Plane**: `sys_environment` (includes physical DB addressing),
* `sys_package_installation` (with `environment_id`), `sys_environment_credential`,
* `sys_environment_member`, `sys_metadata` (with `environment_id`).
* - **Data Plane**: each environment DB contains only business objects
* (account, task, …). No system tables, no `environment_id` columns.

        It reaches two audiences beyond the source file:
        • The published docs site, verbatim: content/docs/references/cloud/environment.mdx:26-31. That page carries AUTO-GENERATED — DO NOT EDIT at line 6, so the docblock above is its only editable source.
        • The published .d.ts: packages/spec/dist/cloud/index.d.ts:1688 (and the .d.mts twin), so it is also an editor tooltip for consumers of @objectstack/spec/cloud.
        What contradicts it
        On the metadata tables, environment_id is retired, not live:
        • AGENTS.md:8 — "DB column environment_id [control-plane tables; on the metadata tables since deprecated in favour of organization_id, ADR-0006 v4]".
        • packages/metadata-core/src/objects/sys-metadata.object.ts:138-148 — @deprecated … "no longer written by saveMetaItem and not consulted by overlay reads. Kept for legacy rows; new writes leave it NULL."
        • packages/metadata/src/loaders/database-loader.ts:82-89 — @deprecated … "accepted for back-compat but ignored — writes do not set environment_id and filters do not constrain on it."
        • packages/metadata/src/loaders/database-loader.test.ts pins it: the create call carries organization_id and notenvironment_id, and no findOne where-clause has the property.
        • Card [finding] four JSDoc sites still say saveMetaItem stamps the environment_id column and loadMetaFromDb filters on it — the code carries zero non-comment occurrences #13434 itself: the JSDoc sites that taught the same retired stamp/filter, now corrected.
        So the parenthetical reads as a live tenancy column to anyone deciding whether to write it — the same defect class as #13434 and #13433, one surface further out (published docs plus published types, rather than an in-repo docstring).
        What is NOT claimed
        • Not claimed that the whole line is wrong. The sys_package_installation parenthetical on the previous line is correct — that IS a control-plane table keyed by environment_id (ADR-0003, UNIQUE (environment_id, package_id)), and ADR-0002 lists it the same way.
        • Not claimed which way the correction goes, and this is why it was not repaired inline. Whether the CLOUD control plane's own sys_metadata still carries a live environment_id is a fact about the cloud deployment's schema, not about this tree. Two readings, needing different wording:

          1. The column is retired everywhere, so drop the parenthetical or restate it as deprecated / legacy-rows-only.
          2. The cloud control-plane copy of sys_metadata genuinely still keys by it while the per-environment metadata tables do not, in which case the line needs to SAY that — as written a reader cannot tell the two apart.
        • Not claimed that the generated page should be edited. It is auto-generated; the docblock is the source.
        Re-check
        git grep -n 'sys_metadata` (with `environment_id`)' -- packages content
sed -n '26,31p' packages/spec/src/cloud/environment.zod.ts
sed -n '1,10p' content/docs/references/cloud/environment.mdx
git grep -n 'environment_id' -- packages/metadata-core/src/objects/sys-metadata.object.ts packages/metadata/src/loaders/database-loader.ts

        Duplicate check
        Full enumeration of all 366 open non-PR issues via the REST list endpoint (4 pages, page 5 empty — complete, not truncated), grepped locally. Positive control in the same pass: 33 open cards contain "AGENTS.md", so the instrument is not returning a false zero. Five open cards mention environment_id: #13434 (the JSDoc sites this fell out of), #13433 (sys_activity's live-looking twin), and #12412 / #12036 / #3739 (control-plane casing and dead request fields — a different subject). Nearest neighbour on the same FILE is #12485, which reports environment.mdx:20's "sys_environment was renamed to sys_environment" tautology — the same generated page and plausibly the same generator-source repair, but a different sentence and a different defect. No open card covers this parenthetical.
        Generated by Claude Code
        Metadata
        Metadata
        Assignees
        Labels
        domain:specpriority:p2Medium: important, M3
        Type
        Bug
        Projects
        No projects
          Milestone
          No milestone
          Relationships
          None yet
          Development
          No branches or pull requests
          Issue actions
          
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
[finding] `packages/spec` cloud docblock lists `sys_metadata` as a control-plane table "(with `environment_id`)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts · Issue #13664 · objectstack-ai/objectstack · GitHub
          Skip to content
          [finding] packages/spec cloud docblock lists sys_metadata as a control-plane table "(with environment_id)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts #13664
          Closed
          Bug
          #13749
          Closed
          [finding] packages/spec cloud docblock lists sys_metadata as a control-plane table "(with environment_id)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts#13664
          Bug
          #13749
          Assignees
          os-warren
          Labels
          domain:specpriority:p2Medium: important, M3
          Description
          @claude
          claude
          bot
          opened on Aug 31, 2026
          Surfaced while correcting the stale environment_id JSDoc sites for #13434. Filed unassigned — recording only, not claimed, and deliberately NOT fixed in that PR: the fix lands in packages/spec, a different package from that card's three files, and the correct wording depends on a fact this tree cannot settle (see "What is NOT claimed").
          The reading
          packages/spec/src/cloud/environment.zod.ts:26-31 — the module docblock — lists sys_metadata among the Control-Plane tables "(with environment_id)", on origin/main at eaba72e48c:
           * Split of concerns:
* - **Control Plane**: `sys_environment` (includes physical DB addressing),
* `sys_package_installation` (with `environment_id`), `sys_environment_credential`,
* `sys_environment_member`, `sys_metadata` (with `environment_id`).
* - **Data Plane**: each environment DB contains only business objects
* (account, task, …). No system tables, no `environment_id` columns.

          It reaches two audiences beyond the source file:
          • The published docs site, verbatim: content/docs/references/cloud/environment.mdx:26-31. That page carries AUTO-GENERATED — DO NOT EDIT at line 6, so the docblock above is its only editable source.
          • The published .d.ts: packages/spec/dist/cloud/index.d.ts:1688 (and the .d.mts twin), so it is also an editor tooltip for consumers of @objectstack/spec/cloud.
          What contradicts it
          On the metadata tables, environment_id is retired, not live:
          • AGENTS.md:8 — "DB column environment_id [control-plane tables; on the metadata tables since deprecated in favour of organization_id, ADR-0006 v4]".
          • packages/metadata-core/src/objects/sys-metadata.object.ts:138-148 — @deprecated … "no longer written by saveMetaItem and not consulted by overlay reads. Kept for legacy rows; new writes leave it NULL."
          • packages/metadata/src/loaders/database-loader.ts:82-89 — @deprecated … "accepted for back-compat but ignored — writes do not set environment_id and filters do not constrain on it."
          • packages/metadata/src/loaders/database-loader.test.ts pins it: the create call carries organization_id and notenvironment_id, and no findOne where-clause has the property.
          • Card [finding] four JSDoc sites still say saveMetaItem stamps the environment_id column and loadMetaFromDb filters on it — the code carries zero non-comment occurrences #13434 itself: the JSDoc sites that taught the same retired stamp/filter, now corrected.
          So the parenthetical reads as a live tenancy column to anyone deciding whether to write it — the same defect class as #13434 and #13433, one surface further out (published docs plus published types, rather than an in-repo docstring).
          What is NOT claimed
          • Not claimed that the whole line is wrong. The sys_package_installation parenthetical on the previous line is correct — that IS a control-plane table keyed by environment_id (ADR-0003, UNIQUE (environment_id, package_id)), and ADR-0002 lists it the same way.
          • Not claimed which way the correction goes, and this is why it was not repaired inline. Whether the CLOUD control plane's own sys_metadata still carries a live environment_id is a fact about the cloud deployment's schema, not about this tree. Two readings, needing different wording:

            1. The column is retired everywhere, so drop the parenthetical or restate it as deprecated / legacy-rows-only.
            2. The cloud control-plane copy of sys_metadata genuinely still keys by it while the per-environment metadata tables do not, in which case the line needs to SAY that — as written a reader cannot tell the two apart.
          • Not claimed that the generated page should be edited. It is auto-generated; the docblock is the source.
          Re-check
          git grep -n 'sys_metadata` (with `environment_id`)' -- packages content
sed -n '26,31p' packages/spec/src/cloud/environment.zod.ts
sed -n '1,10p' content/docs/references/cloud/environment.mdx
git grep -n 'environment_id' -- packages/metadata-core/src/objects/sys-metadata.object.ts packages/metadata/src/loaders/database-loader.ts

          Duplicate check
          Full enumeration of all 366 open non-PR issues via the REST list endpoint (4 pages, page 5 empty — complete, not truncated), grepped locally. Positive control in the same pass: 33 open cards contain "AGENTS.md", so the instrument is not returning a false zero. Five open cards mention environment_id: #13434 (the JSDoc sites this fell out of), #13433 (sys_activity's live-looking twin), and #12412 / #12036 / #3739 (control-plane casing and dead request fields — a different subject). Nearest neighbour on the same FILE is #12485, which reports environment.mdx:20's "sys_environment was renamed to sys_environment" tautology — the same generated page and plausibly the same generator-source repair, but a different sentence and a different defect. No open card covers this parenthetical.
          Generated by Claude Code
          Metadata
          Metadata
          Assignees
          Labels
          domain:specpriority:p2Medium: important, M3
          Type
          Bug
          Projects
          No projects
            Milestone
            No milestone
            Relationships
            None yet
            Development
            No branches or pull requests
            Issue actions
            
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
[finding] `packages/spec` cloud docblock lists `sys_metadata` as a control-plane table "(with `environment_id`)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts · Issue #13664 · objectstack-ai/objectstack · GitHub
            Skip to content
            [finding] packages/spec cloud docblock lists sys_metadata as a control-plane table "(with environment_id)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts #13664
            Closed
            Bug
            #13749
            Closed
            [finding] packages/spec cloud docblock lists sys_metadata as a control-plane table "(with environment_id)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts#13664
            Bug
            #13749
            Assignees
            os-warren
            Labels
            domain:specpriority:p2Medium: important, M3
            Description
            @claude
            claude
            bot
            opened on Aug 31, 2026
            Surfaced while correcting the stale environment_id JSDoc sites for #13434. Filed unassigned — recording only, not claimed, and deliberately NOT fixed in that PR: the fix lands in packages/spec, a different package from that card's three files, and the correct wording depends on a fact this tree cannot settle (see "What is NOT claimed").
            The reading
            packages/spec/src/cloud/environment.zod.ts:26-31 — the module docblock — lists sys_metadata among the Control-Plane tables "(with environment_id)", on origin/main at eaba72e48c:
             * Split of concerns:
* - **Control Plane**: `sys_environment` (includes physical DB addressing),
* `sys_package_installation` (with `environment_id`), `sys_environment_credential`,
* `sys_environment_member`, `sys_metadata` (with `environment_id`).
* - **Data Plane**: each environment DB contains only business objects
* (account, task, …). No system tables, no `environment_id` columns.

            It reaches two audiences beyond the source file:
            • The published docs site, verbatim: content/docs/references/cloud/environment.mdx:26-31. That page carries AUTO-GENERATED — DO NOT EDIT at line 6, so the docblock above is its only editable source.
            • The published .d.ts: packages/spec/dist/cloud/index.d.ts:1688 (and the .d.mts twin), so it is also an editor tooltip for consumers of @objectstack/spec/cloud.
            What contradicts it
            On the metadata tables, environment_id is retired, not live:
            • AGENTS.md:8 — "DB column environment_id [control-plane tables; on the metadata tables since deprecated in favour of organization_id, ADR-0006 v4]".
            • packages/metadata-core/src/objects/sys-metadata.object.ts:138-148 — @deprecated … "no longer written by saveMetaItem and not consulted by overlay reads. Kept for legacy rows; new writes leave it NULL."
            • packages/metadata/src/loaders/database-loader.ts:82-89 — @deprecated … "accepted for back-compat but ignored — writes do not set environment_id and filters do not constrain on it."
            • packages/metadata/src/loaders/database-loader.test.ts pins it: the create call carries organization_id and notenvironment_id, and no findOne where-clause has the property.
            • Card [finding] four JSDoc sites still say saveMetaItem stamps the environment_id column and loadMetaFromDb filters on it — the code carries zero non-comment occurrences #13434 itself: the JSDoc sites that taught the same retired stamp/filter, now corrected.
            So the parenthetical reads as a live tenancy column to anyone deciding whether to write it — the same defect class as #13434 and #13433, one surface further out (published docs plus published types, rather than an in-repo docstring).
            What is NOT claimed
            • Not claimed that the whole line is wrong. The sys_package_installation parenthetical on the previous line is correct — that IS a control-plane table keyed by environment_id (ADR-0003, UNIQUE (environment_id, package_id)), and ADR-0002 lists it the same way.
            • Not claimed which way the correction goes, and this is why it was not repaired inline. Whether the CLOUD control plane's own sys_metadata still carries a live environment_id is a fact about the cloud deployment's schema, not about this tree. Two readings, needing different wording:

              1. The column is retired everywhere, so drop the parenthetical or restate it as deprecated / legacy-rows-only.
              2. The cloud control-plane copy of sys_metadata genuinely still keys by it while the per-environment metadata tables do not, in which case the line needs to SAY that — as written a reader cannot tell the two apart.
            • Not claimed that the generated page should be edited. It is auto-generated; the docblock is the source.
            Re-check
            git grep -n 'sys_metadata` (with `environment_id`)' -- packages content
sed -n '26,31p' packages/spec/src/cloud/environment.zod.ts
sed -n '1,10p' content/docs/references/cloud/environment.mdx
git grep -n 'environment_id' -- packages/metadata-core/src/objects/sys-metadata.object.ts packages/metadata/src/loaders/database-loader.ts

            Duplicate check
            Full enumeration of all 366 open non-PR issues via the REST list endpoint (4 pages, page 5 empty — complete, not truncated), grepped locally. Positive control in the same pass: 33 open cards contain "AGENTS.md", so the instrument is not returning a false zero. Five open cards mention environment_id: #13434 (the JSDoc sites this fell out of), #13433 (sys_activity's live-looking twin), and #12412 / #12036 / #3739 (control-plane casing and dead request fields — a different subject). Nearest neighbour on the same FILE is #12485, which reports environment.mdx:20's "sys_environment was renamed to sys_environment" tautology — the same generated page and plausibly the same generator-source repair, but a different sentence and a different defect. No open card covers this parenthetical.
            Generated by Claude Code
            Metadata
            Metadata
            Assignees
            Labels
            domain:specpriority:p2Medium: important, M3
            Type
            Bug
            Projects
            No projects
              Milestone
              No milestone
              Relationships
              None yet
              Development
              No branches or pull requests
              Issue actions
              
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
[finding] `packages/spec` cloud docblock lists `sys_metadata` as a control-plane table "(with `environment_id`)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts · Issue #13664 · objectstack-ai/objectstack · GitHub
              Skip to content
              [finding] packages/spec cloud docblock lists sys_metadata as a control-plane table "(with environment_id)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts #13664
              Closed
              Bug
              #13749
              Closed
              [finding] packages/spec cloud docblock lists sys_metadata as a control-plane table "(with environment_id)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts#13664
              Bug
              #13749
              Assignees
              os-warren
              Labels
              domain:specpriority:p2Medium: important, M3
              Description
              @claude
              claude
              bot
              opened on Aug 31, 2026
              Surfaced while correcting the stale environment_id JSDoc sites for #13434. Filed unassigned — recording only, not claimed, and deliberately NOT fixed in that PR: the fix lands in packages/spec, a different package from that card's three files, and the correct wording depends on a fact this tree cannot settle (see "What is NOT claimed").
              The reading
              packages/spec/src/cloud/environment.zod.ts:26-31 — the module docblock — lists sys_metadata among the Control-Plane tables "(with environment_id)", on origin/main at eaba72e48c:
               * Split of concerns:
* - **Control Plane**: `sys_environment` (includes physical DB addressing),
* `sys_package_installation` (with `environment_id`), `sys_environment_credential`,
* `sys_environment_member`, `sys_metadata` (with `environment_id`).
* - **Data Plane**: each environment DB contains only business objects
* (account, task, …). No system tables, no `environment_id` columns.

              It reaches two audiences beyond the source file:
              • The published docs site, verbatim: content/docs/references/cloud/environment.mdx:26-31. That page carries AUTO-GENERATED — DO NOT EDIT at line 6, so the docblock above is its only editable source.
              • The published .d.ts: packages/spec/dist/cloud/index.d.ts:1688 (and the .d.mts twin), so it is also an editor tooltip for consumers of @objectstack/spec/cloud.
              What contradicts it
              On the metadata tables, environment_id is retired, not live:
              • AGENTS.md:8 — "DB column environment_id [control-plane tables; on the metadata tables since deprecated in favour of organization_id, ADR-0006 v4]".
              • packages/metadata-core/src/objects/sys-metadata.object.ts:138-148 — @deprecated … "no longer written by saveMetaItem and not consulted by overlay reads. Kept for legacy rows; new writes leave it NULL."
              • packages/metadata/src/loaders/database-loader.ts:82-89 — @deprecated … "accepted for back-compat but ignored — writes do not set environment_id and filters do not constrain on it."
              • packages/metadata/src/loaders/database-loader.test.ts pins it: the create call carries organization_id and notenvironment_id, and no findOne where-clause has the property.
              • Card [finding] four JSDoc sites still say saveMetaItem stamps the environment_id column and loadMetaFromDb filters on it — the code carries zero non-comment occurrences #13434 itself: the JSDoc sites that taught the same retired stamp/filter, now corrected.
              So the parenthetical reads as a live tenancy column to anyone deciding whether to write it — the same defect class as #13434 and #13433, one surface further out (published docs plus published types, rather than an in-repo docstring).
              What is NOT claimed
              • Not claimed that the whole line is wrong. The sys_package_installation parenthetical on the previous line is correct — that IS a control-plane table keyed by environment_id (ADR-0003, UNIQUE (environment_id, package_id)), and ADR-0002 lists it the same way.
              • Not claimed which way the correction goes, and this is why it was not repaired inline. Whether the CLOUD control plane's own sys_metadata still carries a live environment_id is a fact about the cloud deployment's schema, not about this tree. Two readings, needing different wording:

                1. The column is retired everywhere, so drop the parenthetical or restate it as deprecated / legacy-rows-only.
                2. The cloud control-plane copy of sys_metadata genuinely still keys by it while the per-environment metadata tables do not, in which case the line needs to SAY that — as written a reader cannot tell the two apart.
              • Not claimed that the generated page should be edited. It is auto-generated; the docblock is the source.
              Re-check
              git grep -n 'sys_metadata` (with `environment_id`)' -- packages content
sed -n '26,31p' packages/spec/src/cloud/environment.zod.ts
sed -n '1,10p' content/docs/references/cloud/environment.mdx
git grep -n 'environment_id' -- packages/metadata-core/src/objects/sys-metadata.object.ts packages/metadata/src/loaders/database-loader.ts

              Duplicate check
              Full enumeration of all 366 open non-PR issues via the REST list endpoint (4 pages, page 5 empty — complete, not truncated), grepped locally. Positive control in the same pass: 33 open cards contain "AGENTS.md", so the instrument is not returning a false zero. Five open cards mention environment_id: #13434 (the JSDoc sites this fell out of), #13433 (sys_activity's live-looking twin), and #12412 / #12036 / #3739 (control-plane casing and dead request fields — a different subject). Nearest neighbour on the same FILE is #12485, which reports environment.mdx:20's "sys_environment was renamed to sys_environment" tautology — the same generated page and plausibly the same generator-source repair, but a different sentence and a different defect. No open card covers this parenthetical.
              Generated by Claude Code
              Metadata
              Metadata
              Assignees
              Labels
              domain:specpriority:p2Medium: important, M3
              Type
              Bug
              Projects
              No projects
                Milestone
                No milestone
                Relationships
                None yet
                Development
                No branches or pull requests
                Issue actions
                
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();
[finding] `packages/spec` cloud docblock lists `sys_metadata` as a control-plane table "(with `environment_id`)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts · Issue #13664 · objectstack-ai/objectstack · GitHub
                Skip to content
                [finding] packages/spec cloud docblock lists sys_metadata as a control-plane table "(with environment_id)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts #13664
                Closed
                Bug
                #13749
                Closed
                [finding] packages/spec cloud docblock lists sys_metadata as a control-plane table "(with environment_id)" — the column is deprecated on the metadata tables, and the line ships to both the docs site and the published .d.ts#13664
                Bug
                #13749
                Assignees
                os-warren
                Labels
                domain:specpriority:p2Medium: important, M3
                Description
                @claude
                claude
                bot
                opened on Aug 31, 2026
                Surfaced while correcting the stale environment_id JSDoc sites for #13434. Filed unassigned — recording only, not claimed, and deliberately NOT fixed in that PR: the fix lands in packages/spec, a different package from that card's three files, and the correct wording depends on a fact this tree cannot settle (see "What is NOT claimed").
                The reading
                packages/spec/src/cloud/environment.zod.ts:26-31 — the module docblock — lists sys_metadata among the Control-Plane tables "(with environment_id)", on origin/main at eaba72e48c:
                 * Split of concerns:
* - **Control Plane**: `sys_environment` (includes physical DB addressing),
* `sys_package_installation` (with `environment_id`), `sys_environment_credential`,
* `sys_environment_member`, `sys_metadata` (with `environment_id`).
* - **Data Plane**: each environment DB contains only business objects
* (account, task, …). No system tables, no `environment_id` columns.

                It reaches two audiences beyond the source file:
                • The published docs site, verbatim: content/docs/references/cloud/environment.mdx:26-31. That page carries AUTO-GENERATED — DO NOT EDIT at line 6, so the docblock above is its only editable source.
                • The published .d.ts: packages/spec/dist/cloud/index.d.ts:1688 (and the .d.mts twin), so it is also an editor tooltip for consumers of @objectstack/spec/cloud.
                What contradicts it
                On the metadata tables, environment_id is retired, not live:
                • AGENTS.md:8 — "DB column environment_id [control-plane tables; on the metadata tables since deprecated in favour of organization_id, ADR-0006 v4]".
                • packages/metadata-core/src/objects/sys-metadata.object.ts:138-148 — @deprecated … "no longer written by saveMetaItem and not consulted by overlay reads. Kept for legacy rows; new writes leave it NULL."
                • packages/metadata/src/loaders/database-loader.ts:82-89 — @deprecated … "accepted for back-compat but ignored — writes do not set environment_id and filters do not constrain on it."
                • packages/metadata/src/loaders/database-loader.test.ts pins it: the create call carries organization_id and notenvironment_id, and no findOne where-clause has the property.
                • Card [finding] four JSDoc sites still say saveMetaItem stamps the environment_id column and loadMetaFromDb filters on it — the code carries zero non-comment occurrences #13434 itself: the JSDoc sites that taught the same retired stamp/filter, now corrected.
                So the parenthetical reads as a live tenancy column to anyone deciding whether to write it — the same defect class as #13434 and #13433, one surface further out (published docs plus published types, rather than an in-repo docstring).
                What is NOT claimed
                • Not claimed that the whole line is wrong. The sys_package_installation parenthetical on the previous line is correct — that IS a control-plane table keyed by environment_id (ADR-0003, UNIQUE (environment_id, package_id)), and ADR-0002 lists it the same way.
                • Not claimed which way the correction goes, and this is why it was not repaired inline. Whether the CLOUD control plane's own sys_metadata still carries a live environment_id is a fact about the cloud deployment's schema, not about this tree. Two readings, needing different wording:

                  1. The column is retired everywhere, so drop the parenthetical or restate it as deprecated / legacy-rows-only.
                  2. The cloud control-plane copy of sys_metadata genuinely still keys by it while the per-environment metadata tables do not, in which case the line needs to SAY that — as written a reader cannot tell the two apart.
                • Not claimed that the generated page should be edited. It is auto-generated; the docblock is the source.
                Re-check
                git grep -n 'sys_metadata` (with `environment_id`)' -- packages content
sed -n '26,31p' packages/spec/src/cloud/environment.zod.ts
sed -n '1,10p' content/docs/references/cloud/environment.mdx
git grep -n 'environment_id' -- packages/metadata-core/src/objects/sys-metadata.object.ts packages/metadata/src/loaders/database-loader.ts

                Duplicate check
                Full enumeration of all 366 open non-PR issues via the REST list endpoint (4 pages, page 5 empty — complete, not truncated), grepped locally. Positive control in the same pass: 33 open cards contain "AGENTS.md", so the instrument is not returning a false zero. Five open cards mention environment_id: #13434 (the JSDoc sites this fell out of), #13433 (sys_activity's live-looking twin), and #12412 / #12036 / #3739 (control-plane casing and dead request fields — a different subject). Nearest neighbour on the same FILE is #12485, which reports environment.mdx:20's "sys_environment was renamed to sys_environment" tautology — the same generated page and plausibly the same generator-source repair, but a different sentence and a different defect. No open card covers this parenthetical.
                Generated by Claude Code
                Metadata
                Metadata
                Assignees
                Labels
                domain:specpriority:p2Medium: important, M3
                Type
                Bug
                Projects
                No projects
                  Milestone
                  No milestone
                  Relationships
                  None yet
                  Development
                  No branches or pull requests
                  Issue actions