8 Commits

Author	SHA1	Message	Date
Anso	41bf075eb0	feat(recovery): make rollback-recovery image lifecycle visible and controllable (#1753) ... * feat(recovery): make rollback-recovery image lifecycle visible and controllable GitHub discussion #1751 asked why Sencho creates sencho-rb/<id>/<service>:hold images during automatic updates and how to clean them up. That surfaced a real safety bug alongside the missing visibility: the manual single-image delete route did not consult the held-image predicate every other deletion path already honors, so a user could delete a rollback-protected image straight through the Images tab and silently break automatic recovery for that update. A short/truncated id also bypassed the predicate's full-id lookup. Fixes: - POST /images/delete now resolves the submitted id to its canonical form and checks the unified held-image predicate before deleting, returning 409 IMAGE_HELD_FOR_ROLLBACK for a protected image. - The Images tab no longer mislabels a protected image as plain "Unused"; a fully-synthetic hold image is kept out of the generic inventory entirely and surfaced instead in a new Resources -> Rollback tab, with an additive "Rollback protected" badge for images that still carry a normal tag too. New capability: - Two settings (Deploy Guardrails): superseded-generation retention (days, replaces a hardcoded 7) and a cap on retained generations per stack. - A new Resources -> Rollback tab lists every generation (stack, short id, state, retention) with an admin-gated manual release action, including releasing the current generation with an explicit warning that automatic rollback becomes unavailable until the next successful update. Release is a single atomic, server-revalidated transition so a stale UI read can never release a row that has since become ineligible. Also consolidated three near-duplicate implementations of the held-image predicate (two of which relied on a require() of a sibling .ts file that silently failed to resolve under the test runner and was never actually exercised by a real test before this change) into one shared module. Known follow-up, not fixed here: an orphaned sencho-rb tag whose recovery row no longer exists (DB restore, node re-add) is invisible in both the Images and Rollback tabs with no UI path to reclaim it. * fix(audit): add summary mapping for rollback generation release * fix(security): sanitize prune target in log sinks and cover release RBAC Closes two open js/log-injection findings on the system prune route by applying the same inline sanitizeForLog barrier the rest of the file already uses. The prune target is validated against an enum by parsePruneTargets before reaching these sinks, so the findings were false positives, but the barrier is cheap and removes the standing alerts on a file this change already touches. Also wraps the generation id in the release log line for consistency with the stack name beside it. Adds coverage for gaps a QA pass identified: - Release endpoint refuses a viewer and a deployer (Admin-only), leaving the generation and its artifacts untouched. - Viewer can still read the generations list, matching the sibling Resources routes. - The predicate the prune routes build reports full-stack rollback holds, not just service-scoped ones, and re-reads per call so a hold taken between plan and delete still gates the delete. - After releasing the current generation, no rollback point is claimed for the stack through any consumer of the current-generation lookup.	2026-08-02 21:55:22 -04:00
Anso	79914fe750	fix: recognize clean one-shot completions in health gate and drift (#1691) ... * fix: recognize clean one-shot completions in health gate and drift Treat exit 0 with restart policy no/absent as successful completion so init and migration jobs no longer fail post-update observation or show as service-missing, while long-running restart policies still fail closed. * fix: ignore residual health on clean one-shots and honor deploy.restart_policy Completed exit-0 jobs with no-restart intent no longer fail the health gate on leftover starting/unhealthy state, and Drift treats deploy.restart_policy with Compose precedence so any/on-failure services are not mistaken for one-shots. * fix: require explicit Compose restart no for one-shot recognition Docker inspect reports restart no for both intentional jobs and bare services that omit restart, so Health Gate and Drift now require declared restart:""no"" (or deploy.restart_policy condition none) and load Compose intent once per gate.	2026-07-24 09:41:21 -04:00
Anso	b1decbb32a	docs: v1 docs refresh (batch 7) (#1627) ... * docs(introduction): refresh screenshots and correct stale nav/tab coverage Replace all 5 screenshots with fresh 1920x1080 production captures. Document the shipped Take down stack action, the Compose Labels stack tab, and the Docker Labels Fleet tab, none of which were mentioned. Correct the Console nav item to note it is a limited-availability surface rather than a plain role/tier-gated view. * docs(quickstart): refresh screenshots and correct preflight, dashboard, and menu drift Replace all three quickstart screenshots with fresh captures and correct several claims that drifted from the current UI: - Document the environment preflight's 7th check (Sencho compose location), previously missing entirely from both the text and the screenshot alt text. - Add the Stack health table's Source and Port columns, and note that columns are sortable and default to load order. - Note the masthead's running-container count, live CPU/memory readout, and alert count. - Fix the profile menu list: replace the nonexistent "Feedback" entry with "Open New Issue", drop "Appearance" (it lives in Settings, not the profile menu), and add the conditional "Billing" entry. - Note that the sidebar groups stacks by Docker Compose label once labels are assigned, with pinned stacks first. * docs(configuration): document missing env vars and fix JWT secret wording Add SENCHO_UPLOAD_DIR, TRIVY_CACHE_DIR, SENCHO_MESH_RECONCILE_INTERVAL_MS, SENCHO_MESH_PROXY_TUNNEL_IDLE_MS, SENCHO_COMPOSE_COMMAND_TIMEOUT_MS, and SSO_OIDC_CUSTOM_ENABLED, all real environment variables that were missing from the reference tables. Clarify that the JWT signing secret has no environment variable at all, generated and stored in the database only, rather than implying an unused JWT_SECRET var exists. * docs(stack-management): refresh against current live app and source Rewrites the Stack Management page against the production node and frontend source: adds the Compose Labels anatomy tab (new since the last refresh), the Mute action on the stack header and sidebar context menu, corrects the update-available banner wording and the sidebar context menu's lifecycle ordering, notes the Doctor tab's severity dot and the scan-status banner, and replaces all 14 screenshots with fresh production captures. * docs(editor): refresh against current live app and source Replace all 8 screenshots with fresh 1920x1080 production captures (mobile shot at phone viewport). Document the self-stack protection dialog that blocks deploy/delete actions on the stack running the current Sencho instance, the multi-container summary strip and Compact/Detailed density toggle, the mutually exclusive Expand containers / Expand logs controls, the Files tab full-screen toggle, and the post-deploy scan-status banner on the Anatomy panel, none of which were previously covered. * docs(editor): recapture mobile compose screenshot without redaction The previous mobile screenshot used the plex stack, whose compose volume mount includes a real host path that had to be blacked out and overlaid with placeholder text, leaving a visible seam. Recapture against the dozzle stack instead, whose only volume is the Docker socket, so the screenshot needs no editing. * docs(stack-file-explorer): refresh page against current app and code Renames "Files & Volumes tab" references to the current "Files" tab label, documents the full-screen toggle and word-wrap control, expands the non-browsable-volume reasons to match the current containment logic (single-file binds, the full protected host-path list, and the Docker-unreachable named-volume case), documents the 100-item bulk selection cap and the 5000-file/1 GiB archive limits, corrects the non-existent DISK_FULL error code, notes that override compose files are unprotected, and scopes the atomic-write claim to fs-backed roots. Replaces all 9 screenshots with fresh production captures taken in the Files tab's full-screen mode, so no other stack UI (health metrics, logs) appears in the background. * docs(resources): refresh against current live app and source * docs(dashboard): refresh against current live app and source * docs(app-store): refresh against current live app and source Replaces all 6 screenshots with fresh production captures and corrects the Environment Variables and About-panel metadata claims to match what the bundled LinuxServer.io registry actually returns today. * fix(docs): recapture app-store advanced-tab screenshot without scroll cut-off The prior capture was taken mid-scroll to reveal the Security checkbox, leaving the template logo and About text cropped awkwardly at the top. * docs(global-search): refresh against current live app and source * docs(deep-links): refresh against current live app and source - Add App Store, Logs, Update, Console, and Audit to the URL table (previously undocumented) - Document hub-only URL redirect behavior and cross-link to Multi-Node Fleet - Note Fleet tab URL segments do not always match their on-screen label (Status/configuration, Map/dependencies) - Document the no-env-files edge case (Env tab absent, falls back to compose) - Clarify Settings section-list state is phone-only; desktop always normalizes to /settings/appearance - Note which top-level views share identical URLs between desktop and phone - Remove greenfield-violating temporal phrasing ("now has", "as today") - Replace em dashes in touched bullet list * docs(appearance): refresh against current live app and source * docs(stack-activity): refresh against current live app and source Add the missing "Stack taken down" event category, cross-link the Suppressed badge to notification mute rules, list the new Compose Labels tab in the Anatomy panel strip, and replace both screenshots with current production captures. * docs(dossier): fix generated-facts wording, add rollback readiness section Corrects three Dossier tab Generated Facts rows against current frontend behavior: the Ports count is not filtered to host-published mappings, the Network row's "bridge" label is fixed text rather than a derived driver, and missing env var names appear only in the Markdown export, not the live tab. Adds a Rollback Readiness subsection under Connected Features (previously only an orphaned Limitations bullet), links to Compose Networking and Storage Portability, and clarifies that a missing export section can mean either an older node build or a failed on-demand fetch, not only a version gap. Recaptures all three screenshots against production. * docs(stack-drift): refresh against current live app and source Fixes the stack detail tab bar description (Compose Labels tab was missing, Files/Edit compose were wrongly listed as tabs), documents that re-check only requires read access to the stack (so viewer and auditor roles can trigger a ledger write), and cross-links the network findings to the Networking tab's runtime drift section and the Fleet Overview's Drift filter. Replaces all four screenshots with fresh 1920x1080 production captures. * docs(compose-doctor): refresh against current live app and source Corrects the rule count from 31 to 32 and documents the previously undocumented self-managed-stack guard rule and enforcement, the per-browser dismiss control for the summary card and Doctor tab dot, the acknowledged summary state, the full Health-Gated Updates verdict mapping, and the temporary exposure intent option. Replaces all four screenshots with production captures. * docs(compose-networking): refresh against current live app and source Adds cross-links to the new node-wide Networking operator page, documents the "view node networking" link and the unset/inherit exposure-intent pill labels, corrects the stale Resources Hub network-tab reference, and replaces all screenshots against the production node. * fix(docs): unbreak stack-activity page render The screenshot alt text used backslash-escaped quotes, which is invalid MDX/HTML attribute syntax. Mintlify failed to parse the file and silently dropped it from routing, so the page 404'd despite being listed in docs.json navigation. * docs(environment-guardrails): refresh against current live app and source Fix the ENV FILES section description: it lists env_file: entries and project files with an existence problem, not every declared env file. A cleanly-resolving project file is already named in the Project Environment File panel above it. Replace all three screenshots with current production captures. * docs(docker-label-audit): refresh against current live app and source Add production screenshots (page had none), a Capability gating section, a Limitations section, and a Troubleshooting accordion. Tighten the secret-redaction heuristic description and cross-link Stack Labels, Compose Doctor, Environment Guardrails, and Node Compatibility. * docs(compose-storage): refresh against current live app and source Captured fresh production screenshots (both prior images were stale) and fixed a leftover pre-rename card title pointing at the Files tab. * docs(stack-labels): refresh against current live app and source Removed the stale trailing-dot sidebar claim (that rendering was removed from the sidebar in a prior UI pass), documented the new label-scoped notification muting available from the sidebar, stack context menu, and Settings panel, corrected the Fleet Actions card copy to match the redesigned cards, added the previously undocumented bulk-assign size cap and the node-scoped label bulk-action API, and replaced all 8 screenshots with fresh production captures. * docs(sidebar): refresh against current live app and source Removes the stale per-row label dot claim (removed from StackRow), corrects the update indicator and Updates chip color from orange to fuchsia, and documents Mute/Take down in the context menu, the label group mute kebab, Ctrl+A/Esc bulk-mode shortcuts, pin-eviction toast, and the offline-node skip behavior in cross-node search. Replaces all 8 screenshots with fresh production captures. * docs(deploy-progress): refresh against current live app and source Corrected the Scan entry point (node-wide Scan this node from Security Overview, not a per-stack config scan), added the missing Take down verb and entry point, broadened recovery actions to cover restart and rollback failures, fixed the modal status text and raw-output color claims to match the live UI, and replaced all screenshots with fresh captures from a throwaway demo stack on the production node. * docs(atomic-deployments): refresh against current live app and source * docs(health-gated-updates): refresh against current live app and source * docs(deploy-enforcement): refresh against current live app and source Correct the tier note to every-tier (verified against the current policy gate, which no longer has a paid-only blocking switch), add the Security Overview deploy-enforcement summary card, tighten the honor- suppressions default wording, cross-link the separate pre-deploy scan advisory dialog to avoid confusion with the block dialog, and replace all three screenshots against the current production UI. * docs(blueprint-model): refresh against current live app and source Replaced all 11 screenshots with fresh production captures. Corrected the volume-destroying-drift Enforce-downgrade claim (appeared three times): that code path has no call sites in the runtime reconciler, so any compose edit on a stateful or state-unknown blueprint always re-enters Awaiting confirmation regardless of drift mode. Corrected the Create workflow (creation does not trigger an immediate reconciliation tick) and the Delete workflow (now requires typing the blueprint name to confirm). * docs(scheduled-operations): refresh against current live app and source * docs(blueprint-model): drop tier framing, treat as Community-native Blueprints carry no tier gate, so "available on every tier" implied a comparison that doesn't exist. Removed the tier framing from the intro note, the Prerequisites table, and the Security section; the role requirement (admin to write, every role to read) already says everything that matters. * docs(auto-update-policies): refresh against current live app and source Documents that every update trigger on this page, Apply now and scheduled Auto-update tasks alike, runs through the same atomic backup, build-aware rebuild, and post-update health gate as a manual update from the stack editor, and is subject to the same deploy enforcement policy gate. Corrects the readiness-computation description to scope it to registry-image services and cross-links to Health-Gated Updates, Atomic Deployments, Deploy Enforcement, and Stack Management. Replaces the readiness board screenshot with a fresh production capture and removes three orphaned screenshots left over from the page's prior CRUD-policy layout. * docs(auto-heal-policies): refresh against current live app and source Correct the admin-only prerequisite: viewing policies and history is open to every signed-in role, only creating/toggling/deleting requires admin. Rewrite the matching troubleshooting entry to match, note the overlap behavior between an All-services and a named-service policy on the same container, and replace all three screenshots with a real production policy. * docs(webhooks): refresh against current live app and source Replaced all three screenshots with fresh production captures (single webhook create/reveal flow, two-card configured list), verified every claim against WebhookService/StackOpLockService/registry.ts, and added the previously undocumented per-stack lock skip behavior for non-Git-source-sync actions with a matching troubleshooting entry. * docs(global-observability): refresh against current live app and source * docs(audit-log): refresh against current live app and source - Fix nav terminology: Audit is a top navigation tab, not a sidebar tab. - Correct retention claim: Admiral shows full retained history (default 90 days), not a fixed 14-day window; the 14-day clamp only applies to the Community API, which has no navigation entry point at all. - Fix settings path: Settings - Operations - Data Retention (previously pointed at the now-split Developer Diagnostics section). - Restore current Recovery Vault naming (was stale Sencho Cloud Backup). - Expand the tracked-actions list: stack take-down, label management, MFA reset, and notification suppression rules were missing. - Note that assigning the Auditor role itself requires Admiral. - Replace all four screenshots with fresh production captures (Stream, Table, expanded row, Data Retention) reflecting the current five-row retention card. * fix(audit-log): reframe data-retention screenshot to card content only The prior crop included the Settings sub-navigation panel, which isn't part of what the surrounding text describes. Retake tightly cropped to match the page's other screenshots (card content only, no chrome). * docs(multi-node): refresh against current live app and source Rewrites the Pilot Agent enrollment flow (now a generated compose.yaml plus docker compose up -d, not a single docker run command) and the Settings scope table (current registry: Stacks, Container Alerts, Docker & Storage, Data Retention, Mute Rules, Recovery, and the Admiral Account / Recovery Vault renames). Adds a Sencho Mesh cross-link matching the live add-node form copy. Replaces all eight screenshots with sanitized production captures. * docs(pilot-agent): refresh against current live app and source * docs(readme): refresh GitHub README against current live app Replace all 9 screenshots (stale top nav showing a removed Console item and missing the new Networking page); document Take down, Drift Detection, Environment and Secrets Guardrails, Storage Portability, Docker Label Audit, Remote Updates, and the node-wide Networking dashboard; fix a broken non-root-user anchor link; correct the notification channels list (no email channel exists yet) and the global search scope (pages, nodes, and stacks, not containers or services); rename "scan policy packs" to the current "scan policies" terminology; broaden the App Store bullet to cover custom registries. * docs(readme): reposition intro copy and refresh badge row Lead with DevOps/platform/sysadmin framing instead of homelab-first, drop pre-1.0 "production" language, state plainly that Sencho provides a UI instead of promotional "does the work you do" phrasing, and call out that multi-node was part of the architecture from the start. Swap the Discussions badge for CodeQL, last-commit, open issues, and live website/docs status badges, and add a blog link. * docs: retake Dashboard and Global Search screenshots for accuracy Configuration Status now shows Recovery Vault instead of the stale Cloud Backup label, and the search palette capture includes the Networking page entry added after the prior screenshot batch. * docs: refresh Fleet View page against current app Fleet View has drifted since its last rewrite: the Docker Labels tab, Export Dossier action, Networking filter/badge, node label pills and latency in topology, the Policy sync status row, and the node card Mute submenu were all shipped but undocumented. The Check Updates and Add Node actions also moved into the Overview toolbar (renamed Node Update / Manage Nodes) and no longer sit in the shared action row. Replaces all five screenshots with fresh production captures and corrects the masthead's motion description (a calm shimmer on Healthy, a steady glow on Degraded/Critical, not a pulsing dot). Also fixes a Fleet Sync limitation that claimed no first-party sync-status panel exists, now that the Status tab surfaces one. * docs: refresh Fleet Dossier page against current app Adds the page's first screenshot, documents the network exposure summary now included per stack, documents the storage-summary omission versus the Stack Dossier export, and adds two troubleshooting entries. * docs(fleet-federation): deep rewrite for the rollout-approval gate Federation's cordon and pin controls no longer take effect by themselves: the reconciler requires a confirmed rollout preview (Apply now -> Confirm Apply) before it mutates the fleet, and pinning or unpinning always clears a blueprint's approval. Rewrote the mental model, step-by-step, lifecycle table, security section, limitations, practical workflows, troubleshooting, and cross-links to reflect that gate. Also corrected the audit-log claims: cordon/uncordon/pin are not filterable by a node.cordon/blueprint.pin action taxonomy, only by the free-text search box against the method, path, and summary. Replaced 4 screenshots and added 3 new ones (production fleet plus an isolated instance to capture the rollout preview dialog in both a safe and a blocked state), and fixed one stale pin-workflow sentence in blueprint-model.mdx that the same audit surfaced. * docs(fleet-federation): drop tier-availability framing The feature isn't tier-gated, so calling out "every tier" reads as an unnecessary advertisement. Removed the tier note and the Community/ Admiral prerequisite row, and reworded two role-visibility sentences that had conflated tier with role. * docs(fleet-actions): deep rewrite for the v2 action-card redesign Rewrites the page against the shipped Fleet Action Card redesign: a single cyan rail with per-card action-class chips instead of the old per-card rose/purple/amber rails, plus the live blast-radius preview, dry-run, and confirmed-target binding mechanics that replaced the old static warning banners. Documents two previously-undocumented endpoints (match-preview, prune/estimate), the preview-confirm-execute model shared by all three cards, per-node locking, timeouts, and the version-gated confirmed-target contract for mixed-version fleets. All five screenshots recaptured against the live production UI. * docs(fleet-actions): fix nested quote in screenshot alt text * docs(fleet-sync): refresh against current app and document proxy gap Retake all screenshots against the live fleet (control authoring view, a genuine replica showing the read-only banner, and replicated suppression rows) and document a previously-unwritten behavior: scan policies, CVE suppressions, and misconfig acknowledgements are fetched localOnly and are not proxied through the node switcher like most other Security page tabs, so viewing a remote's Fleet Sync state requires signing into that instance directly. * docs(fleet-backups): refresh against current app and note new integration points Replaces all 6 screenshots with fresh 1920x1080 production captures and corrects several drifted details: the Cloud Snapshots panel's pagination and per-item delete action, the exact Recovery Vault storage-mode label, and the real per-file size-cap behavior (an oversized compose.yaml skips the whole stack; an oversized .env is dropped but the stack still captures). Documents two entry points that were missing from the page: the pre-update snapshot checkbox in Health-Gated Updates and the snapshot coverage nudge on the Storage Portability tab. Expands the single warning banner description in the detail view to cover all four banner types, notes the Snapshots tab and Recovery Vault are hub-only, and adds a Where Fleet Backups fits table cross-linking the six adjacent features. * docs(remote-updates): refresh against current app and add hardened-channel notes Replace all screenshots with fresh 1920x1080 production captures and fix the Node Updates trigger label (Check Updates -> Node Update). Add the Changelog tab, correct the reconnect overlay's stale 'Update timed out'/Try Reloading copy to the current Taking longer than expected/Reload to check text, and document the Admiral Hardened Build channel's carve-outs (pinned-but-not-blocked, entitlement-gated local update path). Disambiguate this page from the unrelated top-level Update (Health-Gated Updates) nav tab. * docs(node-compatibility): refresh against current app and expand capability list Replace all screenshots with fresh production captures (node switcher, capability lock card, connection test panel) and swap the lock-card example from a now-hidden Host Console to Audit Log, which is directly reachable. Bring the capability table from 26 to 35 entries to match the current registry, add a Mute Rules row, and split out fine-grained fallback capabilities (update-guard, service-scoped-update, cross-node-rbac, stack-down-remove-volumes) with their non-lock-card fallback behavior. Fix the compose-networking row, which incorrectly claimed to also gate the node-level Networking overview. Note that Pilot Agent nodes never advertise host-console regardless of version. * docs(security): refresh against current app and document scan-node launcher Replaces all screenshots with fresh production captures, documents the Scan this node launcher and the third Scanner setup toggle (pre-deploy scan advisory), tightens the Compose risks example list and the Policies block-condition description to match the live app, and adds an On a phone section. * docs(vulnerability-scanning): refresh for exploit intel and risk-based policies Documents exploit intelligence (KEV/EPSS evidence tags), the redesigned risk-based scan policies (severity/known-exploited/fixable block conditions replacing the single max-severity field), and the new Findings badge state. Replaces all screenshots with fresh production captures and adds a Secrets tab example. * docs: refresh CVE suppressions page Retook all screenshots against production (prior ones predated the triage-status/OpenVEX UI and the edit capability). Documented the suppression edit flow, which the page previously described as delete-and-recreate only. Corrected the remote-node banner copy on the Suppressions tab and added a screenshot of it. Cross-linked the Misconfig acknowledgements panel that now sits on the same tab. * docs(two-factor-authentication): refresh screenshots and document rate-limit layers Replace all 11 non-count-variant screenshots with fresh production captures. Document the throttled sign-in state precisely (kicker/hero/caption change, not just the input), that a replayed TOTP counts toward the lockout counter, and the separate per-network-address sign-in rate limit that sits in front of the per-account MFA lockout. * docs(api-tokens): refresh screenshots and document service-scoped deploy actions Deploy Only now authorizes eight lifecycle POSTs (was six): the per-service update and restore endpoints were missing from the scope table. Universal restrictions gained a row for image channel management, which was already rejecting API tokens in code but undocumented. Replaced all five screenshots with fresh captures showing the current three-scope create flow and a populated list with one token of each scope. * docs(upgrade): refresh against current app and remove legacy-version framing Fixes migration-list inaccuracies (registry credentials were never plaintext, unlike node API tokens), rephrases the SSH/TLS and JSON-config migration bullets to drop version-numbered legacy framing, adds a GHCR mirror note matching the quickstart pattern, and cross-links the Hardened Build entitlement-gated update path so digest-pinned installs aren't sent down the manual docker pull steps. * docs: refresh Backup & Restore against current backend Broadens the encryption.key warning to cover everything CryptoService actually encrypts (node tokens, Git source and Fleet Secrets, SSO/MFA, Recovery Vault, fleet snapshot contents), not just registry credentials. Adds the built-in backupData CLI as a no-host-tooling alternative to the sqlite3 .backup command, cross-linked to Emergency command-line recovery. Corrects node-token migration guidance: tokens are signed with a secret stored in sencho.db and remain valid after a host move, so no regeneration is required. * docs: refresh Recovery guide against current Settings page and CLI Documents the Settings · Recovery page's full System health / Environment / Safe actions / Command-line hub instead of only its environment-preflight section, adds the missing "Sencho compose location" preflight check, adds the SSO/OIDC/LDAP lockout scenario now that disableSso.js exists, and corrects the rollback description (exact UI label, backup-required and image-layer caveats). * docs(emergency-cli): sync in-app page description, add CLI operational details Aligns the "in-app Recovery page" summary with the freshly refreshed Recovery guide (System health / Environment / Safe actions / Command-line recovery, SSO providers, one-click command download). Adds constraints verified against the CLI source: password/username minimums, the valid SSO provider identifiers with an example, and a note that diagnostics.js always reports Docker as unreachable (it runs without a live Docker connection, unlike the in-app page). * docs(troubleshooting): refresh against current backend and nav Corrects several claims that had drifted from the implementation: network name validation (underscore is not a valid leading character), the remote-update delayed-failure window (3 minutes, not 90 seconds), and an unsubstantiated version-compatibility check on the Admiral 403 entry. Removes two entries describing legacy pre-v0.39 node behavior that no longer applies to any currently shipped build. Replaces stale "Profile > Settings > X" navigation with the current Settings hub paths, and "wifi icon" with the current Test Connection label. Adds Pilot Agent awareness to the remote-offline entry with a cross-link to its dedicated troubleshooting section, and trims the docker-run converter entry to point at the fuller, already-current version on the Stack Management page instead of duplicating it with a broken anchor. * docs(verifying-images): document the :dev GHCR integration tag Verified the existing cosign/SBOM/VEX/tag-policy content against docker-publish.yml and docker-preview.yml; all accurate. Added the previously undocumented :dev/:dev-<sha> integration tag published on every push to main via docker-dev.yml. * docs(trivy-setup): sync install guide with node-scoped scanner and current Trivy upstream docs Documents that Trivy installs independently per node, adds the TRIVY_BIN override and non-PATH mounting option, fixes the deprecated apt-key install flow and RHEL repo gpgkey placement, notes the Exploit intelligence toggle for air-gapped hosts, and replaces the stale Scanner setup screenshot. * docs(two-factor-admin): document lockout recovery and self-reset gotcha Verified the reset flow, CLI recovery, and SSO toggle claims against current source and replaced the stale admin-reset modal screenshot. Added the failed-attempt lockout behavior (undocumented despite being promised in the page description) and a warning about resetting your own 2FA from the Users list, which signs you out immediately unlike the self-service disable flow. * fix(docs): make Settings and Self-hosting discoverable in the sidebar The Reference and Operations groups used root pages that were only reachable by clicking the ambiguous group label, and that click also triggered an unwanted double action (expand plus navigate). List both pages as explicit sidebar entries and disable global drilldown so group headers only expand or collapse. * docs(settings): sync reference page with current Settings Hub Renamed License to Admiral Account throughout (Hardened Build channel switch, image channel display, DURATION pill), corrected the password policy, documented the new Appearance navigation and log-chip-color controls plus font options, noted Mesh data plane is not on every installation, fixed the label cap (50, not 100), and replaced every screenshot with a fresh capture from the production node. * fix(docs): apply the sidebar toggle-only fix to Start here and Product guide These two groups had the same click-to-navigate-and-expand pattern as Reference and Operations. Flattening them is safe here too: the Product guide root page has no directory listing depending on it, and the Start here root page's own hand-authored Next steps CardGroup already covers the same links the auto-generated listing duplicated. * docs(licensing): refresh licensing page for Hardened Build and sales-led Admiral pricing Admiral pricing moved from self-serve checkout to a contact-sales model, and a new Hardened Build image-channel switcher shipped in the Admiral Account settings page; neither was reflected in the docs. Also documents the lifetime-license edge case (no Manage subscription button, no Billing row) and refreshes all four screenshots against the current UI. * docs(security): sync reference page with current API-token and encryption scope Verified every claim against the live implementation: the API-token universal restrictions list was missing MFA management, Recovery Vault, and image channel management; the encryption-at-rest field list was missing Recovery Vault credentials; added a note on the password strength indicator's recommended-vs-enforced distinction. Refreshed the SSO settings, API tokens, and audit log screenshots against the production node. * docs(settings): fix password policy and session-invalidation claims Cross-checked against auth.ts while verifying the same claims on the security reference page: the enforced minimum is 8 characters (the 12+/mixed-case/number text is a frontend strength hint, not a validated rule), and a password change invalidates every other session for the account rather than leaving them valid. * docs(contact): sync contact channels with sales-led pricing and current support gating Replace the retired contact@sencho.io with hello@sencho.io (the address actually used in the website footer and the pricing page's Get in touch CTA), narrow the licensing@sencho.io scope to existing-license activation/billing/refunds now that new Admiral conversations route through hello@sencho.io, drop the stale LICENSE-file and in-app upgrade-prompt claims (the AGPLv3 relicense removed both), correct the Support settings path and add the published response-time targets, and remove the unsubstantiated bug bounty mention.	2026-07-21 09:13:12 -04:00
Anso	63213c0960	feat: add service-scoped Compose update and restore (#1648) ... * feat: add service-scoped Compose update and restore Allow updating or rebuilding one declared Compose service on multi-service stacks without recreating siblings, with recovery snapshots, health-gate observation, and prune holds for rollback images. Full-stack update paths and single-service UX stay unchanged. * fix: sanitize service-scoped update log messages for CodeQL * fix: address service-scoped update audit findings B-01 through B-07 * fix: complete service-scoped update audit metadata and surfaces * test: wrap Updates readiness tests for deploy-feedback context * fix: keep service recovery reachable without Deploy Progress Make failed service-gate recovery discoverable when Deploy Progress is disabled or dismissed, suppress stale image-scan notification side effects, normalize ComposeService line endings, and add focused regression coverage. * fix: resurface ContainersHealth density and expand on multi-service stacks Service grouping hid the summary strip and Compact/Detailed/Expand controls that still applied to multi-container stacks.	2026-07-19 02:42:29 -04:00
Anso	ad71a281a3	docs: reorganize documentation navigation (#1606)	2026-07-09 14:31:55 -04:00
Anso	9ff678a7bb	docs: v1 docs refresh (batch 5) (#1395) ... * docs(introduction): refresh for the redesigned UI and replace screenshots Bring the Getting Started Introduction page in line with the current product: - Add the Security top-level view to the navigation list and a dedicated Security section with a new screenshot. - Correct the Fleet tab names (Snapshots, Status, Map, Deployments, Routing, Federation, Actions, Secrets). - Split Settings out from security and list the current nine setting groups (Security graduated to its own view). - Refine the navigation paragraph so role, tier, and local-vs-remote context read accurately. Replace all four existing screenshots (Home, stack workspace, Fleet, Resources) with fresh captures of the redesigned UI and add a Security overview screenshot. * docs(configuration): document advanced env vars and clarify deployment vs runtime config Add an Advanced environment variables section (TRIVY_BIN, SENCHO_MESH_SUBNET, GITSOURCE_MAX_CLONE_BYTES, SENCHO_PUBLIC_URL, SENCHO_COMPOSE_STALL_TIMEOUT_MS) and reframe the intro to separate deployment-time configuration from the runtime settings that live in the in-app Settings Hub. Cross-link the pilot-agent variables to the Pilot Agent page instead of duplicating them. * docs(sso): refresh SSO Setup Guide and SSO & LDAP reference for the redesigned UI Refresh both SSO documentation pages against the current product and the redesigned settings UI. - Correct the navigation path to Settings -> Access -> SSO on both pages. - Fix the "Require 2FA on SSO sign-in" toggle location to Settings -> Personal -> Account. - Describe the login-page experience (the Local / LDAP toggle and the branded OIDC buttons under the "Or continue with" divider) and the SSO panel masthead (SCOPE, PROVIDERS, ENABLED). - Replace all six SSO screenshots with fresh captures of the redesigned UI. * docs(features): refresh the Features Overview page for the redesigned UI Rewrite docs/features/overview.mdx to mirror the current Features navigation grouping (Stacks, Deployment, Resources, Observability, Fleet, Automation, Security & Identity) and add the recently shipped capabilities surfaced in the redesign: Stack Dossier, Drift Detection, Compose Doctor, Compose Networking, Environment & secrets guardrails, Storage portability, Health-Gated Updates, Fleet Dossier, and the dedicated Security page. Correct stale claims (the file explorer now gates writes on stack edit permission, not an admin role; downloads are a read action; bulk label assign now spans nodes) and standardize the tier callouts so partly paid features read as "Admiral adds X". Replace the three pre-redesign screenshots and add a Security overview banner, all captured from a populated fleet. * docs(features): refresh the Appearance page for the redesigned UI Add fresh screenshots and a troubleshooting section to the Appearance page, verified against the live product. - Add four screenshots: the Theme card (live preview, mode, accent, and fine-tune sliders), the top-bar quick switcher, the Typography card, and the Display card. - Refresh the Density screenshot used by the Settings reference page. - State that the quick switcher also covers text size, and that the contrast, border, and glow sliders stay in Settings. - Add a Troubleshooting accordion covering per-browser persistence, resets to defaults, cross-operator scope, and the quick-switcher versus full-Settings split. * docs(introduction): refresh screenshots and correct stale content * docs(reference): refresh the Settings Reference page for the redesigned UI Replace all seven stale screenshots with fresh 1920x1080 captures. Add five new screenshots for the sections that previously had none. Content changes: - Sidebar table: rename Infrastructure "Fleet Mesh" entry to "Fleet"; add "Image update checks" to the Automation group list - Fleet section: rename heading to match registry label; add the Documentation snapshots subsection (snapshot_documentation toggle) - Container Alerts: add screenshot - Image update checks: add the full section (Registry checks table, scheduling mode, interval presets, cron expression support) - Stacks / Deploy Guardrails: add screenshot - Recovery: add the full section (System health snapshot, Environment preflight checks, Safe actions, Command-line recovery table) * docs(sso): refresh screenshots for SSO quickstart and feature pages * docs: refresh Features Overview screenshots and content Replace all 4 hero screenshots with fresh 1920x1080 production captures. Correct security posture state names (Action needed / Monitoring / Secure), add the Policies tab to the Security section tab list, mention the Simple mode in Scheduled operations, and update all alt text to match the new screenshots. * docs: refresh Appearance page screenshots and correct quick-switcher scope Replace all four Appearance screenshots with fresh production captures. Fix the quick-switcher control list: remove fonts (not present in the popover), add visual style and readability which are. Add Log chip color to the Display section. Update all screenshot alt text to match new captures. * docs: refresh stack management page with current UI and anatomy tabs * docs: fix convert-tab-error screenshot with fully visible error toast * docs: convert troubleshooting section to AccordionGroup format * docs(quickstart): refresh screenshots and align dashboard description Replace all three first-boot and dashboard screenshots with current UI. Add Security to the top navigation list, update gauge and Stack health descriptions to reflect sparklines and column detail, and align Configuration Status wording with the Introduction page. * docs(editor): rewrite anatomy panel, replace all screenshots - Correct the anatomy panel tab inventory: the panel has eight tabs (Anatomy, Activity, Dossier, Drift always; Environment, Networking, Doctor, Storage when the node advertises the matching capability), not three as previously documented - Add table describing all eight tabs with capability gates and links to dedicated feature pages - Add anatomy-tabs.png screenshot showing the scrollable tab row - Note the Doctor severity dot (red for blocker, amber for high-risk) - Remove the stale Markdown-export subsection; Dossier and Activity are now covered in the tab table - Replace all six stale screenshots with fresh 1920x1080 captures - Replace the compose diff preview screenshot * docs(files): refresh Files & Volumes screenshots and fix context-menu alt text Replace all 9 stale screenshots on the Files & Volumes page with fresh captures from the production node. Fix three alt-text strings that did not match the live UI: removed hardcoded octal value 644, and added the Duplicate, Copy to, and Move to entries missing from the context-menu alt text. * docs: rewrite Stack Activity page with full event categories and fresh screenshots Expands the event category table from 5 to 10 entries to cover drift detected, drift resolved, update started, health gate passed, and health gate failed. Adds a live-disconnected-state section, a background-actor attribution table, and a corrected troubleshooting accordion covering the WebSocket reconnect case. Replaces both stale screenshots with fresh 1920x1080 captures from the production node. * docs(drift): rewrite drift detection page with screenshots and full coverage Full rewrite of the Drift Detection feature page. Adds two previously undocumented finding types (network-undeclared, network-missing), expands the temporal section to distinguish the raw-file hash from the parsed-model hash, documents the two-layer spatial-engine and ledger architecture, explains when the ledger is reconciled (post-deploy vs manual re-check vs tab open), adds Activity timeline integration note, introduces a Limitations section (no background scanner, port-range caveat, history cap, advisory-only enforcement), expands Troubleshooting from five entries to seven using the AccordionGroup convention, and adds four production screenshots. * docs(drift): use CardGroup for Related section * docs(dossier): rewrite Stack Dossier page with full feature coverage * docs(networking): rewrite Compose Networking page with full feature coverage * docs(doctor): rewrite Compose Doctor with full 30-rule reference, screenshots, and cross-links * docs(networking): add production screenshots and correct alt text Adds 7 production screenshots for all sections of the Compose Networking page and updates the four placeholder alt texts written before screenshots were taken to match what the actual images show (arr-net external badge, swag service with 443/tcp and 80/tcp, single-service exposure intent row). Also adds the full-panel overview image at the top of the page. * docs(environment-guardrails): rewrite with project env file, env file status, and screenshots * docs(storage): rewrite Storage Portability page with screenshots and full coverage Rewrites compose-storage.mdx from a 61-line sketch into a complete reference page. Key additions: Where to find it section with screenshot, full storage inventory section documenting all mount type/access/status chips and the Linux owner display, expanded portability verdict section with per-reason detail and edge-case caveats (read-only binds, symlink escapes, anonymous volume risks), snapshot coverage section with admin scope and remote-node behavior, Findings in Doctor cross-reference, and six troubleshooting accordions covering tab visibility, bind status, external named volumes, render errors, and snapshot coverage states. Adds two production screenshots: storage-tab.png and storage-node-bound.png. * docs(stack-labels): rewrite with accurate permissions, capability gate, dry run, live preview, and color conflict docs * docs: rewrite Stack Sidebar page with accurate feature coverage Rewrites the Stack Sidebar documentation page to match the current UI. Key changes: - Fix branding header description (shows logo + version, not just version) - Fix bulk mode icon description (stacked-rows, not square) - Add cross-node search section (fan-out behavior, Other nodes section, unreachable-node warnings, click-to-switch navigation) - Update Labels submenu description (inline New label creation, Manage labels link) - Note that Delete only appears when the user has delete permission - Remove the auto-update implication from Schedule task description - Rewrite the Activity ticker section with the full 6-state priority cascade table; remove the non-existent IDLE state; correct pulsing-dot behavior - Replace all 7 stale screenshots with fresh production screenshots - Add new sidebar-cross-node-search.png screenshot * docs(atomic-deployments): refresh screenshot and document project env files, rollback readiness, and recovery actions * docs(atomic-deployments): fix rollback permission visibility and banner string accuracy The Rollback menu entry is hidden by the frontend when the user lacks stack:deploy; it never appears and does not 403. Fixed the step-4 narrative and troubleshooting accordion to match. The rollback-failure banner emitted by ComposeService is '=== Rollback failed. Manual intervention may be required ===' (period, capital M). Fixed both occurrences in the page. Updated the Settings navigation path from the nonexistent 'Roles & Access' to the real 'Access'. * docs(deploy-progress): rewrite with health gate, inline style, and 9 fresh screenshots Add health gate section covering all four states (observing, passed, failed, unknown) with exact UI banner text and the configurable observation window. Expand the inline style section with full band content, 4s auto-dismiss, and pill handoff. Add Scanning as a supported entry point. Replace all 6 existing screenshots and add 3 new ones (modal-health-gate, inline-banner, setting-style). Add two health gate troubleshooting accordions. Add Related CardGroup linking to health-gated-updates, stack-activity, deploy-enforcement, and atomic-deployments. * docs(health-gated-updates): refresh screenshots and correct signal row order and label * docs(deploy-enforcement): rewrite with fleet replication, honor suppressions location, scan-failed dialog state, and fresh screenshots Adds the Fleet policy replication section covering control/replica behavior, Managed by control node banner, and Demote to control. Documents the exact location of the Honor suppressions toggle (bottom of Policies tab). Expands the block dialog section with the scan-failed row state. Updates all three screenshots to the current visual design. Restores the Admiral license note and corrects the policy-card scope description. * docs(app-store): rewrite with mobile layout, fresh screenshots, and registry admin note - Replace all 5 stale screenshots with 1920x1080 production captures - Add app-store-mobile.png showing the status masthead layout - Document mobile single-column layout in a new Mobile subsection - Note that the featured hero has its own Deploy button - Mark the category rail as desktop only with a cross-link to Mobile - Add admin-account requirement to the custom registry section - Add Related CardGroup linking vulnerability scanning, deploy progress, deploy enforcement, and resources	2026-06-29 01:29:03 -04:00
Anso	e9c262ae6a	feat: split Host Alerts into Host Alerts, Container Alerts, and Stacks guardrails (#1461) ... * feat: split Host Alerts into Host Alerts, Container Alerts, and Stacks guardrails Move global_crash from Host Alerts to new Monitoring > Container Alerts section. Move health gate and env deploy guardrails from Host Alerts to Infrastructure > Stacks > Deploy Guardrails subsection. Host Alerts now contains only host threshold settings (CPU, RAM, disk, alert suppression, and the master host_alerts_enabled toggle). Stacks gains a Deploy Guardrails subsection (node-scoped, admin-gated) alongside the existing Workflow controls (browser-local). Dashboard Crash detection row now routes to Container Alerts. * docs: update crash detection toggle description to match new Container Alerts section	2026-06-25 21:04:55 -04:00
Anso	38aabe7064	feat: health-gated updates and rollback readiness (#1354) ... * feat: classify stack deploy and update failures with suggested next actions Failed deploy and update responses now carry a failure classification (cause category, headline, and suggested next step) derived from the compose error output. The recovery panel and chip render the classification and include it in copied diagnostics, and gateway-style failures surface as a node-unreachable cause. * feat: add update and rollback readiness reports for stacks Before a manual update, Sencho now shows an advisory readiness verdict computed from the stored preflight result, open drift findings, live container health, the pending image change, the rollback backup slot, and node disk headroom. The Stack Dossier gains a rollback readiness section that states what a rollback can restore and explicitly discloses that volume and bind-mounted data are not covered. Toolbar and sidebar updates now share one update path, and admins can create a fleet snapshot from the readiness dialog before updating. Nodes that do not advertise the capability keep the direct update flow. * feat: observe stack health after updates with a post-deploy health gate After a deploy or update succeeds, Sencho now watches the stack for a configurable observation window and records a passed, failed, or unknown verdict: containers must stay running, healthchecks must report healthy, and restart loops or disappearing containers fail the gate. The deploy panel shows the observation live and holds off auto-closing until the verdict lands, a failed gate surfaces the existing recovery actions including rollback, and the stack timeline records update started and gate verdict events. Scheduled, webhook, bulk, and git-source updates are gated the same way; rollbacks and installs are deliberately not. The gate is observational only and can be tuned or disabled per node under host alert settings. * docs: document health-gated updates and rollback readiness New operator page covering the update readiness dialog, the post-update health gate and its settings, the rollback readiness disclosure, and classified failures, with cross-links from the atomic deployments and deploy progress pages. The API reference gains the readiness and health-gate endpoints, the healthGateId success field, and the failure classification schema on deploy and update error responses. * feat: withhold the success verdict while the health gate observes An update used to show a green Succeeded that a failed health gate then contradicted moments later. The deploy modal now reports Verifying health while the gate observes, shows success only when the gate passes, and makes a failed or unknown gate the headline result; success toasts soften to a verifying message while a gate runs. The mobile recovery card groups its actions behind one bottom-right Take action menu so it stays compact on a phone, with the classified cause still visible on the card. A successful image update now also counts as the last known-good marker in rollback readiness, and the docs gain screenshots of the readiness dialog, gate states, dossier section, and settings. * fix: harden log format strings and the env existence path check Log calls that interpolated the stack name into the console format string now use constant format strings with placeholder arguments, and envExists validates path containment inline at its filesystem access, matching the established patterns used elsewhere in the same files. * test: adapt deploy modal success specs to the post-deploy health gate The deploy feedback modal now withholds its success verdict while the health gate observes the new containers, showing "Verifying health" until the gate passes. The two success-path E2E tests waited for "Succeeded" within the gate's 90s default window and timed out. Shorten the observation window to the 15s minimum for these tests via the settings API, assert the verify-then-succeed sequence the modal actually renders, and restore the default window afterward so the test value does not leak into later runs. * fix: serialize health gate polling and harden gate observation Address race conditions in the post-update health gate found in review. Backend: the gate poller used setInterval, so a Docker observe slower than the 5s tick could overlap the next poll and corrupt the restart and missing-container accounting, and a wedged socket could leave a poll pending forever. Polling is now single-flight: each cycle self-schedules the next only after it settles, and the observe is bounded by an 8s timeout so a hung probe counts as a poll error and resolves the gate unknown after three in a row. Frontend: the gate poller could overlap requests, letting a slow earlier "observing" response overwrite an already-applied terminal verdict. It is now single-flight with a terminal latch, so a late response can never roll the UI back from passed or failed. Also reject a non-digit nodeId on the snapshot coverage route instead of letting parseInt coerce it, document that turning off the deploy progress panel opts out of the live gate UI while the gate still runs server-side, and add gate-coverage tests for the webhook, git source, and auto-update apply paths plus the new single-flight, observe-timeout, and recovery cases.	2026-06-11 00:26:26 -04:00