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
docs: correct gallery DB diagnostics sampling description (#13369)
Adam Eivybee963bdcc8a
diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.mdindex aa4d56da10..bcf6c68cb0 100644--- a/docs/CONTRIBUTING.md+++ b/docs/CONTRIBUTING.md@@ -305,10 +305,12 @@ the complete serial DB workload regardless of test-memo reuse, run`PORTOS_DB_PHASE_DIAGNOSTICS=1 npm run test:db` after the earlier validationstages finish. The observer reads only `portos_test` session state, waits,transaction ages and run-lock ownership: no query text, network addresses or-record contents. It samples at most three times per phase, caps each snapshot-at 16 sessions, and uses a separate connection with a 500 ms statement timeout.+record contents. It samples about once a second while a phase is slow (fast+phases need no SQL), at most 32 snapshots per phase, caps each snapshot at 16+sessions, and uses a separate connection with a 500 ms statement timeout.Opt-in diagnostics add observation work; original test deadlines stay intact.-Failure messages retain bounded phase evidence even with quiet reporting.+Failure messages retain bounded phase evidence even with quiet reporting; without+the opt-in they still name the active phase and per-phase elapsed time.A passing run without a reproduced slow phase does not resolve the timeout.For server watch mode, run this alternative from the repository root: