Skip to content

PR #100 dropped the metadata-authoring destination in five more places than the four #102 names #148

Closed
Task
#232
Closed
PR #100 dropped the metadata-authoring destination in five more places than the four #102 names#148
Task
#232
Assignees
os-zhuang

Description

@os-project-manager
os-project-manager
opened on Aug 22, 2026

Found while executing #102 (the ruled Studio card). Filed rather than folded in: #102's dispatch declared a six-file surface and named exactly four rewrite sites; these five are outside it, and widening the surface without reporting is what that card forbids.

How this was measured

By diffing PR #100 (adbcafc, restricted to content/docs), not by enumerating pages from memory:

git show adbcafc -U0 -- 'content/docs'> pr100.diff

Then classifying each removed Console occurrence by what it pointed at. #102's four are the ones where the removed noun named a metadata-authoring destination and the replacement dropped it. The same classification finds five more.

The five

Verified on origin/main at 514527b:

SitePR #100 removedIt reads todayPoints at
build/index.mdx:13table row **Console click-build** (fallback)table row **Click-build** (fallback)authoring, click path — the exact peer of build/data/index.mdx:21, which #102 fixes
build/index.mdx:3 (description)"by clicking in Console""by clicking through forms"the same click-build path
build/index.mdx:52"Wire a Console form.""Wire a form."form design
build/automation/flows.mdx:9"Console's flow builder""the flow builder"flow authoring
build/automation/flows.mdx:279"Console ships a visual flow builder""ObjectOS ships a visual flow builder"flow authoring — substituted with the product name, so the where is still unnamed

The first is the sharpest: build/index.mdx:13 and build/data/index.mdx:21 carry the same "click-build" row on two pages, and after #102 only one of them names Studio.

Flow authoring really is Studio's, and it is measurable rather than inferred: PILLAR_FOR_SURFACE_TYPE maps flow to the automations pillar (objectui packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx, origin/main at 6ff0eb1).

Everything else PR #100 dropped is correct and must stay dropped

The same sweep classified the rest as the end-user / rendering sense of the word — "a button in Console's record detail", "records in Console", "REST, Console, ObjectQL". Those are #79's unnamed surface and the noun is correctly gone. This card is only about occurrences that named where an author goes.

What settling it looks like

Apply #102's ruling to the five, the same way #102 applied it to its four: name Studio as the destination, without reintroducing Console. The decision is already made — this is transcription, not a question. build/index.mdx:13 should read as build/data/index.mdx:21 now does.

Cost of leaving it

The corpus ends up half-converted: the Build index says "Click-build" with no destination while the page it links to says "Studio → Objects → New Object". A reader who greps for the authoring surface finds it named in some places and absent in others, which is the state #102 exists to end.

