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: consolidate the GitHub triage catalog row after synchronization
[._.]/ Adam Eivyd04682cca7ed
diff --git a/server/lib/README.md b/server/lib/README.mdindex e71e2456e1..34c7876424 100644--- a/server/lib/README.md+++ b/server/lib/README.md@@ -492,7 +492,6 @@ The barrel `server/lib/index.js` is a machine-checkable enumeration of every pub| `githubNotificationAudit.js` | `AUDIT_WINDOW_DAYS`, `buildAuditSuggestions` — the GitHub notifications subscription audit's suggestions from 30 days of stored threads per repo × reason: unwatch, mute handled threads, and links for settings the API cannot change. || `githubNotificationParse.js` | `parseGhIncludeOutput`, `linkHeaderHasNext`, `pollIntervalSeconds`, `repoApiPath`, `advisoryIdFromUrl`, `GHSA_RE`, `notificationHtmlUrl`, `toNotificationRecord` — pure parsing for the GitHub notifications inbox: `gh api --include` output and thread records, with links rebuilt only onto the account's own GitHub host. || `githubNotificationPullRequest.js` | `notificationPullRequestTarget`, `notificationPullRequestView` — same-host PR targets and the inbox action eligibility projection; mutations always re-read the forge. |-| `githubNotificationTriage.js` | `TRIAGE_DECISIONS`, `TRUST_LEVELS`, `MASS_MENTION_THRESHOLD`, `computeThreadTrust`, `spamSignals`, `parseCiBranch`, `decideThread`, `ASSIST_VERDICTS`, `decisionFromVerdict`, `learnedDecisionForAction`, `applyLearnedRule`, `assistAction`, `selectNotificationProvider`, `agentHandoff`, `autopilotHandoff`, `agentRuleScope`, `agentRunPin`, `GENERIC_AGENT_LANE`, `APP_FREE_AGENT_LANES`, `AGENT_RULE_KINDS`, `AGENT_RULE_ACTIONS`, `GENERIC_RULE_KINDS`, `threadAgentKind`, `KIND_SQL`, `normalizeAgentRules`, `ruleAction`, `ruleActionScope`, `PINNED_TRIAGE_RULES` — the GitHub inbox's fixed trust, spam and routing rules plus Assist's verdict enum, learned rules, allowed actions and Private-account provider allow-list, plus agent lanes (with the generic `notification-resolve` lane's trust gate), per-repo automation rules (kind × agent/done/mute/leave, legacy `agent` booleans read as actions) and run-pin precedence; trust comes only from accounts, repo ownership and forge permissions, never from content. || `githubNotificationTriage.js` | `TRIAGE_DECISIONS`, `TRUST_LEVELS`, `MASS_MENTION_THRESHOLD`, `computeThreadTrust`, `spamSignals`, `parseCiBranch`, `decideThread`, `ASSIST_VERDICTS`, `decisionFromVerdict`, `learnedDecisionForAction`, `applyLearnedRule`, `assistAction`, `selectNotificationProvider`, `notificationAgentAccountBinding`, `agentHandoff`, `autopilotHandoff`, `agentRuleScope`, `agentRunPin`, `GENERIC_AGENT_LANE`, `APP_FREE_AGENT_LANES`, `AGENT_RULE_KINDS`, `AGENT_RULE_ACTIONS`, `GENERIC_RULE_KINDS`, `threadAgentKind`, `KIND_SQL`, `normalizeAgentRules`, `ruleAction`, `ruleActionScope`, `PINNED_TRIAGE_RULES` — the GitHub inbox's fixed trust, spam and routing rules plus Assist's verdict enum, learned rules, allowed actions and Private-account provider allow-list, plus agent lanes (with the generic `notification-resolve` lane's trust gate), per-repo automation rules (kind × agent/done/mute/leave, legacy `agent` booleans read as actions) and run-pin precedence; trust comes only from accounts, repo ownership and forge permissions, never from content. || `gitRemote.js` | `getOriginInfo`, `classifyOriginRemote`, `parseGitRemoteUrl`, `readRemoteUrl`, `isUpstreamOwner`, `isUpstreamFullName`, `UPSTREAM_OWNER`/`UPSTREAM_REPO` — safely reads and classifies checkout remotes against PortOS or a caller-supplied canonical upstream. Used by self-update and managed integrations to detect forks. || `gitStaleLock.js` | `gitLockPathFromError`, `isStaleGitLock`, `clearStaleGitLock`, `clearStaleGitLocksIn`, `STALE_GIT_LOCK_MIN_AGE_MS` — recognizes the `*.lock` a KILLED git process left behind and removes it so the caller can retry. A lock under `.git/modules/<submodule>/` is shared by every worktree of the repo, so one dead process wedges submodule checkout install-wide with a bogus "another git process is running". Removal requires a `.lock` path under a `.git` directory (so a malformed message cannot aim the unlink at `yarn.lock`) that is older than 30 minutes — 3x the longest git command PortOS runs (`worktreeManager.WORKTREE_ADD_TIMEOUT_MS`, pinned by a test), which is what keeps it from deleting a LIVE competitor's lock. The threshold is deliberately not a parameter. `clearStaleGitLock(message)` is the reactive form, wired into `services/gitSubmodules.js#updateSubmodule` and `worktreeManager.addWorktreeWithRetry`; `clearStaleGitLocksIn(gitDir)` sweeps ahead of `update.sh`/`update.ps1`, the most likely producer. `scripts/doctor.js` reports one as the blocker. |