arkaos 2.15.0 → 2.16.0

package/arka/skills/platform-arka/references/workflows.md

@@ -0,0 +1,202 @@
+# arka-platform-arka — Full Orchestration Workflows
+
+Referenced from SKILL.md. Read only when executing the relevant flow.
+
+## Standard Flow (feature, fix, docs)
+
+```
+1. Context Loading
+   - Read CLAUDE.md, VERSION, package.json, pyproject.toml
+   - Load recent git history (git log --oneline -20)
+   - Check current test status (pytest --tb=no -q)
+
+2. Analysis & Planning
+   - Product Owner assesses scope and priority
+   - Skill Architect identifies affected areas (core/installer/dashboard/skills)
+   - Assign appropriate engineer(s) based on affected layers
+
+3. Plan Presentation & Approval
+   - Present plan: affected files, squad roles, scope estimate
+   - User approves before any code execution
+
+4. Execution
+   - Features/evolve: branch (feature/* or evolve/*) + worktree isolation
+   - Hotfixes/patches: direct on master
+   - Squad agents execute in their domain
+   - QA Engineer runs tests after changes
+
+5. Quality Gate
+   - Marta (CQO) orchestrates review
+   - Eduardo (Copy) reviews all text output
+   - Francisca (Tech) reviews all code
+   - APPROVED or REJECTED — no exceptions
+
+6. Documentation
+   - Update Obsidian at WizardingCode Internal/ArkaOS/
+```
+
+## Release Flow
+
+```
+1. Pre-flight
+   - Run full test suite: cd /Users/andreagroferreira/AIProjects/arka-os && python -m pytest tests/ --tb=short -q
+   - Check git status (must be clean working tree)
+   - Review changes since last release: git log $(git describe --tags --abbrev=0)..HEAD --oneline
+
+2. Preparation
+   - Determine version bump type (patch/minor/major) from changes
+   - Update VERSION, package.json version, pyproject.toml version
+   - Generate changelog from conventional commits
+   - Commit: git commit -m "chore: bump to vX.Y.Z"
+
+3. Confirmation Gate (PAUSE)
+   - Present to user: new version number, changelog summary, files changed count
+   - WAIT for explicit user confirmation before proceeding
+   - If user declines: revert bump commit, stop
+
+4. Publish (only after user confirms)
+   - git push origin master
+   - gh release create vX.Y.Z --title "vX.Y.Z" --notes "<changelog>"
+   - npm publish:
+     ```bash
+     # Method 1: Direct (if ~/.npmrc has valid publish token)
+     npm publish --access public
+
+     # Method 2: Temp config (if Method 1 fails with 403)
+     TMPRC=$(mktemp)
+     echo "//registry.npmjs.org/:_authToken=<TOKEN>" > "$TMPRC"
+     npm publish --access public --userconfig "$TMPRC"
+     rm -f "$TMPRC"
+     ```
+   - Verify: npm view arkaos version (must show new version)
+   - npm account: wizardingcode | Package: arkaos | Access: public
+
+5. Post-release
+   - Save release notes to Obsidian: WizardingCode Internal/ArkaOS/Releases/vX.Y.Z.md
+   - Update metrics snapshot
+```
+
+## Audit Flow
+
+```
+1. Platform Analyst scans the codebase:
+
+   a. Department completeness:
+      - List all departments/ subdirectories
+      - Check each has: agents/*.yaml, skills/*/SKILL.md, workflows/*.yaml
+      - Flag departments missing any component
+
+   b. Agent validation:
+      - Parse all departments/*/agents/*.yaml
+      - Verify 4-framework behavioral DNA (DISC, Enneagram, Big Five, MBTI)
+      - Flag agents with incomplete profiles
+
+   c. Skill coverage:
+      - List all ~/.claude/skills/arka-*/SKILL.md
+      - Cross-reference with department command tables
+      - Flag commands without corresponding skills
+
+   d. Test coverage:
+      - Run: python -m pytest tests/ --tb=no -q
+      - Count test files vs source files
+      - Flag untested modules
+
+   e. Code quality:
+      - Check for unused imports, dead code patterns
+      - Verify CLAUDE.md accuracy against actual file structure
+      - Check VERSION consistency across package.json, pyproject.toml, VERSION
+
+2. Present findings ranked by impact (high/medium/low)
+3. Save audit report to Obsidian: WizardingCode Internal/ArkaOS/Audits/YYYY-MM-DD.md
+```
+
+## Evolve Flow
+
+```
+1. Run audit (automatic first step — reuse audit flow above)
+
+2. Proposal
+   - Filter audit findings to actionable improvements
+   - Rank by impact and effort (quick wins first)
+   - Present top 5 proposals with:
+     - What: description of the improvement
+     - Why: impact on ArkaOS quality/completeness
+     - How: which squad member(s) implement it
+     - Effort: small/medium/large
+   - User selects which proposals to implement
+
+3. Implementation
+   - Create branch: evolve/YYYY-MM-DD-<description>
+   - Use worktree isolation
+   - Each improvement as a separate commit with conventional commit message
+   - QA Engineer runs tests after each change
+
+4. Quality Gate
+   - Marta (CQO) orchestrates final review
+   - Eduardo (Copy) reviews any text changes
+   - Francisca (Tech) reviews any code changes
+   - APPROVED → merge to master
+   - REJECTED → fix and re-submit
+```
+
+## Status Command
+
+```
+1. Read current version from VERSION file
+2. Run: python -m pytest tests/ --tb=no -q (capture pass/fail/total)
+3. Run: git log --oneline -10 (recent activity)
+4. Run: git describe --tags --abbrev=0 (latest release tag)
+5. Count: departments, agents, skills, tests
+6. Present formatted status:
+
+   === ArkaOS Platform Status ===
+   Version: X.Y.Z
+   Latest Release: vX.Y.Z (YYYY-MM-DD)
+   Tests: X passed / Y total
+   Departments: 17 | Agents: 65 | Skills: 244+
+   Recent commits: [last 5]
+   Reports to: /wiz (WizardingCode Internal)
+   ==============================
+```
+
+## Metrics Command
+
+```
+1. Count files:
+   - departments/*/agents/*.yaml → agent count
+   - ~/.claude/skills/arka-*/SKILL.md → skill count
+   - departments/ subdirectories → department count
+   - tests/python/ test files → test count
+
+2. Check completeness:
+   - Departments with all 3 components (agents, skills, workflows)
+   - Agents with full 4-framework DNA
+
+3. Version history:
+   - git tag --sort=-version:refname | head -10
+
+4. Present formatted metrics dashboard
+```
+
+## Skill Create Command
+
+```
+1. Ask for skill name and target department
+2. Create directory: ~/.claude/skills/arka-<name>/
+3. Scaffold SKILL.md with:
+   - YAML frontmatter (name, description)
+   - Command table template
+   - Squad roles section
+   - Orchestration workflow template
+4. Inform user to register in settings.json if needed
+```
+
+## Agent Create Command
+
+```
+1. Ask for agent name, department, and role
+2. Scaffold YAML file at departments/<dept>/agents/<name>.yaml with:
+   - Basic identity (name, role, department)
+   - 4-framework DNA template (DISC, Enneagram, Big Five, MBTI) with placeholders
+3. Run agent validate to check consistency
+```