Related: #102 (the ruling), #79, #100.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Task

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" + '
PR #100 dropped the metadata-authoring destination in five more places than the four #102 names · Issue #148 · objectstack-ai/objectos · GitHub
    Skip to content
    PR #100 dropped the metadata-authoring destination in five more places than the four #102 names #148
    Closed
    Task
    #232
    Closed
    PR #100 dropped the metadata-authoring destination in five more places than the four #102 names#148
    Task
    #232
    Assignees
    os-zhuang
    Description
    @os-project-manager
    os-project-manager
    opened on Aug 22, 2026
    Found while executing #102 (the ruled Studio card). Filed rather than folded in: #102's dispatch declared a six-file surface and named exactly four rewrite sites; these five are outside it, and widening the surface without reporting is what that card forbids.
    How this was measured
    By diffing PR #100 (adbcafc, restricted to content/docs), not by enumerating pages from memory:
    git show adbcafc -U0 -- 'content/docs'> pr100.diff
    Then classifying each removed Console occurrence by what it pointed at. #102's four are the ones where the removed noun named a metadata-authoring destination and the replacement dropped it. The same classification finds five more.
    The five
    Verified on origin/main at 514527b:
    SitePR #100 removedIt reads todayPoints at
    build/index.mdx:13table row **Console click-build** (fallback)table row **Click-build** (fallback)authoring, click path — the exact peer of build/data/index.mdx:21, which #102 fixes
    build/index.mdx:3 (description)"by clicking in Console""by clicking through forms"the same click-build path
    build/index.mdx:52"Wire a Console form.""Wire a form."form design
    build/automation/flows.mdx:9"Console's flow builder""the flow builder"flow authoring
    build/automation/flows.mdx:279"Console ships a visual flow builder""ObjectOS ships a visual flow builder"flow authoring — substituted with the product name, so the where is still unnamed
    The first is the sharpest: build/index.mdx:13 and build/data/index.mdx:21 carry the same "click-build" row on two pages, and after #102 only one of them names Studio.
    Flow authoring really is Studio's, and it is measurable rather than inferred: PILLAR_FOR_SURFACE_TYPE maps flow to the automations pillar (objectui packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx, origin/main at 6ff0eb1).
    Everything else PR #100 dropped is correct and must stay dropped
    The same sweep classified the rest as the end-user / rendering sense of the word — "a button in Console's record detail", "records in Console", "REST, Console, ObjectQL". Those are #79's unnamed surface and the noun is correctly gone. This card is only about occurrences that named where an author goes.
    What settling it looks like
    Apply #102's ruling to the five, the same way #102 applied it to its four: name Studio as the destination, without reintroducing Console. The decision is already made — this is transcription, not a question. build/index.mdx:13 should read as build/data/index.mdx:21 now does.
    Cost of leaving it
    The corpus ends up half-converted: the Build index says "Click-build" with no destination while the page it links to says "Studio → Objects → New Object". A reader who greps for the authoring surface finds it named in some places and absent in others, which is the state #102 exists to end.
    Related: #102 (the ruling), #79, #100.
    Metadata
    Metadata
    Assignees
    Labels
    No labels
    No labels
    Type
    Task
    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('^' + ".*" + '
PR #100 dropped the metadata-authoring destination in five more places than the four #102 names · Issue #148 · objectstack-ai/objectos · GitHub
      Skip to content
      PR #100 dropped the metadata-authoring destination in five more places than the four #102 names #148
      Closed
      Task
      #232
      Closed
      PR #100 dropped the metadata-authoring destination in five more places than the four #102 names#148
      Task
      #232
      Assignees
      os-zhuang
      Description
      @os-project-manager
      os-project-manager
      opened on Aug 22, 2026
      Found while executing #102 (the ruled Studio card). Filed rather than folded in: #102's dispatch declared a six-file surface and named exactly four rewrite sites; these five are outside it, and widening the surface without reporting is what that card forbids.
      How this was measured
      By diffing PR #100 (adbcafc, restricted to content/docs), not by enumerating pages from memory:
      git show adbcafc -U0 -- 'content/docs'> pr100.diff
      Then classifying each removed Console occurrence by what it pointed at. #102's four are the ones where the removed noun named a metadata-authoring destination and the replacement dropped it. The same classification finds five more.
      The five
      Verified on origin/main at 514527b:
      SitePR #100 removedIt reads todayPoints at
      build/index.mdx:13table row **Console click-build** (fallback)table row **Click-build** (fallback)authoring, click path — the exact peer of build/data/index.mdx:21, which #102 fixes
      build/index.mdx:3 (description)"by clicking in Console""by clicking through forms"the same click-build path
      build/index.mdx:52"Wire a Console form.""Wire a form."form design
      build/automation/flows.mdx:9"Console's flow builder""the flow builder"flow authoring
      build/automation/flows.mdx:279"Console ships a visual flow builder""ObjectOS ships a visual flow builder"flow authoring — substituted with the product name, so the where is still unnamed
      The first is the sharpest: build/index.mdx:13 and build/data/index.mdx:21 carry the same "click-build" row on two pages, and after #102 only one of them names Studio.
      Flow authoring really is Studio's, and it is measurable rather than inferred: PILLAR_FOR_SURFACE_TYPE maps flow to the automations pillar (objectui packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx, origin/main at 6ff0eb1).
      Everything else PR #100 dropped is correct and must stay dropped
      The same sweep classified the rest as the end-user / rendering sense of the word — "a button in Console's record detail", "records in Console", "REST, Console, ObjectQL". Those are #79's unnamed surface and the noun is correctly gone. This card is only about occurrences that named where an author goes.
      What settling it looks like
      Apply #102's ruling to the five, the same way #102 applied it to its four: name Studio as the destination, without reintroducing Console. The decision is already made — this is transcription, not a question. build/index.mdx:13 should read as build/data/index.mdx:21 now does.
      Cost of leaving it
      The corpus ends up half-converted: the Build index says "Click-build" with no destination while the page it links to says "Studio → Objects → New Object". A reader who greps for the authoring surface finds it named in some places and absent in others, which is the state #102 exists to end.
      Related: #102 (the ruling), #79, #100.
      Metadata
      Metadata
      Assignees
      Labels
      No labels
      No labels
      Type
      Task
      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('^' + ".*" + '
PR #100 dropped the metadata-authoring destination in five more places than the four #102 names · Issue #148 · objectstack-ai/objectos · GitHub
        Skip to content
        PR #100 dropped the metadata-authoring destination in five more places than the four #102 names #148
        Closed
        Task
        #232
        Closed
        PR #100 dropped the metadata-authoring destination in five more places than the four #102 names#148
        Task
        #232
        Assignees
        os-zhuang
        Description
        @os-project-manager
        os-project-manager
        opened on Aug 22, 2026
        Found while executing #102 (the ruled Studio card). Filed rather than folded in: #102's dispatch declared a six-file surface and named exactly four rewrite sites; these five are outside it, and widening the surface without reporting is what that card forbids.
        How this was measured
        By diffing PR #100 (adbcafc, restricted to content/docs), not by enumerating pages from memory:
        git show adbcafc -U0 -- 'content/docs'> pr100.diff
        Then classifying each removed Console occurrence by what it pointed at. #102's four are the ones where the removed noun named a metadata-authoring destination and the replacement dropped it. The same classification finds five more.
        The five
        Verified on origin/main at 514527b:
        SitePR #100 removedIt reads todayPoints at
        build/index.mdx:13table row **Console click-build** (fallback)table row **Click-build** (fallback)authoring, click path — the exact peer of build/data/index.mdx:21, which #102 fixes
        build/index.mdx:3 (description)"by clicking in Console""by clicking through forms"the same click-build path
        build/index.mdx:52"Wire a Console form.""Wire a form."form design
        build/automation/flows.mdx:9"Console's flow builder""the flow builder"flow authoring
        build/automation/flows.mdx:279"Console ships a visual flow builder""ObjectOS ships a visual flow builder"flow authoring — substituted with the product name, so the where is still unnamed
        The first is the sharpest: build/index.mdx:13 and build/data/index.mdx:21 carry the same "click-build" row on two pages, and after #102 only one of them names Studio.
        Flow authoring really is Studio's, and it is measurable rather than inferred: PILLAR_FOR_SURFACE_TYPE maps flow to the automations pillar (objectui packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx, origin/main at 6ff0eb1).
        Everything else PR #100 dropped is correct and must stay dropped
        The same sweep classified the rest as the end-user / rendering sense of the word — "a button in Console's record detail", "records in Console", "REST, Console, ObjectQL". Those are #79's unnamed surface and the noun is correctly gone. This card is only about occurrences that named where an author goes.
        What settling it looks like
        Apply #102's ruling to the five, the same way #102 applied it to its four: name Studio as the destination, without reintroducing Console. The decision is already made — this is transcription, not a question. build/index.mdx:13 should read as build/data/index.mdx:21 now does.
        Cost of leaving it
        The corpus ends up half-converted: the Build index says "Click-build" with no destination while the page it links to says "Studio → Objects → New Object". A reader who greps for the authoring surface finds it named in some places and absent in others, which is the state #102 exists to end.
        Related: #102 (the ruling), #79, #100.
        Metadata
        Metadata
        Assignees
        Labels
        No labels
        No labels
        Type
        Task
        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" + '
PR #100 dropped the metadata-authoring destination in five more places than the four #102 names · Issue #148 · objectstack-ai/objectos · GitHub
          Skip to content
          PR #100 dropped the metadata-authoring destination in five more places than the four #102 names #148
          Closed
          Task
          #232
          Closed
          PR #100 dropped the metadata-authoring destination in five more places than the four #102 names#148
          Task
          #232
          Assignees
          os-zhuang
          Description
          @os-project-manager
          os-project-manager
          opened on Aug 22, 2026
          Found while executing #102 (the ruled Studio card). Filed rather than folded in: #102's dispatch declared a six-file surface and named exactly four rewrite sites; these five are outside it, and widening the surface without reporting is what that card forbids.
          How this was measured
          By diffing PR #100 (adbcafc, restricted to content/docs), not by enumerating pages from memory:
          git show adbcafc -U0 -- 'content/docs'> pr100.diff
          Then classifying each removed Console occurrence by what it pointed at. #102's four are the ones where the removed noun named a metadata-authoring destination and the replacement dropped it. The same classification finds five more.
          The five
          Verified on origin/main at 514527b:
          SitePR #100 removedIt reads todayPoints at
          build/index.mdx:13table row **Console click-build** (fallback)table row **Click-build** (fallback)authoring, click path — the exact peer of build/data/index.mdx:21, which #102 fixes
          build/index.mdx:3 (description)"by clicking in Console""by clicking through forms"the same click-build path
          build/index.mdx:52"Wire a Console form.""Wire a form."form design
          build/automation/flows.mdx:9"Console's flow builder""the flow builder"flow authoring
          build/automation/flows.mdx:279"Console ships a visual flow builder""ObjectOS ships a visual flow builder"flow authoring — substituted with the product name, so the where is still unnamed
          The first is the sharpest: build/index.mdx:13 and build/data/index.mdx:21 carry the same "click-build" row on two pages, and after #102 only one of them names Studio.
          Flow authoring really is Studio's, and it is measurable rather than inferred: PILLAR_FOR_SURFACE_TYPE maps flow to the automations pillar (objectui packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx, origin/main at 6ff0eb1).
          Everything else PR #100 dropped is correct and must stay dropped
          The same sweep classified the rest as the end-user / rendering sense of the word — "a button in Console's record detail", "records in Console", "REST, Console, ObjectQL". Those are #79's unnamed surface and the noun is correctly gone. This card is only about occurrences that named where an author goes.
          What settling it looks like
          Apply #102's ruling to the five, the same way #102 applied it to its four: name Studio as the destination, without reintroducing Console. The decision is already made — this is transcription, not a question. build/index.mdx:13 should read as build/data/index.mdx:21 now does.
          Cost of leaving it
          The corpus ends up half-converted: the Build index says "Click-build" with no destination while the page it links to says "Studio → Objects → New Object". A reader who greps for the authoring surface finds it named in some places and absent in others, which is the state #102 exists to end.
          Related: #102 (the ruling), #79, #100.
          Metadata
          Metadata
          Assignees
          Labels
          No labels
          No labels
          Type
          Task
          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('^' + ".*" + '
PR #100 dropped the metadata-authoring destination in five more places than the four #102 names · Issue #148 · objectstack-ai/objectos · GitHub
            Skip to content
            PR #100 dropped the metadata-authoring destination in five more places than the four #102 names #148
            Closed
            Task
            #232
            Closed
            PR #100 dropped the metadata-authoring destination in five more places than the four #102 names#148
            Task
            #232
            Assignees
            os-zhuang
            Description
            @os-project-manager
            os-project-manager
            opened on Aug 22, 2026
            Found while executing #102 (the ruled Studio card). Filed rather than folded in: #102's dispatch declared a six-file surface and named exactly four rewrite sites; these five are outside it, and widening the surface without reporting is what that card forbids.
            How this was measured
            By diffing PR #100 (adbcafc, restricted to content/docs), not by enumerating pages from memory:
            git show adbcafc -U0 -- 'content/docs'> pr100.diff
            Then classifying each removed Console occurrence by what it pointed at. #102's four are the ones where the removed noun named a metadata-authoring destination and the replacement dropped it. The same classification finds five more.
            The five
            Verified on origin/main at 514527b:
            SitePR #100 removedIt reads todayPoints at
            build/index.mdx:13table row **Console click-build** (fallback)table row **Click-build** (fallback)authoring, click path — the exact peer of build/data/index.mdx:21, which #102 fixes
            build/index.mdx:3 (description)"by clicking in Console""by clicking through forms"the same click-build path
            build/index.mdx:52"Wire a Console form.""Wire a form."form design
            build/automation/flows.mdx:9"Console's flow builder""the flow builder"flow authoring
            build/automation/flows.mdx:279"Console ships a visual flow builder""ObjectOS ships a visual flow builder"flow authoring — substituted with the product name, so the where is still unnamed
            The first is the sharpest: build/index.mdx:13 and build/data/index.mdx:21 carry the same "click-build" row on two pages, and after #102 only one of them names Studio.
            Flow authoring really is Studio's, and it is measurable rather than inferred: PILLAR_FOR_SURFACE_TYPE maps flow to the automations pillar (objectui packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx, origin/main at 6ff0eb1).
            Everything else PR #100 dropped is correct and must stay dropped
            The same sweep classified the rest as the end-user / rendering sense of the word — "a button in Console's record detail", "records in Console", "REST, Console, ObjectQL". Those are #79's unnamed surface and the noun is correctly gone. This card is only about occurrences that named where an author goes.
            What settling it looks like
            Apply #102's ruling to the five, the same way #102 applied it to its four: name Studio as the destination, without reintroducing Console. The decision is already made — this is transcription, not a question. build/index.mdx:13 should read as build/data/index.mdx:21 now does.
            Cost of leaving it
            The corpus ends up half-converted: the Build index says "Click-build" with no destination while the page it links to says "Studio → Objects → New Object". A reader who greps for the authoring surface finds it named in some places and absent in others, which is the state #102 exists to end.
            Related: #102 (the ruling), #79, #100.
            Metadata
            Metadata
            Assignees
            Labels
            No labels
            No labels
            Type
            Task
            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('^' + ".*" + '
PR #100 dropped the metadata-authoring destination in five more places than the four #102 names · Issue #148 · objectstack-ai/objectos · GitHub
              Skip to content
              PR #100 dropped the metadata-authoring destination in five more places than the four #102 names #148
              Closed
              Task
              #232
              Closed
              PR #100 dropped the metadata-authoring destination in five more places than the four #102 names#148
              Task
              #232
              Assignees
              os-zhuang
              Description
              @os-project-manager
              os-project-manager
              opened on Aug 22, 2026
              Found while executing #102 (the ruled Studio card). Filed rather than folded in: #102's dispatch declared a six-file surface and named exactly four rewrite sites; these five are outside it, and widening the surface without reporting is what that card forbids.
              How this was measured
              By diffing PR #100 (adbcafc, restricted to content/docs), not by enumerating pages from memory:
              git show adbcafc -U0 -- 'content/docs'> pr100.diff
              Then classifying each removed Console occurrence by what it pointed at. #102's four are the ones where the removed noun named a metadata-authoring destination and the replacement dropped it. The same classification finds five more.
              The five
              Verified on origin/main at 514527b:
              SitePR #100 removedIt reads todayPoints at
              build/index.mdx:13table row **Console click-build** (fallback)table row **Click-build** (fallback)authoring, click path — the exact peer of build/data/index.mdx:21, which #102 fixes
              build/index.mdx:3 (description)"by clicking in Console""by clicking through forms"the same click-build path
              build/index.mdx:52"Wire a Console form.""Wire a form."form design
              build/automation/flows.mdx:9"Console's flow builder""the flow builder"flow authoring
              build/automation/flows.mdx:279"Console ships a visual flow builder""ObjectOS ships a visual flow builder"flow authoring — substituted with the product name, so the where is still unnamed
              The first is the sharpest: build/index.mdx:13 and build/data/index.mdx:21 carry the same "click-build" row on two pages, and after #102 only one of them names Studio.
              Flow authoring really is Studio's, and it is measurable rather than inferred: PILLAR_FOR_SURFACE_TYPE maps flow to the automations pillar (objectui packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx, origin/main at 6ff0eb1).
              Everything else PR #100 dropped is correct and must stay dropped
              The same sweep classified the rest as the end-user / rendering sense of the word — "a button in Console's record detail", "records in Console", "REST, Console, ObjectQL". Those are #79's unnamed surface and the noun is correctly gone. This card is only about occurrences that named where an author goes.
              What settling it looks like
              Apply #102's ruling to the five, the same way #102 applied it to its four: name Studio as the destination, without reintroducing Console. The decision is already made — this is transcription, not a question. build/index.mdx:13 should read as build/data/index.mdx:21 now does.
              Cost of leaving it
              The corpus ends up half-converted: the Build index says "Click-build" with no destination while the page it links to says "Studio → Objects → New Object". A reader who greps for the authoring surface finds it named in some places and absent in others, which is the state #102 exists to end.
              Related: #102 (the ruling), #79, #100.
              Metadata
              Metadata
              Assignees
              Labels
              No labels
              No labels
              Type
              Task
              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); }
})();
})();
PR #100 dropped the metadata-authoring destination in five more places than the four #102 names · Issue #148 · objectstack-ai/objectos · GitHub
                Skip to content
                PR #100 dropped the metadata-authoring destination in five more places than the four #102 names #148
                Closed
                Task
                #232
                Closed
                PR #100 dropped the metadata-authoring destination in five more places than the four #102 names#148
                Task
                #232
                Assignees
                os-zhuang
                Description
                @os-project-manager
                os-project-manager
                opened on Aug 22, 2026
                Found while executing #102 (the ruled Studio card). Filed rather than folded in: #102's dispatch declared a six-file surface and named exactly four rewrite sites; these five are outside it, and widening the surface without reporting is what that card forbids.
                How this was measured
                By diffing PR #100 (adbcafc, restricted to content/docs), not by enumerating pages from memory:
                git show adbcafc -U0 -- 'content/docs'> pr100.diff
                Then classifying each removed Console occurrence by what it pointed at. #102's four are the ones where the removed noun named a metadata-authoring destination and the replacement dropped it. The same classification finds five more.
                The five
                Verified on origin/main at 514527b:
                SitePR #100 removedIt reads todayPoints at
                build/index.mdx:13table row **Console click-build** (fallback)table row **Click-build** (fallback)authoring, click path — the exact peer of build/data/index.mdx:21, which #102 fixes
                build/index.mdx:3 (description)"by clicking in Console""by clicking through forms"the same click-build path
                build/index.mdx:52"Wire a Console form.""Wire a form."form design
                build/automation/flows.mdx:9"Console's flow builder""the flow builder"flow authoring
                build/automation/flows.mdx:279"Console ships a visual flow builder""ObjectOS ships a visual flow builder"flow authoring — substituted with the product name, so the where is still unnamed
                The first is the sharpest: build/index.mdx:13 and build/data/index.mdx:21 carry the same "click-build" row on two pages, and after #102 only one of them names Studio.
                Flow authoring really is Studio's, and it is measurable rather than inferred: PILLAR_FOR_SURFACE_TYPE maps flow to the automations pillar (objectui packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx, origin/main at 6ff0eb1).
                Everything else PR #100 dropped is correct and must stay dropped
                The same sweep classified the rest as the end-user / rendering sense of the word — "a button in Console's record detail", "records in Console", "REST, Console, ObjectQL". Those are #79's unnamed surface and the noun is correctly gone. This card is only about occurrences that named where an author goes.
                What settling it looks like
                Apply #102's ruling to the five, the same way #102 applied it to its four: name Studio as the destination, without reintroducing Console. The decision is already made — this is transcription, not a question. build/index.mdx:13 should read as build/data/index.mdx:21 now does.
                Cost of leaving it
                The corpus ends up half-converted: the Build index says "Click-build" with no destination while the page it links to says "Studio → Objects → New Object". A reader who greps for the authoring surface finds it named in some places and absent in others, which is the state #102 exists to end.
                Related: #102 (the ruling), #79, #100.
                Metadata
                Metadata
                Assignees
                Labels
                No labels
                No labels
                Type
                Task
                Projects
                No projects
                  Milestone
                  No milestone
                  Relationships
                  None yet
                  Development
                  No branches or pull requests
                  Issue actions