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
fix: unblock release CI by marking the receipt-sweep hook test-only, and make the release agent stay with its PR through CI
[._.]/ Adam Eivy5350dd4bee66
diff --git a/server/services/cosMergeHandoff.test.js b/server/services/cosMergeHandoff.test.jsindex 80427b1b02..103a489baa 100644--- a/server/services/cosMergeHandoff.test.js+++ b/server/services/cosMergeHandoff.test.js@@ -77,7 +77,7 @@ const pending = () => readPendingMergePrs(f.apps.get('app1'));// ordered. Imported at call time: the restart case resets the module registry.const handedOff = async (overrides) => {const result = await handoff(overrides);- await (await import('./prWatcher.js')).sweepPendingMergeApp('app1');+ await (await import('./prWatcher.js'))._sweepPendingMergeApp('app1');return result;};const greenChecks = () => { f.pr.statusCheckRollup = [{ conclusion: 'SUCCESS' }]; };diff --git a/server/services/prWatcher.js b/server/services/prWatcher.jsindex db8293bfff..235b8b38f2 100644--- a/server/services/prWatcher.js+++ b/server/services/prWatcher.js@@ -700,7 +700,7 @@ export async function sweepPendingMergePrs() {* timer. It spends no tick budget — the receipt is not a cadence cycle — and* never throws: the timer sweep remains the owner of every queued entry.*/-export function sweepPendingMergeApp(appId) {+export function _sweepPendingMergeApp(appId) {const inFlight = pendingMergeSweeps.get(appId);if (!inFlight) return receiptSweep(appId);// That pass read the queue before this receipt was written: reload it once the@@ -731,7 +731,7 @@ function receiptSweep(appId) {* bounded follow-up poll. Never rejects.*/export function followUpHandoffReceipt(appId, receiptId) {- return sweepPendingMergeApp(appId)+ return _sweepPendingMergeApp(appId).then(() => armHandoffFollowUp(appId, receiptId)).catch((err) => {console.error(`❌ Handoff follow-up for app ${appId} could not be armed: ${err.message}`);@@ -810,7 +810,7 @@ async function pollHandoffFollowUp(appId, poller) {if (blocked) {console.warn(`⏸️ Handoff follow-up poll for app ${appId} skipped: ${blocked}`);} else {- const result = await sweepPendingMergeApp(appId);+ const result = await _sweepPendingMergeApp(appId);// null: receiptSweep already logged the thrown failure.if (result && !result.ok) {console.error(`❌ Handoff follow-up poll for app ${appId} failed: ${result.reason || 'sweep error'}`);diff --git a/server/services/taskPromptDefaults/integrity.snapshot.json b/server/services/taskPromptDefaults/integrity.snapshot.jsonindex e9f019f899..3a8c7b3058 100644--- a/server/services/taskPromptDefaults/integrity.snapshot.json+++ b/server/services/taskPromptDefaults/integrity.snapshot.json@@ -24,7 +24,7 @@"data-integrity": "5fcc4f5044101e89da5bbf4890c11a1c","data-safety": "25e79bc34cfadeab3cc3969a6c3421c2","dependency-updates": "2d94021c979a86a349e125f5c15665d8",- "do-release": "0ee9c504bad68f4a73be15f0b955a796",+ "do-release": "dcb1b0c84712f7824afd9c44cb4208da","do-replan": "35660eb7b43e4259a6a9253ed288a1db","documentation": "c94797b4bd3a0d554e225888ed48b76b","error-handling": "416b4e9aa2c1fcc3bfea7a2d38814ae5",@@ -89,7 +89,7 @@"data-integrity": 1,"data-safety": 3,"dependency-updates": 7,- "do-release": 17,+ "do-release": 18,"do-replan": 2,"documentation": 9,"error-handling": 4,@@ -328,7 +328,8 @@"5a82eec9f86ad05185ed77a42dbfd9d4","cd936b9a4fb76273b36ec54c3ed6d5ba","b185da91e17d796514d841378fc7be6b",- "e2fb83ae74cc759d1fface857169badc"+ "e2fb83ae74cc759d1fface857169badc",+ "0ee9c504bad68f4a73be15f0b955a796"],"do-replan": ["59a57f1bb445138c30ab4fa23630c6f8"diff --git a/server/services/taskPromptDefaults/prompts.js b/server/services/taskPromptDefaults/prompts.jsindex 1b4ea5c8e0..c7cf8ce9b6 100644--- a/server/services/taskPromptDefaults/prompts.js+++ b/server/services/taskPromptDefaults/prompts.js@@ -3956,6 +3956,10 @@ The PortOS Code Review Defaults rendered into \`{reviewers}\` are advisory for tRun the bundled \`/do:release\` workflow (or its equivalent \`release\` skill) in autonomous mode with no \`--interactive\` flag. It owns release readiness, version/changelog finalization, tests/build, optional code review, PR creation, CI, merge, tagging, and the final report. Every accepted finding must be resolved before merge or release; required CI and release tests/build checks must also pass — and a failing test or red CI run is work for Step 4, not a reason to end the run.+### Stay with the release PR until it is MERGED and tagged++Opening the release PR is the middle of the run, not the end. Stay in this session and drive it to completion: wait for CI on the release PR with \`gh pr checks <PR_NUM> --watch --fail-fast --interval 30\` (repeat after each fix; a few minutes of apparent silence is not a reason to stop), read every failing job's log, and apply Step 4 to each red check — including a failure inherited from \`<DEV_BRANCH>\`. When the fix belongs on \`<DEV_BRANCH>\`, land it there through its own PR (never push to the protected branch directly), then bring it into the release PR (merge the updated \`<DEV_BRANCH>\` into the release PR's head or re-run the workflow) and wait again. Once required CI is green, merge, confirm the release workflow created the tag and the GitHub Release (poll \`gh release view vX.Y.Z\`; never tag by hand), and only then write your report. Do not end the run with \`INCOMPLETE\`, "next run should resume", or a CI-pending release PR unless a Step 4 stop condition (fresh sub-agent also failed, or a real human-only blocker) actually applies — and name that condition in the report. An idle-session nudge is a signal that you stopped too early: continue, do not summarize.+### Release naming and notesWhen the canonical release workflow compiles the notes for a new release, the agent in charge of the release MUST choose the release name. Read the complete release range and identify the one or two biggest user-visible wins — especially performance, reliability, accessibility, or bandwidth improvements — then choose a short, memorable, fun name that is accurate to those wins (for example, \`Performant Dragon\`). The name is a theme, not a new product claim: do not invent benefits, use private data, repeat implementation jargon, or settle for a generic label such as \`Update\`.diff --git a/server/services/taskPromptDefaults/versions.js b/server/services/taskPromptDefaults/versions.jsindex 25edfbf2cf..eb38bc62d7 100644--- a/server/services/taskPromptDefaults/versions.js+++ b/server/services/taskPromptDefaults/versions.js@@ -80,7 +80,7 @@ export const PROMPT_VERSIONS = {'better-test-quality': 2, // v2: adds mocks that drift from the module they replace (members/exports the real module lacks). Previous version: v1: vacuous/weak/redundant existing tests, proven with a mutation probe. Distinct from test-coverage, which owns the gaps.'stash-cleanup': 2, // v2: the STALE/ABANDONED heuristic names `AGENTS.md` (or `CLAUDE.md`) as the policy file to check before assuming a stash contradicts current architecture (#4852). v1: triage git stash list — supersession check against main, drop superseded/stale entries, leave real unlanded work in place. Net-new type (no retired-hash history needed).'repo-sync': 1, // v1: verify + finish the deterministic install-wide origin-sync sweep (services/repoSync.js) — resolve mid-flight merges/rebases, decide what to do with uncommitted work, land or report unpushed branches, triage the stashes it could not prove redundant. Net-new type (no retired-hash history needed).- 'do-release': 17, // v17: previously accepted rules may be retired after documented value/feasibility reassessment. v16: unresolved accepted findings block release at every severity; optional reviewer availability remains optional. v15: renamed from `release-check` — the goal is a SHIPPED release, not a readiness check. The run first finishes in-flight work no live agent owns (open PRs, lingering branches via branch-reconcile), merges dependency-bot PRs, then releases; a blocker that survives three attempts goes to a sub-agent or a queued PortOS task instead of ending the run (v14 stopped at its 10-commit bound with the release PR open), local-only flakes no longer block a green-CI release, and routine design/preference decisions are made and listed for operator review. The operator's `{releaseOptions}` toggles (finishInFlight / mergeDependencyUpdates / resolveBlockers / autoDecide) gate each step. v14: the release agent names each release from its one or two biggest user-visible wins and writes the exact first heading the GitHub workflow promotes to the release title. v13: a failing test suite or red CI is work the run must FIX (reproduce, classify regression vs. bad test vs. environmental blocker, fix the root cause, verify, commit, resume) instead of a reason to halt the release — a pre-existing failure on main stopped v12 short with the release untouched; skipping/deleting/loosening a test to force green is explicitly not a fix, and the loop is bounded (3 attempts per failure, 10 fix commits per run). v12: code review is advisory and only CI gates release progress; v11: delegate release mechanics to bundled slashdo release and pin PortOS-configured reviewers. v10: the release-documentation search names the `AGENTS.md` (or `CLAUDE.md`) context instead of CLAUDE.md alone (#4852). v9: Step 1 reconciles missing GitHub Releases against git release tags (publishing any missing tag with .changelog/vX.Y.Z.md as body and --latest=false when a newer version exists) BEFORE evaluating if enough unreleased work has accumulated; v8: database-backed release tests are provisioned and run using the repo's documented isolated test database before the release PR gate; v7: Step 1 also reads the UNCOLLECTED changelog fragments (the fragment dir, plus whatever preview command that repo documents — release-check is a generic {appName} prompt, so it never names a PortOS script to run) and counts substantive entries across the assembled notes — reading only the staged `.changelog/NEXT.md` under-counts a release whose entries are still per-branch fragments, so a ready release reported as "not enough work". v6: generic {appName} body (older defaults hardcoded "PortOS")+ 'do-release': 18, // v18: the run stays with the release PR through CI, fixes red checks (including ones inherited from the dev branch) and ends only with a merged, tagged, published release — v17 agent-36fff086 opened the release PR, got one idle nudge and reported INCOMPLETE with CI still pending. v17: previously accepted rules may be retired after documented value/feasibility reassessment. v16: unresolved accepted findings block release at every severity; optional reviewer availability remains optional. v15: renamed from `release-check` — the goal is a SHIPPED release, not a readiness check. The run first finishes in-flight work no live agent owns (open PRs, lingering branches via branch-reconcile), merges dependency-bot PRs, then releases; a blocker that survives three attempts goes to a sub-agent or a queued PortOS task instead of ending the run (v14 stopped at its 10-commit bound with the release PR open), local-only flakes no longer block a green-CI release, and routine design/preference decisions are made and listed for operator review. The operator's `{releaseOptions}` toggles (finishInFlight / mergeDependencyUpdates / resolveBlockers / autoDecide) gate each step. v14: the release agent names each release from its one or two biggest user-visible wins and writes the exact first heading the GitHub workflow promotes to the release title. v13: a failing test suite or red CI is work the run must FIX (reproduce, classify regression vs. bad test vs. environmental blocker, fix the root cause, verify, commit, resume) instead of a reason to halt the release — a pre-existing failure on main stopped v12 short with the release untouched; skipping/deleting/loosening a test to force green is explicitly not a fix, and the loop is bounded (3 attempts per failure, 10 fix commits per run). v12: code review is advisory and only CI gates release progress; v11: delegate release mechanics to bundled slashdo release and pin PortOS-configured reviewers. v10: the release-documentation search names the `AGENTS.md` (or `CLAUDE.md`) context instead of CLAUDE.md alone (#4852). v9: Step 1 reconciles missing GitHub Releases against git release tags (publishing any missing tag with .changelog/vX.Y.Z.md as body and --latest=false when a newer version exists) BEFORE evaluating if enough unreleased work has accumulated; v8: database-backed release tests are provisioned and run using the repo's documented isolated test database before the release PR gate; v7: Step 1 also reads the UNCOLLECTED changelog fragments (the fragment dir, plus whatever preview command that repo documents — release-check is a generic {appName} prompt, so it never names a PortOS script to run) and counts substantive entries across the assembled notes — reading only the staged `.changelog/NEXT.md` under-counts a release whose entries are still per-branch fragments, so a ready release reported as "not enough work". v6: generic {appName} body (older defaults hardcoded "PortOS")// A SCHEDULE task type absent from this map is silently exempt from// auto-upgrade forever: taskScheduleStore's upgrade block is gated on