Attempting fix for missing verses

.Jules/palette.md

@@ -0,0 +1,4 @@
+
+## 2024-05-18 - Added aria-label to Dashboard icon buttons
+**Learning:** React components returning icon-only buttons via `lucide-react` icons (like `Users`, `BookOpen`) inside Radix UI primitives (`Button`, `DropdownMenuTrigger`) must explicitly have `aria-label` attributes set to be accessible by screen readers. The `title` attribute is primarily for visual tooltips and does not sufficiently substitute for `aria-label` for assistive technologies in all contexts.
+**Action:** When adding new icon-only buttons to the UI, particularly within navigation bars or dropdown triggers, always include a descriptive `aria-label` attribute alongside the `title` attribute.

.claude/hooks/session-start.sh

@@ -0,0 +1,5 @@
+#!/bin/bash
+# Wrapper for the Python SessionStart hook
+# $CLAUDE_PROJECT_DIR is provided by Claude, but we can fallback to PWD
+PROJECT_DIR="${CLAUDE_PROJECT_DIR:-$(pwd)}"
+python3 "$PROJECT_DIR/scripts/hooks/session_start.py"

.claude/settings.json

@@ -0,0 +1,15 @@
+{
+  "hooks": {
+    "SessionStart": [
+      {
+        "matcher": ".*",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "$CLAUDE_PROJECT_DIR/.claude/hooks/session-start.sh"
+          }
+        ]
+      }
+    ]
+  }
+}

.claude/settings.local.json

@@ -0,0 +1,9 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(python3:*)"
+    ],
+    "deny": [],
+    "ask": []
+  }
+}

.github/workflows/ci.yml

@@ -18,8 +18,7 @@ jobs:
         uses: actions/setup-go@v5
         with:
           go-version: 'stable'
-          cache: true
-          cache-dependency-path: api/go.sum
+          cache: false
 
       - name: Install dependencies
         run: go mod tidy
@@ -49,6 +48,7 @@ jobs:
         with:
           name: backend-coverage
           path: api/coverage.txt
+          retention-days: 1
 
   frontend:
     runs-on: ubuntu-latest
@@ -63,8 +63,6 @@ jobs:
         uses: actions/setup-node@v4
         with:
           node-version: '20'
-          cache: 'npm'
-          cache-dependency-path: web/package-lock.json
 
       - name: Install dependencies
         run: npm ci
@@ -81,6 +79,7 @@ jobs:
         with:
           name: frontend-coverage
           path: web/coverage/coverage-summary.json
+          retention-days: 1
 
       - name: Build
         run: npm run build
@@ -99,8 +98,6 @@ jobs:
         uses: actions/setup-node@v4
         with:
           node-version: '20'
-          cache: 'npm'
-          cache-dependency-path: web/package-lock.json
 
       - name: Install dependencies
         run: npm ci
@@ -124,7 +121,7 @@ jobs:
         with:
           name: playwright-report
           path: web/playwright-report/
-          retention-days: 30
+          retention-days: 1
 
   coverage-report:
     runs-on: ubuntu-latest
@@ -153,3 +150,19 @@ jobs:
           script: |
             const script = require('./scripts/gh-actions/post-coverage-comment.js')
             await script({github, context})
+
+  automerge:
+    needs: [backend, frontend, e2e, coverage-report]
+    runs-on: ubuntu-latest
+    if: github.event_name == 'pull_request' && github.event.pull_request.user.login == 'julwrites' && github.event.pull_request.base.ref == 'staging'
+    permissions:
+      contents: write
+      pull-requests: write
+    steps:
+      - name: Automerge PR
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          PR_URL: ${{ github.event.pull_request.html_url }}
+        run: |
+          gh pr review --approve "$PR_URL" || true
+          gh pr merge --rebase --delete-branch "$PR_URL"

.github/workflows/deploy-staging.yml

@@ -85,7 +85,7 @@ jobs:
           region: ${{ env.GCP_REGION }}
           flags: '--service-account=${{ secrets.GCP_SERVICE_ACCOUNT }} --allow-unauthenticated'
           env_vars: |
-            APP_ENV=production
+            APP_ENV=staging
             GOOGLE_CLOUD_PROJECT=${{ env.GCP_PROJECT_ID }}
             FIREBASE_PROJECT_ID=${{ secrets.STG_FIREBASE_PROJECT_ID }}
             # Application secrets (STG_DJ_DB_*) are loaded from Google Secret Manager at runtime

.github/workflows/weekly-coverage.yml

@@ -19,8 +19,7 @@ jobs:
         uses: actions/setup-go@v5
         with:
           go-version: 'stable'
