@rubytech/create-sitedesk-code 0.1.524 → 0.1.526

package/payload/platform/docs/superpowers/plans/2026-07-24-task-1942-subaccount-switcher-brand-head.md

@@ -1,327 +0,0 @@
-# Task 1942 — Sub-account switcher to sidebar brand head — Implementation Plan
-
-> **For agentic workers:** REQUIRED SUB-SKILL: superpowers:executing-plans. Steps use checkbox (`- [ ]`) syntax.
-
-**Goal:** Open the sub-account picker by clicking the sidebar brand head; remove it from the footer kebab.
-
-**Architecture:** `Sidebar.tsx` owns a `switcherOpen` state and renders the brand head as a button (icon + lockup + chevron) when the switcher is available, with `SubAccountPicker` + a full-screen scrim anchored beneath `.side-brand`. `AccountMenu.tsx` loses the switcher block, its five props, and the `SubAccountPicker` import. `globals.css` makes `.side-brand` a positioned anchor, re-anchors the panel left-aligned, and deletes the dead footer overrides.
-
-**Tech Stack:** React 18, TypeScript, vitest + jsdom (Node 22), lucide-react icons.
-
-## Global Constraints
-
-- Node 22 for the jsdom test run (`platform/ui` requirement).
-- Switcher availability gate is exactly `subAccounts.length > 1 && Boolean(onSwitchAccount)`; unchanged from today.
-- No new task-id leaks in shipped docs; docs edit at `platform/plugins/docs/references/admin-ui.md`.
-- All paths below are relative to the worktree's `maxy-code/platform/ui/`.
-
----
-
-### Task 1: Strip the switcher out of AccountMenu
-
-**Files:**
-- Modify: `app/components/AccountMenu.tsx`
-- Test: `app/components/__tests__/AccountMenu.test.tsx`
-
-**Interfaces:**
-- Produces: `AccountMenuProps` with no `subAccounts`/`activeAccountId`/`switchingAccount`/`onSwitchAccount`/`refreshAccounts` fields.
-
-- [ ] **Step 1: Update the test to assert the switcher is gone**
-
-In `AccountMenu.test.tsx`, delete the two switcher tests (`renders no Switch account affordance with 0-1 sub-accounts` and `opens the sub-account picker and fires onSwitchAccount + refreshAccounts`, lines 56-88). Add one test:
-
-```tsx
-it('renders no Switch account affordance (relocated to sidebar brand head, Task 1942)', () => {
-  render(<AccountMenu {...baseProps} variant="admin" cacheKey="k" onOpenConversations={vi.fn()} />)
-  expect(screen.queryByRole('menuitem', { name: /switch account/i })).toBeNull()
-  expect(screen.queryByPlaceholderText(/search sub-accounts/i)).toBeNull()
-})
-```
-
-Remove `subAccounts`/`activeAccountId`/`switchingAccount`/`onSwitchAccount`/`refreshAccounts` from any remaining render in the file.
-
-- [ ] **Step 2: Run — expect fail (props still typed / item still renders)**
-
-Run: `npx vitest run app/components/__tests__/AccountMenu.test.tsx`
-Expected: FAIL (the Switch account menuitem still renders).
-
-- [ ] **Step 3: Remove the switcher from AccountMenu.tsx**
-
-- Delete the `import { SubAccountPicker } from './SubAccountPicker'` line.
-- In `AccountMenuProps`, delete the five switcher prop declarations and their doc comment block (`subAccounts?`, `activeAccountId?`, `switchingAccount?`, `onSwitchAccount?`, `refreshAccounts?`).
-- In the destructure, remove `subAccounts = []`, `activeAccountId = null`, `switchingAccount = false`, `onSwitchAccount`, `refreshAccounts`.
-- Delete the `switcherOpen` state and `switcherAvailable` const.
-- Delete the whole `{switcherAvailable && ( … <SubAccountPicker … /> … )}` JSX block.
-- Remove `UserRound` from the lucide-react import (it was used only by the deleted block; grep the file to confirm no other use).
-
-- [ ] **Step 4: Run — expect pass**
-
-Run: `npx vitest run app/components/__tests__/AccountMenu.test.tsx`
-Expected: PASS.
-
-- [ ] **Step 5: Commit**
-
-```bash
-git add maxy-code/platform/ui/app/components/AccountMenu.tsx maxy-code/platform/ui/app/components/__tests__/AccountMenu.test.tsx
-git commit -m "refactor(1942): remove sub-account switcher from AccountMenu"
-```
-
----
-
-### Task 2: Brand head becomes the switcher trigger in Sidebar
-
-**Files:**
-- Modify: `app/Sidebar.tsx`
-- Test: `app/__tests__/Sidebar-subaccount-switcher.test.tsx` (create), `app/__tests__/Sidebar-user-footer.test.tsx`
-
-**Interfaces:**
-- Consumes: `SubAccountPicker` from `./components/SubAccountPicker`; `ChevronDown` from `lucide-react`; existing `subAccounts`/`activeAccountId`/`switchingAccount`/`onSwitchAccount`/`refreshAccounts` Sidebar props.
-
-- [ ] **Step 1: Write the failing test (new file)**
-
-Create `app/__tests__/Sidebar-subaccount-switcher.test.tsx`:
-
-```tsx
-import React from 'react'
-import { render, screen, fireEvent } from '@testing-library/react'
-import { describe, it, expect, vi, beforeEach, afterEach } from 'vitest'
-import { Sidebar } from '../Sidebar'
-
-function jsonResponse(body: unknown, status = 200): Response {
-  return new Response(JSON.stringify(body), { status, headers: { 'content-type': 'application/json' } }) as Response
-}
-function routedFetch() {
-  return vi.spyOn(global, 'fetch').mockImplementation((input: RequestInfo | URL) => {
-    const url = typeof input === 'string' ? input : input.toString()
-    if (url.includes('/api/admin/sidebar-sessions')) return Promise.resolve(jsonResponse({ accountId: 'acct', sessions: [] }))
-    if (url.includes('/api/admin/system-stats')) return Promise.resolve(jsonResponse({ cpuPct: null, memUsedPct: 0.5, platform: 'darwin' }))
-    if (url.includes('/api/admin/version')) return Promise.resolve(jsonResponse({ installed: '1.0.0', latest: null, updateAvailable: false }))
-    return Promise.resolve(jsonResponse({}, 404))
-  })
-}
-const ACCOUNTS = [
-  { accountId: 'a1', businessName: 'House', role: 'admin', isHouse: true },
-  { accountId: 'a2', businessName: 'Client', role: 'admin', isHouse: false },
-]
-function baseProps(over: Record<string, unknown> = {}) {
-  return {
-    businessName: 'House', cacheKey: 'k', role: 'admin', userName: 'Ada Ops', userAvatar: null,
-    onSelectProjects: vi.fn(), onSelectTasks: vi.fn(), onCloseMobileDrawer: vi.fn(),
-    collapsed: false, mobileDrawerOpen: false, onSelectData: vi.fn(),
-    onLogout: vi.fn(), onDisconnect: vi.fn(async () => true), disconnecting: false, claudeConnected: true,
-    ...over,
-  }
-}
-beforeEach(() => { Object.defineProperty(document, 'hidden', { value: false, configurable: true }) })
-afterEach(() => { vi.restoreAllMocks() })
-
-describe('Sidebar sub-account switcher on the brand head (Task 1942)', () => {
-  it('brand head is a button that toggles the picker and fires refreshAccounts', () => {
-    routedFetch()
-    const refreshAccounts = vi.fn()
-    render(<Sidebar {...baseProps({ subAccounts: ACCOUNTS, activeAccountId: 'a1', switchingAccount: false, onSwitchAccount: vi.fn(), refreshAccounts })} />)
-    const head = screen.getByRole('button', { name: /switch sub-account/i })
-    expect(screen.queryByPlaceholderText(/search sub-accounts/i)).toBeNull()
-    fireEvent.click(head)
-    expect(screen.getByPlaceholderText(/search sub-accounts/i)).toBeInTheDocument()
-    expect(refreshAccounts).toHaveBeenCalledTimes(1)
-    fireEvent.click(head)
-    expect(screen.queryByPlaceholderText(/search sub-accounts/i)).toBeNull()
-  })
-
-  it('selecting a card calls onSwitchAccount and closes the picker', () => {
-    routedFetch()
-    const onSwitchAccount = vi.fn()
-    render(<Sidebar {...baseProps({ subAccounts: ACCOUNTS, activeAccountId: 'a1', switchingAccount: false, onSwitchAccount, refreshAccounts: vi.fn() })} />)
-    fireEvent.click(screen.getByRole('button', { name: /switch sub-account/i }))
-    fireEvent.click(screen.getByRole('button', { name: 'Client' }))
-    expect(onSwitchAccount).toHaveBeenCalledWith('a2')
-    expect(screen.queryByPlaceholderText(/search sub-accounts/i)).toBeNull()
-  })
-
-  it('single-account install: brand head is not a switcher button and no picker mounts', () => {
-    routedFetch()
-    render(<Sidebar {...baseProps({ subAccounts: [ACCOUNTS[0]], activeAccountId: 'a1', onSwitchAccount: vi.fn() })} />)
-    expect(screen.queryByRole('button', { name: /switch sub-account/i })).toBeNull()
-    expect(screen.queryByPlaceholderText(/search sub-accounts/i)).toBeNull()
-  })
-})
-```
-
-- [ ] **Step 2: Run — expect fail**
-
-Run: `npx vitest run app/__tests__/Sidebar-subaccount-switcher.test.tsx`
-Expected: FAIL (no button named "Switch sub-account").
-
-- [ ] **Step 3: Implement the trigger in Sidebar.tsx**
-
-Add imports: `SubAccountPicker` from `'./components/SubAccountPicker'`, and `ChevronDown` to the existing `lucide-react` import.
-
-Add state beside `footerMenuOpen`:
-
-```tsx
-const [switcherOpen, setSwitcherOpen] = useState(false)
-const switcherAvailable = (subAccounts?.length ?? 0) > 1 && Boolean(onSwitchAccount)
-```
-
-Replace the `<div className="side-brand">…</div>` block (icon + lockup) with:
-
-```tsx
-<div className="side-brand">
-  {switcherAvailable ? (
-    <button
-      type="button"
-      className="side-brand-trigger"
-      aria-haspopup="menu"
-      aria-expanded={switcherOpen}
-      aria-label="Switch sub-account"
-      onClick={() => {
-        const opening = !switcherOpen
-        setSwitcherOpen(opening)
-        if (opening) refreshAccounts?.()
-        console.info(`[admin-ui] op=subaccount-switcher-toggle anchor=brand-head open=${opening} available=true accounts=${subAccounts?.length ?? 0}`)
-      }}
-    >
-      <img className="side-brand-icon" src={brandIcon} alt="" aria-hidden="true" />
-      <span className="side-brand-lockup">
-        <span className="side-brand-business">{displayName}</span>
-        <span className="side-brand-product">{brand.productName}</span>
-      </span>
-      <ChevronDown size={14} className="side-brand-caret" aria-hidden="true" />
-    </button>
-  ) : (
-    <>
-      <img className="side-brand-icon" src={brandIcon} alt="" aria-hidden="true" />
-      <span className="side-brand-lockup">
-        <span className="side-brand-business">{displayName}</span>
-        <span className="side-brand-product">{brand.productName}</span>
-      </span>
-    </>
-  )}
-  {switcherOpen && (
-    <>
-      <div className="side-brand-scrim" aria-hidden="true" onClick={() => setSwitcherOpen(false)} />
-      <SubAccountPicker
-        open={switcherOpen}
-        accounts={subAccounts ?? []}
-        activeAccountId={activeAccountId ?? null}
-        switching={switchingAccount ?? false}
-        onSelect={(accountId) => onSwitchAccount?.(accountId)}
-        onClose={() => setSwitcherOpen(false)}
-      />
-    </>
-  )}
-</div>
-```
-
-In the footer `<AccountMenu … />`, delete the five props `subAccounts`, `activeAccountId`, `switchingAccount`, `onSwitchAccount`, `refreshAccounts` (the Sidebar keeps consuming them for the head). Leave `onOpenConversations` and the rest.
-
-- [ ] **Step 4: Run — expect pass**
-
-Run: `npx vitest run app/__tests__/Sidebar-subaccount-switcher.test.tsx`
-Expected: PASS.
-
-- [ ] **Step 5: Fix the footer test that asserted the switcher was in the kebab**
-
-In `app/__tests__/Sidebar-user-footer.test.tsx`, the test `threads the sub-account switcher and Conversations into the kebab menu` (lines 53-75) now asserts a false thing. Rewrite it to cover Conversations only:
-
-```tsx
-it('threads Conversations into the kebab menu (switcher moved to brand head, Task 1942)', async () => {
-  routedFetch({ cpuPct: null, memUsedPct: 0.5, platform: 'darwin' })
-  const onOpenConversations = vi.fn()
-  render(<Sidebar {...baseProps({ onOpenConversations })} />)
-  fireEvent.click(screen.getByRole('button', { name: 'Account menu' }))
-  expect(screen.queryByRole('menuitem', { name: /switch account/i })).toBeNull()
-  fireEvent.click(await screen.findByRole('menuitem', { name: /conversations/i }))
-  expect(onOpenConversations).toHaveBeenCalledTimes(1)
-})
-```
-
-- [ ] **Step 6: Run both Sidebar suites — expect pass**
-
-Run: `npx vitest run app/__tests__/Sidebar-subaccount-switcher.test.tsx app/__tests__/Sidebar-user-footer.test.tsx`
-Expected: PASS.
-
-- [ ] **Step 7: Commit**
-
-```bash
-git add maxy-code/platform/ui/app/Sidebar.tsx maxy-code/platform/ui/app/__tests__/Sidebar-subaccount-switcher.test.tsx maxy-code/platform/ui/app/__tests__/Sidebar-user-footer.test.tsx
-git commit -m "feat(1942): brand head opens the sub-account picker"
-```
-
----
-
-### Task 3: CSS — anchor the panel under the head, style the trigger, drop dead overrides
-
-**Files:**
-- Modify: `app/globals.css`
-
-**Interfaces:** consumes class names `side-brand`, `side-brand-trigger`, `side-brand-caret`, `side-brand-scrim`, `sub-account-picker-panel` from Task 2.
-
-- [ ] **Step 1: Add `position: relative` to `.side-brand`**
-
-In the `.side-brand { … }` rule, add `position: relative;`.
-
-- [ ] **Step 2: Add the trigger, caret, and scrim rules** (place beside `.side-brand`)
-
-```css
-.side-brand-trigger {
-  display: flex; align-items: center; gap: 10px; flex: 1; min-width: 0;
-  background: none; border: 0; padding: 0; margin: 0;
-  font: inherit; color: inherit; text-align: left; cursor: pointer;
-}
-.side-brand-caret { flex: none; color: var(--text-tertiary); }
-.side-brand-trigger:hover .side-brand-caret { color: var(--text-secondary); }
-.platform.sidebar-collapsed .side-brand-caret { display: none; }
-.side-brand-scrim { position: fixed; inset: 0; z-index: 40; }
-.platform.sidebar-collapsed .side-brand-scrim { display: none; }
-```
-
-- [ ] **Step 3: Re-anchor `.sub-account-picker-panel` under the head**
-
-The brand head is now the only consumer. In `.sub-account-picker-panel`, remove `left: 50%;` and `transform: translateX(-50%);`, remove the `min-width` (if present), and set `left: 0; right: 0; margin-top: 8px; z-index: 41;` so the panel spans the head's inner width and sits above the scrim.
-
-- [ ] **Step 4: Delete the dead footer overrides**
-
-Delete the `.side-foot-menu .sub-account-picker-panel { … }` and `.side-foot-menu .sub-account-picker-list { … }` rules and the comment above them that describes the footer kebab anchoring.
-
-- [ ] **Step 5: Run the class-name CSS gate + the switcher suites**
-
-Run: `npm run -s check:classname-css 2>/dev/null || node scripts/check-classname-css.mjs`
-Then: `npx vitest run app/__tests__/Sidebar-subaccount-switcher.test.tsx`
-Expected: gate clean; tests PASS.
-
-- [ ] **Step 6: Commit**
-
-```bash
-git add maxy-code/platform/ui/app/globals.css
-git commit -m "style(1942): anchor sub-account picker under the sidebar brand head"
-```
-
----
-
-### Task 4: Docs
-
-**Files:**
-- Modify: `platform/plugins/docs/references/admin-ui.md`
-
-- [ ] **Step 1: Update the switcher location**
-
-Find the passage describing the sub-account switcher opening from the footer kebab / user-footer AccountMenu. Rewrite it to state the switcher opens by clicking the sidebar brand head (the account name), with the picker dropping beneath it; note the footer kebab no longer carries it. Keep it to the existing register; no task-id string in the shipped doc.
-
-- [ ] **Step 2: Commit**
-
-```bash
-git add maxy-code/platform/plugins/docs/references/admin-ui.md
-git commit -m "docs(1942): sub-account switcher now opens from the sidebar brand head"
-```
-
-## Self-Review
-
-- **Spec coverage:** brand-head trigger (T2), whole-head + chevron + scrim decisions (T2/T3), AccountMenu strip (T1), CSS re-anchor + dead-override delete (T3), observability toggle log (T2 Step 3), docs (T4), test updates incl. the footer-test fix (T2 Step 5). All spec items mapped.
-- **Placeholder scan:** none; every code step shows code.
-- **Type consistency:** `SubAccountPicker` prop names (`open`, `accounts`, `activeAccountId`, `switching`, `onSelect`, `onClose`) match its component signature; Sidebar prop names match the existing signature.
-
-## Known follow-ups
-
-None at plan time. Any code-review finding out of scope is filed as a new `.tasks/` file per the sprint rules.

