Self-hosted, Self-Improving, Federated Everything App — dev management, agent orchestration, persistent mind, digital twin, second brain, and creative pipeline from a single dashboard over Tailscale to port the user into the OS
JavaScript ai-agentsdashboarddeveloper-toolsdigital-twinquantified-selfsecond-brainself-hostedtailscale
perf: keep the performance prompt pointer conditional and synthetic-only (#12998)
[._.]/ Adam Eivy60f0108a428a
diff --git a/server/services/taskPromptDefaults/integrity.snapshot.json b/server/services/taskPromptDefaults/integrity.snapshot.jsonindex a6a53e450a..8b1dd58fda 100644--- a/server/services/taskPromptDefaults/integrity.snapshot.json+++ b/server/services/taskPromptDefaults/integrity.snapshot.json@@ -39,7 +39,7 @@"model-comparison-refresh": "f66e070fa08e30edda2c3020289f0c67","module-hygiene": "1637fd164737e20db284fe5c2b440453","observability": "243e58bcfae2759f82caf3ff6c8fc9c5",- "performance": "45aa35e50c45cf9f4e7d3d7125bf4b5b",+ "performance": "b5a221d23042b7751d5ece776399b403","plan-feature": "7f859397ff16889ffc0cf5a8ba6bddab","plan-task": "b718701c2d4ed2b4900225fc58857208","plan-task-claim": "07f6252f00905f9c6e4134a3d3587310",diff --git a/server/services/taskPromptDefaults/prompts.js b/server/services/taskPromptDefaults/prompts.jsindex 3375bd7b0b..7d98cce249 100644--- a/server/services/taskPromptDefaults/prompts.js+++ b/server/services/taskPromptDefaults/prompts.js@@ -404,11 +404,11 @@ be scoped to visible consumers. Use synthetic large collections to verifyserver page limits, compact list projections, lazy details, bounded renderedrows, and no full history hydration hidden behind client-side slicing.-If the app is PortOS (it ships scripts/perf/browserCollectionAudit.mjs) and the-live browser is unauthenticated, run-node scripts/perf/browserCollectionAudit.mjs --route=/ --sibling=<tab> against-the synthetic fixture (see scripts/perf/README.md) for the cold, sibling and idle-counts above.+Only when the app is PortOS (it ships scripts/perf/browserCollectionAudit.mjs) and+the live browser is unauthenticated, also run+node scripts/perf/browserCollectionAudit.mjs --route=/ --sibling=/<path> against+its synthetic fixture (see scripts/perf/README.md). That is synthetic shell+traffic only; live UI load and idle transfer stay UNVERIFIED.Do not claim UI performance passed from source inspection or a small/emptyfixture alone. If browser access, an authorized session, or usable large-fixturediff --git a/server/services/taskPromptDefaults/versions.js b/server/services/taskPromptDefaults/versions.jsindex eacf69aba8..3c68b54e29 100644--- a/server/services/taskPromptDefaults/versions.js+++ b/server/services/taskPromptDefaults/versions.js@@ -36,7 +36,7 @@ export const PROMPT_VERSIONS = {// current {appName} body. See the retired-hash history in// integrity.snapshot.json + the self-heal in taskScheduleStore.js readSchedule().'security': 6, // v6: generic trust-model pointer (AGENTS.md Security Model + ETHOS.md for PortOS) replaces the PortOS-specific authority paragraph, adds the one-finding-per-class rule, and drops the redaction sentence the mode banners own (#12081, #12080). v5: distinguish delegated authority from untrusted content and require workflow-preserving boundary fixes. v4: adds tenant/resource isolation, SSRF, and unsafe deserialization — the service and data-API defects the v3 list (written for a web app) did not name. v3: carries {modeInstructions} (the pre-v3 body had no placeholder, so its own "fix and commit" steps fought a file-issues dispatch) and defers to the project's documented threat model, requiring an attacker-or-accident story per finding instead of a generic OWASP checklist walk. Previously v2: generic {appName} body (older default hardcoded "PortOS"/"server/routes" paths)- 'performance': 7, // v7: names the PortOS --route audit for an unauthenticated live browser (#12998). v6: the service/data-path and UI-load sections are "Where present" (apply what exists, skip the rest silently) and the app-specific reference-data sentence is a generic hunt bullet (#12078). v5: adds required service/data-path coverage (query plans, streaming vs buffering, batch shape, pools, partition pruning, cold start), hands spend to cost-efficiency, and replaces PortOS-specific collection names with generic ones — the prompt runs against every managed app. v4: requires UI route-load, idle-network and large-collection evidence; missing measurements are explicitly unverified.+ 'performance': 7, // v7: points a PortOS run at the synthetic --route audit when the live browser is unauthenticated, marking live UI load UNVERIFIED (#12998). v6: the service/data-path and UI-load sections are "Where present" (apply what exists, skip the rest silently) and the app-specific reference-data sentence is a generic hunt bullet (#12078). v5: adds required service/data-path coverage (query plans, streaming vs buffering, batch shape, pools, partition pruning, cold start), hands spend to cost-efficiency, and replaces PortOS-specific collection names with generic ones — the prompt runs against every managed app. v4: requires UI route-load, idle-network and large-collection evidence; missing measurements are explicitly unverified.'code-quality': 6, // v6: the triage lane ranks the three focused audits to run next under a `Recommended next audits` heading and cedes unhandled boundary calls to error-handling (#12085). v5: drops the read-instruction-files and scan-then-bound restatements the mode banners and discovery contract own (#12080). v4: hands generated-artifact/hand-synced-registry/layout-coupling drift to the better-structural-drift lane and counted branching + reader cost to better-complexity / better-cognitive-load, keeping conventional maintainability defects — the split across PortOS's specialist tasks. Previously v3: inventory structural drift, duplicate sources of truth, volatile generated artifacts, and incidental-layout coupling before conventional maintainability checks. v2: generic {appName} body (older default hardcoded "PortOS")'test-coverage': 4, // v4: files issues by default and, in implement mode, names the redundant test removed to pay for a new one in a suite over the size budget (#12087). v3: carries {modeInstructions}, ranks gaps by consequence rather than percentage, tests at the highest practical public boundary, requires naming the regression a new test uniquely catches, and hands existing-test quality to better-test-quality. Previously v2: generic {appName} body (older default hardcoded "PortOS")'accessibility': 5, // v5: the "skip what static analysis already covers" list now also names keyboard-trap/unreachable-control and faked-semantics findings, matching Biome's `useKeyWithClickEvents`, `noNoninteractiveElementToInteractiveRole`, `useFocusableInteractive`, and `noAriaHiddenOnFocusable` a11y rules (enabled in `client/biome.jsonc` alongside the four from v4) — the live-agent budget shifts further to focus-order/live-region/contrast/zoom issues static analysis still can't establish. Previously v4: checks for an existing JSX a11y linter (Biome's a11y group, jsx-a11y) first and skips findings it already catches deterministically (missing alt/labels, invalid/unsupported ARIA), so the live-agent budget goes to keyboard/focus/live-region/contrast/zoom issues static analysis can't establish. Previously v3: carries {modeInstructions}, names who is blocked and how far they get, and prefers a native element over a custom control with patched attributes. Previously v2: generic {appName} + the app UI (older default hardcoded "PortOS" + http://localhost:5555)