-          cache: true
-          cache-dependency-path: api/go.sum
+          cache: false
 
       - name: Install dependencies
         run: go mod tidy
@@ -43,6 +42,7 @@ jobs:
         with:
           name: backend-coverage
           path: api/coverage.txt
+          retention-days: 1
 
   frontend:
     runs-on: ubuntu-latest
@@ -57,8 +57,6 @@ jobs:
         uses: actions/setup-node@v4
         with:
           node-version: '20'
-          cache: 'npm'
-          cache-dependency-path: web/package-lock.json
 
       - name: Install dependencies
         run: npm ci
@@ -72,3 +70,4 @@ jobs:
         with:
           name: frontend-coverage
           path: web/coverage/coverage-summary.json
+          retention-days: 1

.gitignore

@@ -33,3 +33,7 @@ test-results/
 # Go binaries
 */discipleship_journal_api
 *.log
+
+.agents/
+__pycache__/
+*.pyc

AGENTS.md

@@ -3,47 +3,12 @@
 You are an expert Software Engineer working on this project. Your primary responsibility is to implement features and fixes while strictly adhering to the **Task Documentation System**.
 
 ## Core Philosophy
-**"If it's not documented in `docs/tasks/`, it didn't happen."**
-
-## Workflow
-1.  **Pick a Task**: Run `python3 scripts/tasks.py next` to find the best task, `context` to see active tasks, or `list` to see pending ones.
-2.  **Plan & Document**:
-    *   **Memory Check**: Run `python3 scripts/memory.py list` (or use the Memory Skill) to recall relevant long-term information.
-    *   **Security Check**: Ask the user about specific security considerations for this task.
-    *   If starting a new task, use `scripts/tasks.py create` (or `python3 scripts/tasks.py create`) to generate a new task file.
-    *   Update the task status: `python3 scripts/tasks.py update [TASK_ID] in_progress`.
-3.  **Implement**: Write code, run tests.
-4.  **Update Documentation Loop**:
-    *   As you complete sub-tasks, check them off in the task document.
-    *   If you hit a blocker, update status to `wip_blocked` and describe the issue in the file.
-    *   Record key architectural decisions in the task document.
-    *   **Memory Update**: If you learn something valuable for the long term, use `scripts/memory.py create` to record it.
-5.  **Review & Verify**:
-    *   Once implementation is complete, update status to `review_requested`: `python3 scripts/tasks.py update [TASK_ID] review_requested`.
-    *   Ask a human or another agent to review the code.
-    *   Once approved and tested, update status to `verified`.
-6.  **Finalize**:
-    *   Update status to `completed`: `python3 scripts/tasks.py update [TASK_ID] completed`.
-    *   Record actual effort in the file.
-    *   Ensure all acceptance criteria are met.
-
-## Tools
-*   **Wrapper**: `./scripts/tasks` (Checks for Python, recommended).
-*   **Next**: `./scripts/tasks next` (Finds the best task to work on).
-*   **Create**: `./scripts/tasks create [category] "Title"`
-*   **List**: `./scripts/tasks list [--status pending]`
-*   **Context**: `./scripts/tasks context`
-*   **Update**: `./scripts/tasks update [ID] [status]`
-*   **Migrate**: `./scripts/tasks migrate` (Migrate legacy tasks to new format)
-*   **Memory**: `./scripts/memory.py [create|list|read]`
-*   **JSON Output**: Add `--format json` to any command for machine parsing.
+This repository uses the agent-harness conventions.
 
 ## Documentation Reference
-*   **Guide**: Read `docs/tasks/GUIDE.md` for strict formatting and process rules.
 *   **Architecture**: Refer to `docs/architecture/` for system design.
 *   **Features**: Refer to `docs/features/` for feature specifications.
 *   **Security**: Refer to `docs/security/` for risk assessments and mitigations.
-*   **Memories**: Refer to `docs/memories/` for long-term project context.
 
 ## Code Style & Standards
 
@@ -102,7 +67,3 @@ Once the human approves the plan and comments:
 ### 4. Close Task
 *   Update task status to `completed`.
 
-## Agent Interoperability
-- **Task Manager Skill**: `.claude/skills/task_manager/`
-- **Memory Skill**: `.claude/skills/memory/`
-- **Tool Definitions**: `docs/interop/tool_definitions.json`

README.md

@@ -40,7 +40,6 @@ For detailed setup instructions, see:
 See `web/README.md` for frontend-specific instructions.
 
 ## Documentation
-- **Tasks & Status**: `docs/tasks/`
 - **Features**: `docs/features/`
 - **Architecture**: `docs/architecture/`
 - **Testing**: `docs/testing/`