package/payload/platform/docs/superpowers/plans/2026-07-25-task-1974-uploads-intake-inbox.md

@@ -1,235 +0,0 @@
-# Task 1974 — uploads/ intake inbox Implementation Plan
-
-> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
-
-**Goal:** Reclassify the account `uploads/` directory from tool-owned scratch to a temporary intake inbox, and add a `stranded-intake` reconcile count so a node file-reference left pointing into `uploads/` is visible.
-
-**Architecture:** Doctrine plus audit change, no code path change. Three prose files are edited (`SCHEMA.md`, `data-manager.md`, `internals.md`), then the `platform-architecture` SKILL.md twin is regenerated from the docs corpus so the no-drift gate passes. Detection-only, mirroring the outbound `output/` rule landed by task 1930.
-
-**Tech Stack:** Markdown doctrine files; Node regen scripts (`docs/scripts/copy-docs.mjs`, `maxy-code/scripts/assemble-architecture-skill.mjs`); the drift gate `maxy-code/platform/scripts/check-architecture-skill-no-drift.mjs`; the bash test `fs-schema-guard.test.sh`.
-
-## Global Constraints
-
-- Zero em-dashes in all shipped prose.
-- The 1930 outbound rule must survive intact: the `output/` promote-out sentence and the `scratch-refs` / `stranded` counts stay present. `stranded-intake` is appended to the output contract, never a rename of `stranded`.
-- `uploads` stays in the `allowed-top-level` block of SCHEMA.md (files still land there).
-- The write-path guard, the admin-UI upload handler, and `memory-ingest` `sourcePath` behaviour are unchanged.
-- Reconcile output contract after this task: `unreachable=N broken-refs=M scratch-refs=P stranded=Q stranded-intake=R`.
-- Paths are relative to the `maxy-code/` subtree root inside the worktree.
-
----
-
-### Task 1: SCHEMA.md — reclassify uploads/ as intake inbox
-
-**Files:**
-- Modify: `platform/templates/account-schema/SCHEMA.md:31-39`
-
-**Interfaces:**
-- Produces: the doctrine text data-manager.md and internals.md refer to. No code symbols.
-
-- [ ] **Step 1: Remove `uploads/` from the "recreated on the next write" list.**
-
-At `SCHEMA.md:36-39`, change the list so `uploads/` is no longer among tool-owned rebuilt dirs:
-
-```
-The internal structure of these is owned by the writing tool and is recreated on
-the next write: `url-get/`, `output/`, `generated/`, `extracted/`,
-any published/served tree (`sites/`, `public/`), `agents/`, `specialists/`, and
-platform-internal areas (`cache/`, `secrets/`, `state/`, `logs/`, `tmp/`).
-```
-
-- [ ] **Step 2: Add the intake-inbox rule paragraph.**
-
-Immediately after the `output/` promote-out paragraph (ends at `SCHEMA.md:34`), insert a new paragraph. It states uploads is a temporary intake inbox, a file is promoted to its canonical bucket when its node is created, no persisted graph reference points into `uploads/`, and the per-`<attachmentId>` reason it is safe to move out of (unlike `output/`):
-
-```
-`uploads/` is a temporary intake inbox, not rebuilt scratch. A file lands at
-`uploads/<attachmentId>/` on upload and is promoted to its canonical entity
-bucket when its graph node is created: a Person or Organization file to
-`contacts/<name>/`, a Project file to `projects/<name>/`, anything else to
-`documents/`. A persisted graph reference must never point into `uploads/`.
-Unlike `output/`, each upload writes its own `uploads/<attachmentId>/` dir and no
-tool walks or rebuilds the subtree, so promoting a file out of it through the
-`data-manager` specialist is safe.
-```
-
-- [ ] **Step 3: Verify the edit.**
-
-Run:
-```bash
-cd platform/templates/account-schema
-# uploads no longer in the recreated-on-next-write list
-awk '/recreated on/,/logs.*tmp/' SCHEMA.md | grep -c 'uploads/' | grep -qx 0 && echo "OK: uploads removed from scratch list"
-# intake-inbox rule present
-grep -q 'temporary intake inbox' SCHEMA.md && echo "OK: intake rule present"
-# uploads still allowed-top-level
-grep -A40 'allowed-top-level' SCHEMA.md | grep -qx 'uploads' && echo "OK: uploads still allowed-top-level"
-# 1930 output/ rule survives
-grep -q 'promoted out of `output/`' SCHEMA.md && echo "OK: 1930 output rule intact"
-# zero em-dashes in this file
-! grep -q '—' SCHEMA.md && echo "OK: no em-dash"
-```
-Expected: all five OK lines.
-
-- [ ] **Step 4: Commit.**
-
-```bash
-git add platform/templates/account-schema/SCHEMA.md
-git commit -m "task: reclassify uploads/ as intake inbox in account SCHEMA.md (1974)"
-```
-
----
-
-### Task 2: data-manager.md — reconcile case (e), walk uploads/, promotion permission, output contract
-
-**Files:**
-- Modify: `platform/templates/specialists/agents/data-manager.md:24` (reconcile brief), `:30` (output contract), and the "What success looks like" area for the promotion permission.
-
-**Interfaces:**
-- Consumes: the SCHEMA.md intake-inbox rule from Task 1.
-- Produces: the `stranded-intake=R` field that internals.md documents in Task 3.
-
-- [ ] **Step 1: Add reconcile case (e) and include uploads/ in the walk.**
-
-At `data-manager.md:24`, extend the counted list. After case (d), add case (e): a graph file-reference that resolves into `uploads/`, the inbound intake mirror of the `output/` scratch case. State that the walk now includes `uploads/` (a file under `uploads/` with no referencing node folds into `unreachable`). Exact appended clause inside the sentence that enumerates (a) to (d):
-
-```
-, and (e) graph file-references that resolve into the `uploads/` intake inbox,
-which is a temporary landing area a file should have been promoted out of when
-its node was created. The walk now includes `uploads/`; a file under `uploads/`
-that no node references counts under (a) unreachable.
-```
-
-- [ ] **Step 2: Add the stewardship promotion permission for uploads/.**
-
-In "## What success looks like" (after `data-manager.md:16`, the paired-move paragraph), add a sentence permitting promotion out of `uploads/`:
-
-```
-- A file in the `uploads/` intake inbox whose graph node exists is promoted to
-  its canonical bucket (Person or Organization to `contacts/<name>/`, Project to
-  `projects/<name>/`, else `documents/`), paired with a `database-operator`
-  `sourcePath` update in the same pass, exactly as any other move.
-```
-
-- [ ] **Step 3: Change the output contract.**
-
-At `data-manager.md:30`, change the reconcile summary line:
-
-```
-For the reconcile audit: `unreachable=N broken-refs=M scratch-refs=P stranded=Q stranded-intake=R`.
-```
-
-- [ ] **Step 4: Verify the edit.**
-
-Run:
-```bash
-cd platform/templates/specialists/agents
-grep -q 'stranded-intake=R' data-manager.md && echo "OK: contract has stranded-intake"
-grep -q 'scratch-refs=P stranded=Q' data-manager.md && echo "OK: 1930 fields survive"
-grep -q '(e) graph file-references that resolve into the `uploads/`' data-manager.md && echo "OK: case e present"
-grep -q 'promoted to' data-manager.md && grep -q 'sourcePath` update' data-manager.md && echo "OK: promotion permission present"
-! grep -q '—' data-manager.md && echo "OK: no em-dash"
-```
-Expected: five OK lines.
-
-- [ ] **Step 5: Commit.**
-
-```bash
-git add platform/templates/specialists/agents/data-manager.md
-git commit -m "task: data-manager reconcile counts uploads/ intake drift as stranded-intake (1974)"
-```
-
----
-
-### Task 3: internals.md — document the reclassification and the stranded-intake count
-
-**Files:**
-- Modify: `platform/plugins/docs/references/internals.md:411`
-
-**Interfaces:**
-- Consumes: the reconcile contract from Task 2.
-- Produces: the corpus text the architecture SKILL.md twin regenerates from in Task 4.
-
-- [ ] **Step 1: Append the intake-inbox rule to the placement paragraph.**
-
-At `internals.md:411`, the sentence currently ends: "...is counted by the `data-manager` reconcile audit (`scratch-refs`, `stranded`); making that audit run on a standing periodic cadence is a filed follow-up." Extend it with the inbound mirror. Append after the `scratch-refs`/`stranded` clause:
-
-```
-The inbound mirror is the `uploads/` intake inbox: an uploaded file lands at `uploads/<attachmentId>/` and is promoted to its canonical entity bucket when its graph node is created, so a persisted node reference resolving into `uploads/` is intake drift, counted by the same reconcile audit as `stranded-intake`. Unlike `output/`, `uploads/` is never rebuilt by a tool, so the `data-manager` may promote a file out of it. The reconcile output contract is `unreachable=N broken-refs=M scratch-refs=P stranded=Q stranded-intake=R`.
-```
-
-- [ ] **Step 2: Verify the edit.**
-
-Run:
-```bash
-grep -q 'stranded-intake' platform/plugins/docs/references/internals.md && echo "OK: internals mentions count"
-grep -q 'intake inbox' platform/plugins/docs/references/internals.md && echo "OK: internals mentions reclassification"
-! grep -q '—' platform/plugins/docs/references/internals.md && echo "OK: no em-dash added"
-```
-Expected: three OK lines. (The last check should already pass before the edit; keep the added prose em-dash-free.)
-
-- [ ] **Step 3: Commit.**
-
-```bash
-git add platform/plugins/docs/references/internals.md
-git commit -m "task: internals.md documents uploads/ intake inbox and stranded-intake count (1974)"
-```
-
----
-
-### Task 4: Regenerate the architecture skill twin and pass the gates
-
-**Files:**
-- Modify (generated): `platform/plugins/admin/skills/platform-architecture/SKILL.md`
-- Run: `docs/scripts/copy-docs.mjs`, `maxy-code/scripts/assemble-architecture-skill.mjs`, `platform/scripts/check-architecture-skill-no-drift.mjs`, `platform/plugins/admin/hooks/__tests__/fs-schema-guard.test.sh`
-
-**Interfaces:**
-- Consumes: the edited internals.md from Task 3.
-- Produces: a SKILL.md byte-equal to what the gate regenerates.
-
-- [ ] **Step 1: Regenerate the corpus and the skill twin.**
-
-Run from the worktree repo root:
-```bash
-node docs/scripts/copy-docs.mjs
-node maxy-code/scripts/assemble-architecture-skill.mjs --brand maxy-code
-```
-Expected: `[copy-docs]` and `[platform-arch-assemble] op=write` lines, no error.
-
-- [ ] **Step 2: Run the drift gate.**
-
-Run:
-```bash
-node maxy-code/platform/scripts/check-architecture-skill-no-drift.mjs --brand maxy-code
-```
-Expected: exit 0, no drift reported. If it reports drift, the regen in Step 1 did not run or the SKILL.md was not re-written; re-run Step 1.
-
-- [ ] **Step 3: Run the write-guard test (regression boundary).**
-
-Run:
-```bash
-bash maxy-code/platform/plugins/admin/hooks/__tests__/fs-schema-guard.test.sh
-```
-Expected: all assertions pass. The guard is unchanged; `uploads/` is still an allowed write, so this stays green.
-
-- [ ] **Step 4: Commit the regenerated twin (and any corpus artefact the gate expects committed).**
-
-```bash
-git add platform/plugins/admin/skills/platform-architecture/SKILL.md
-git status --porcelain docs/public
-# stage docs/public/llms-full.*.txt only if it is a tracked artefact that changed
-git commit -m "task: regenerate platform-architecture skill twin for 1974"
-```
-
----
-
-## Land (Phase 6 handles this — not an implementation task)
-
-LANES.md and task-file archival are done in Phase 6c of the sprint, not here. The task's "LANES Ready row" line describes the pre-implementation state; because this sprint implements and archives in one motion, the end state is: task file under `.tasks/archive/`, no Ready row referencing 1974, and the archive sentence naming 1974. This is a deliberate deviation from the task's literal LANES line, recorded in Plan Conformity.
-
-## Self-Review
-
-- **Spec coverage:** SCHEMA.md reclassification (Task 1), data-manager.md case (e) + walk + promotion + contract (Task 2), internals.md + twin regen (Tasks 3-4), LANES (Phase 6c). Every in-scope item maps to a task.
-- **Out of scope confirmed untouched:** no auto-promotion hook, no cadence (1931), no CC-native uploads reach, no write-guard edit, no ingest-path edit.
-- **Type consistency:** the single shared token is the output-contract string; it reads `unreachable=N broken-refs=M scratch-refs=P stranded=Q stranded-intake=R` identically in Tasks 2 and 3.
-- **Placeholder scan:** none; every edit carries its literal text.