Configure swap file and update sysctl settings

[lionello]

Summary

Add swap configuration and adjust system settings. Without it, the nodes quickly reach 99% mem use.

Validation

• pnpm lint
• pnpm typecheck
• pnpm test
• Additional validation run (if applicable)

Staging Verification (REQUIRED for all code changes — merge-blocking)

All checkboxes below are mandatory for any PR that changes runtime code (.ts, .tsx, .go, etc.). Write N/A: docs-only ONLY if the PR contains zero runtime code changes. See .claude/rules/13-staging-verification.md.

• Staging deployment green — Deploy Staging workflow triggered manually and passed for this branch
• Live app verified via Playwright — logged into app.sammy.party (staging) using test credentials and actively tested the application
• Existing workflows confirmed working — navigated dashboard, projects, and settings; confirmed no regressions in core flows (pages load, data displays, navigation works, no new console errors)
• New feature/fix verified on staging — the specific changes in this PR work correctly on the live staging environment (describe what was tested below)
• Infrastructure verification completed — VM provisioned and heartbeat confirmed (required for changes to cloud-init, VM agent, DNS, TLS, scripts/deploy). Write N/A: no infra changes ONLY if the PR does not touch any infrastructure paths.
• Mobile and desktop verification notes added for UI changes

Staging Verification Evidence

UI Compliance Checklist (Required for UI changes)

• Mobile-first layout verified
• Accessibility checks completed
• Shared UI components used or exception documented
• Playwright visual audit run locally — mock data scenarios (normal, long text, empty, many items, error, special chars) tested at mobile (375x667) and desktop (1280x800); no horizontal overflow; screenshots in .codex/tmp/playwright-screenshots/ (see .claude/rules/17-ui-visual-testing.md)

End-to-End Verification (Required for multi-component changes)

• Data flow traced from user input to final outcome with code path citations (see .claude/rules/10-e2e-verification.md)
• Capability test exercises the complete happy path across system boundaries
• All spec/doc assumptions about existing behavior verified against code (not just "read the code")
• If any gap exists between automated test coverage and full E2E, manual verification steps documented below

Data Flow Trace

Untested Gaps

Post-Mortem (Required for bug fix PRs)

What broke

Root cause

Class of bug

Why it wasn't caught

Process fix included in this PR

Post-mortem file

Specialist Review Evidence (Required for agent-authored PRs)

If review agents were dispatched during Phase 5, list every reviewer below. Do NOT merge until every row shows PASS or ADDRESSED. If any reviewer could not complete (timeout, workspace killed, error), you MUST add the needs-human-review label and stop — do not self-merge. See .claude/rules/25-review-merge-gate.md.

• All dispatched reviewers completed and findings addressed before merge
• If any reviewer did NOT complete: needs-human-review label added and merge deferred to human

Reviewer	Status	Outcome

Exceptions (If any)

• Scope:
• Rationale:
• Expiration:

Agent Preflight (Required)

• Preflight completed before code changes

Classification

• external-api-change
• cross-component-change
• business-logic-change
• public-surface-change
• docs-sync-change
• security-sensitive-change
• ui-change
• infra-change

External References

Provide sources consulted before coding. For external-api-change, include Context7 output or official docs.
If not applicable, write N/A: <reason>.

Codebase Impact Analysis

List affected components and code paths (for example apps/api, packages/shared, packages/vm-agent).
If not applicable, write N/A: <reason>.

Documentation & Specs

List docs/spec files updated, or write N/A: <reason for no updates>.

Constitution & Risk Check

State which constitution principles were checked and summarize key risks/tradeoffs.