package/arka/skills/rothbard100/SKILL.md

@@ -0,0 +1,113 @@
+---
+name: arka-rothbard100
+description: >
+  Rothbard 100 ecosystem orchestrator. Dedicated command for all Rothbard 100 event work.
+  Routes tasks to specialized squad roles (PM, frontend developer, content creator,
+  SEO/marketing, security engineer, QA tester, DevOps). Presents execution plans for
+  approval before proceeding. Currently manages 1 project: rothbard100-landing (Nuxt 4
+  landing page for libertarian event celebrating Murray Rothbard's centenary, Porto, 27 Jun 2026).
+  Organized by Cataláxia EDITORA. Hosted on Cloudflare Pages.
+  Use when user says "rothbard100", "rothbard", or wants to work on any Rothbard 100 project.
+---
+
+# Rothbard 100 Ecosystem Orchestrator — ARKA OS
+
+Dedicated orchestrator for all Rothbard 100 event platform work. The Rothbard 100 is a libertarian event celebrating the 100th anniversary of Murray Rothbard, organized by Cataláxia EDITORA.
+
+## Ecosystem Overview
+
+| Project | Type | Stack | Path |
+|---------|------|-------|------|
+| **rothbard100-landing** | Landing Page (SSG) | Nuxt 4.4.2 + Nuxt UI v4.5.1 + Tailwind CSS 4 + TypeScript | `/Users/andreagroferreira/Work/rothbard100-landing` |
+
+### Event Details
+
+| Property | Value |
+|----------|-------|
+| Date | 27 Junho 2026, 09:00 (GMT+1) |
+| Location | Porto, Portugal |
+| Organizer | Cataláxia EDITORA |
+| Contact | parcerias@rothbard100.pt |
+
+### Future Projects (Planned)
+
+| Project | Type | Status |
+|---------|------|--------|
+| rothbard100-registration | Registration App | planned |
+| rothbard100-crm | Event CRM | planned |
+
+## Commands
+
+| Command | Description |
+|---------|-------------|
+| `/rothbard100 <description>` | Describe what you need — orchestrator analyzes, plans, and routes |
+| `/rothbard100 status` | Status of all Rothbard 100 projects |
+| `/rothbard100 plan <description>` | Plan only (no code) |
+| `/rothbard100 feature <description>` | Implement a feature |
+| `/rothbard100 debug <issue>` | Debug an issue |
+| `/rothbard100 review` | Code review |
+| `/rothbard100 test` | Run tests |
+| `/rothbard100 deploy <env>` | Deploy |
+| `/rothbard100 content <description>` | Create/update landing page copy and content |
+| `/rothbard100 seo` | SEO audit and optimization |
+| `/rothbard100 docs` | Update Obsidian documentation |
+| `/rothbard100 context` | Show full ecosystem context |
+| `/rothbard100 scaffold <name>` | Scaffold a new project into the ecosystem |
+
+## Squad (Compact)
+
+| Role | Agent Type | Specialty |
+|------|-----------|-----------|
+| Project Manager | `tech-lead` | Sprint planning, task breakdown, plan presentation |
+| Frontend Developer | `frontend-dev` | Nuxt 4, Vue 3, TypeScript, Tailwind CSS 4, Nuxt UI 4 |
+| Content Creator | `content-marketer` | Copy, messaging, event storytelling |
+| SEO/Marketing | `cro-specialist` | Landing page optimization, conversion, meta tags |
+| Security Engineer | `security-eng` | XSS, CSP, form validation, data protection |
+| QA Tester | `qa-eng` | Vitest, Playwright, responsive testing, performance |
+| DevOps | `devops-eng` | Cloudflare Pages deployment, CI/CD, CDN |
+
+Full squad routing details: see `references/squad.md`.
+
+## Brand Identity
+
+| Property | Value |
+|----------|-------|
+| Primary Color | `#FFC939` (gold / amber) |
+| Secondary Color | `#000000` (black) |
+| Theme | Dark, premium, revolutionary |
+| Font | Inter (400–900) |
+| Mode | Light only (forced via colorMode) |
+| Tone | Bold, intellectual, freedom-focused |
+
+## Constitution (NON-NEGOTIABLE)
+
+| Rule | Enforcement |
+|------|-------------|
+| `branch-isolation` | Feature branches or worktrees, never direct on main |
+| `spec-driven` | Spec before implementation (features, APIs, components) |
+| `solid-clean-code` | SOLID + Clean Code on all code |
+| `mandatory-qa` | Build must pass. Tests where applicable. |
+| `quality-gate` | Marta + Eduardo + Francisca APPROVE before delivery |
+| `conventional-commits` | feat:, fix:, etc. |
+| `no-mechanical-copy` | Content Creator adapts — never copy-paste user text |
+| `self-critique` | Self-critique phase before presenting |
+| `auto-deploy` | Push to main triggers Cloudflare Pages. Never manual deploy. |
+
+## Complexity Routing
+
+| Tier | Examples | Workflow |
+|------|----------|----------|
+| Quick | Status check, typo fix, single config | Direct execution |
+| Standard | Content update, SEO change, component, bug fix | Standard Workflow (8 phases) |
+| Complex | New feature, architecture change, multi-locale overhaul | Forge → Standard Workflow |
+
+Complex tasks invoke `/arka-forge` first for multi-perspective planning before execution.
+
+## References
+
+- `references/workflows.md` — 8-phase orchestration workflow, status/content/seo/context/scaffold flows, execution report templates
+- `references/squad.md` — Full squad routing details, architectural notes, components, tech stack, conventions, Obsidian output
+
+## Obsidian Output
+
+All documentation: `/Users/andreagroferreira/Documents/Personal/Projects/Rothbard100/`

package/arka/skills/rothbard100/references/squad.md

@@ -0,0 +1,111 @@
+# arka-rothbard100 — squad
+
+Referenced from SKILL.md. Read only when needed.
+
+## Architecture
+
+```
+Visitors --> rothbard100-landing (Nuxt 4, SSG via Nitro)
+                   |
+                   +-- @nuxtjs/i18n (5 locales: pt default, en, fr, es, de)
+                   +-- @nuxt/image v2 (optimized images)
+                   +-- @nuxt/ui v4.5.1 (component library)
+                   +-- Iconify (lucide + simple-icons)
+                   +-- Supabase (registration form submissions)
+                   +-- Google Tag Manager + Microsoft Clarity (analytics)
+                   +-- JSON-LD structured data + llms.txt (SEO/GEO/AEO)
+                   +-- Cloudflare Pages (hosting, auto-deploy from main)
+```
+
+## Squad Roles (Full)
+
+When processing any `/rothbard100` request, assign work to the appropriate squad members:
+
+| Role | Agent Type | Specialty |
+|------|-----------|-----------|
+| **Project Manager** | `tech-lead` | Sprint planning, task breakdown, plan presentation |
+| **Frontend Developer** | `frontend-dev` | Nuxt 4, Vue 3, TypeScript, Tailwind CSS 4, Nuxt UI 4, animations |
+| **Content Creator** | `content-marketer` | Copy, messaging, event storytelling, persuasive writing |
+| **SEO/Marketing** | `cro-specialist` | Landing page optimization, conversion, meta tags, performance |
+| **Security Engineer** | `security-eng` | XSS, CSP, form validation, data protection |
+| **QA Tester** | `qa-eng` | Vitest, Playwright, responsive testing, performance audits |
+| **DevOps** | `devops-eng` | Cloudflare Pages deployment, CI/CD, CDN, domain setup |
+
+## Key Architectural Notes
+
+- **Single page app**: `app/pages/index.vue` composed by 17 section components
+- **i18n-driven copy**: All text in `i18n/locales/*.json` — never in components
+- **i18n strategy**: `prefix_except_default` (pt has no URL prefix)
+- **Pre-rendered routes**: `/`, `/en`, `/fr`, `/es`, `/de`
+- **Speaker/sponsor data**: Lives in component `<script setup>` arrays
+- **Composables**: useCountdown, useScrollAnimate, useStructuredData, useSupabase
+- **Plugins**: gtm.client.ts (Google Tag Manager), clarity.client.ts (Microsoft Clarity)
+- **Public SEO files**: llms.txt, llms-full.txt, robots.txt, sitemap.xml
+- **Backend**: Supabase for registration form submissions only. No auth.
+
+## Components
+
+| Component | Section |
+|-----------|---------|
+| AppHeader | Navigation + language switcher + scroll spy |
+| LandingHero | Hero + countdown timer (27 Jun 2026) |
+| LandingAbout | About Murray Rothbard |
+| LandingAudience | Target audience |
+| LandingHighlights | Event highlights |
+| LandingBooks | Rothbard bibliography |
+| LandingBookLaunch | Book launch section |
+| LandingSchedule | Program/agenda |
+| LandingSpeakers | Speaker cards |
+| LandingTickets | Registration dialog + donation tiers |
+| LandingVideos | Video content |
+| LandingLocation | Venue / event location |
+| LandingObjections | Objections/FAQ |
+| LandingFaq | FAQ accordion |
+| LandingSponsors | Organizers + supporters logos |
+| LandingCta | Final call-to-action |
+| AppFooter | Footer |
+
+## Tech Stack Reference
+
+### rothbard100-landing
+- Nuxt 4.4.2, Vue 3, TypeScript (strict), Tailwind CSS 4, Nuxt UI v4.5.1
+- @nuxtjs/i18n — 5 locales (pt default, en, fr, es, de)
+- @nuxt/image v2
+- @nuxt/eslint (Code quality)
+- @supabase/supabase-js (registration form)
+- Iconify: @iconify-json/lucide + @iconify-json/simple-icons
+- Analytics: Google Tag Manager + Microsoft Clarity
+- SEO: JSON-LD structured data (Event, VideoObject, Organization, BreadcrumbList), OG image, llms.txt (GEO/AEO)
+- Package manager: pnpm
+- Build: SSG (Static Site Generation) via Nitro prerender
+- Hosting: Cloudflare Pages (auto-deploy from main branch)
+- ESLint: Stylistic config (commaDangle: never, braceStyle: 1tbs)
+
+### Key Conventions
+- TypeScript strict mode
+- Composition API (`<script setup lang="ts">`)
+- Light mode only (forced via colorMode)
+- Font: Inter (400–900)
+- CSS classes: `section-light`, `section-divider`, `scroll-animate`, `btn-gold`, `pulse-gold`
+- i18n strategy: `prefix_except_default`
+- Performance-first (target Lighthouse 95+)
+
+## Obsidian Output
+
+All documentation: `/Users/andreagroferreira/Documents/Personal/Projects/Rothbard100/`
+
+Structure:
+```
+Projects/Rothbard100/
+├── Home.md                    ← Ecosystem overview
+├── Landing Page.md            ← Landing page project docs
+├── Architecture/
+│   ├── System Architecture.md ← Architecture documentation
+│   └── Brand Guide.md         ← Brand colors, typography, style
+├── Content/
+│   ├── Copy Guide.md          ← Event messaging and copy standards
+│   └── Speaker Bios.md        ← Speaker information
+├── Squad/
+│   └── Workflows.md           ← Squad workflows and processes
+└── Decisions/                 ← Architecture Decision Records
+```

package/arka/skills/rothbard100/references/workflows.md

@@ -0,0 +1,175 @@
+# arka-rothbard100 — workflows
+
+Referenced from SKILL.md. Read only when needed.
+
+## Orchestration Workflow (Standard — 8 Phases)
+
+For EVERY `/rothbard100` request that modifies code or content:
+
+### Phase 1 — Context Loading
+1. Read the ecosystem registry: `~/.claude/skills/arka/knowledge/ecosystems.json`
+2. Read project files: `~/.claude/skills/arka/projects/rothbard100-landing/PROJECT.md`
+3. Read CLAUDE.md from affected project
+4. Check memory for prior related work and user feedback
+
+### Phase 2 — Analysis & Planning
+
+**Before planning, verify context:**
+- Restate the request to confirm understanding
+- Ask at least 1 clarifying question about scope or intent
+- Challenge at least 1 assumption (devil's advocate)
+
+1. Analyze the request against the ecosystem context
+2. Determine complexity tier (Quick / Standard / Complex)
+3. If Complex → route to `/arka-forge` for multi-perspective planning
+4. Determine which squad roles are needed
+5. Create execution plan with:
+   - **Affected projects** (which ones)
+   - **Squad members involved** (which roles)
+   - **Steps** (numbered, with responsible role)
+   - **Risks/considerations** (cross-project impact, brand consistency, event deadlines)
+   - **Estimated scope** (files to change)
+
+### Phase 3 — Specification (for features/new components)
+If the task creates new functionality:
+1. Define acceptance criteria (testable, BDD-style)
+2. Define scope (in scope / out of scope)
+3. Define edge cases
+4. User approves spec before implementation
+
+For bug fixes, refactors, content updates, and config changes: skip this phase.
+
+### Phase 4 — Plan Presentation & Approval
+Present the plan:
+
+```
+═══ ROTHBARD 100 — Execution Plan ═══
+
+📋 REQUEST: [summary of what was asked]
+🔧 COMPLEXITY: [Quick / Standard / Complex]
+
+🎯 AFFECTED PROJECTS:
+  • [project] — [what changes]
+
+👥 SQUAD:
+  • [role] — [responsibility in this task]
+
+📝 STEPS:
+  1. [step] — [role]
+  2. [step] — [role]
+  ...
+
+⚠️ CONSIDERATIONS:
+  • [risk/note]
+
+═══════════════════════════════
+```
+
+Ask for user approval: "Approve", "Modify", or "Cancel"
+
+### Phase 5 — Execution
+1. Only proceed after approval
+2. Execute using **worktree isolation** for code changes (NON-NEGOTIABLE)
+3. Each squad role runs as the appropriate agent type (dispatch real agents)
+4. Content Creator adapts all text — never mechanical copy-paste
+5. Cross-project changes are coordinated
+
+### Phase 6 — Self-Critique (NON-NEGOTIABLE)
+Before quality gate, the executing agent(s) must:
+1. Review own output against the plan and spec
+2. Check for regressions, missing edge cases, i18n consistency
+3. Verify build passes (`pnpm build`)
+4. Flag any concerns or deviations from plan
+
+### Phase 7 — Quality Gate (NON-NEGOTIABLE)
+
+Before any output reaches the user:
+- **Marta** (CQO) orchestrates the review
+- **Eduardo** (Copy Director) reviews all text output for spelling, grammar, tone, clarity, AI patterns
+- **Francisca** (Tech/UX Director) reviews all code and technical output for quality, security, correctness
+
+**Verdict:** APPROVED or REJECTED. Binary. No "approved with caveats."
+- APPROVED → proceed to Documentation phase
+- REJECTED → return to Execution phase with specific feedback, fix, re-submit
+
+### Phase 8 — Documentation & Report
+1. Update Obsidian documentation if the change is significant
+2. Present execution report:
+
+```
+═══ ROTHBARD 100 — Execution Report ═══
+
+✅ COMPLETED:
+  • [what was done]
+
+📁 FILES CHANGED:
+  • [project]: [files]
+
+🧪 BUILD:
+  • [build result]
+
+📝 DOCS UPDATED:
+  • [obsidian pages updated]
+
+═══════════════════════════════════
+```
+
+## /rothbard100 status
+
+Check the status of all Rothbard 100 projects:
+
+```bash
+# For each project:
+cd <project_path>
+git status
+git log --oneline -5
+git branch --show-current
+```
+
+Present as:
+
+```
+═══ ROTHBARD 100 — Ecosystem Status ═══
+
+📦 ROTHBARD100-LANDING (Nuxt 4 + Nuxt UI v4 — SSG)
+  Branch: [branch]
+  Last commit: [hash] — [message] ([date])
+  Status: [clean/uncommitted changes]
+
+═══════════════════════════════════
+```
+
+## /rothbard100 content
+
+For content tasks, the Content Creator role takes the lead:
+1. Understand the event messaging and libertarian context
+2. Write persuasive, bold copy aligned with the brand
+3. All copy lives in `i18n/locales/*.json` — never hardcode text
+4. 5 locales must be updated: pt (default), en, fr, es, de
+5. SEO/Marketing role reviews for conversion optimization
+6. Frontend Developer implements in components if needed
+
+## /rothbard100 seo
+
+SEO audit covers:
+1. Meta tags (title, description, OG tags, Twitter cards)
+2. Structured data (Event schema, Organization schema)
+3. Performance audit (Core Web Vitals, Lighthouse)
+4. Image optimization (@nuxt/image usage)
+5. Accessibility (WCAG 2.1 AA minimum)
+6. Mobile responsiveness
+
+## /rothbard100 context
+
+Show full ecosystem context:
+1. Read all project files and CLAUDE.md
+2. Present architecture, tech stack, components, conventions, current state
+
+## /rothbard100 scaffold <name>
+
+When scaffolding a new project:
+1. Use `/arka-scaffold` skill with the appropriate template
+2. Register the project in `ecosystems.json`
+3. Create a project detail file in `~/.claude/skills/arka/projects/<name>/PROJECT.md`
+4. Update SKILL.md's ecosystem overview table
+5. Create Obsidian documentation

package/config/constitution.yaml

@@ -121,6 +121,14 @@ enforcement_levels:
         rule: "All forge plans (approved and rejected) must be persisted to Obsidian"
         enforcement: "persistence.py exports on status change; audit detects missing exports"
 
+      - id: model-routing
+        rule: "Per-tier model assignment enforced: Tier 0 opus, Tier 1/2 sonnet, mechanical haiku. Quality Gate ALWAYS opus."
+        enforcement: "warning"
+
+      - id: subagent-discipline
+        rule: "Dispatch subagents only when task requires >3 Reads or >5 Greps or isolated context. Never parallel subagents sharing state. Prefer main thread for trivial tasks."
+        enforcement: "warning"
+
   should:
     description: "Best practices. Encouraged but not enforced."
     rules:

package/config/hooks/pre-compact.sh

@@ -27,9 +27,15 @@ TRANSCRIPT=$(echo "$input" | jq -r '.transcript // ""' 2>/dev/null)
 DIGEST_DIR="$HOME/.arkaos/session-digests"
 mkdir -p "$DIGEST_DIR"
 
-TIMESTAMP=$(date +%Y%m%d-%H%M%S)
 SHORT_ID=$(echo "$SESSION_ID" | head -c 8)
-DIGEST_FILE="${DIGEST_DIR}/${TIMESTAMP}-${SHORT_ID}.md"
+# Content-hash filename → deduplicable and cache-friendly.
+# Falls back to session id + transcript head so identical compactions collapse.
+if command -v shasum &>/dev/null; then
+  DIGEST_ID=$(printf '%s' "${SESSION_ID:-default}-$(printf '%s' "$TRANSCRIPT" | head -c 200 | tr -d '\n')" | shasum -a 256 | cut -c1-16)
+else
+  DIGEST_ID=$(printf '%s' "${SESSION_ID:-default}-$(printf '%s' "$TRANSCRIPT" | head -c 200 | tr -d '\n')" | md5 | cut -c1-16)
+fi
+DIGEST_FILE="${DIGEST_DIR}/digest-${SHORT_ID}-${DIGEST_ID}.md"
 
 # ─── Extract Context ──────────────────────────────────────────────────────
 # Get last 50 lines of transcript
@@ -56,14 +62,14 @@ cat > "$DIGEST_FILE" << DIGEST_EOF
 ---
 type: session-digest
 session_id: ${SESSION_ID}
-timestamp: ${TIMESTAMP}
+digest_id: ${DIGEST_ID}
 trigger: pre-compact
 ---
 
-# Session Digest — ${TIMESTAMP}
+# Session Digest — ${DIGEST_ID}
 
 **Session:** \`${SESSION_ID}\`
-**Saved at:** $(date '+%Y-%m-%d %H:%M:%S')
+**Digest:** \`${DIGEST_ID}\`
 **Trigger:** Context compaction
 
 ## Last Assistant Messages

package/config/hooks/session-start.sh

@@ -19,11 +19,10 @@ if [ -f "$HOME/.arkaos/.repo-path" ]; then
   [ -f "$REPO/VERSION" ] && VERSION=$(cat "$REPO/VERSION" | tr -d '[:space:]')
 fi
 
-# ─── Time greeting ─────────────────────────────────────────────────────
-HOUR=$(date +%H)
-if [ "$HOUR" -ge 5 ] && [ "$HOUR" -lt 12 ]; then GREETING="Bom dia"
-elif [ "$HOUR" -ge 12 ] && [ "$HOUR" -lt 19 ]; then GREETING="Boa tarde"
-else GREETING="Boa noite"; fi
+# ─── Static greeting (cache-friendly) ──────────────────────────────────
+# Time-of-day branching removed: it invalidated prompt cache 3x/day without
+# meaningful signal. Static greeting keeps SessionStart output stable.
+GREETING="Olá"
 
 # ─── Version drift ─────────────────────────────────────────────────────
 SYNC_STATE="$HOME/.arkaos/sync-state.json"