loki-mode 10.5.17 → 10.5.20

package/docs/enterprise/integration-cookbook.md

@@ -1,4 +1,4 @@
-# Loki Mode v5.51.0 -- Integration Cookbook
+# Loki Mode Integration Cookbook
 
 Step-by-step guides for connecting Loki Mode to external services. Each integration is opt-in and configured via environment variables.
 
@@ -173,9 +173,16 @@ curl -X POST "$LOKI_TEAMS_WEBHOOK_URL" \
 | Variable | Required | Description |
 |----------|----------|-------------|
 | `LOKI_JIRA_URL` | Yes | Jira Cloud base URL |
-| `LOKI_JIRA_EMAIL` | Yes | Jira user email for authentication |
 | `LOKI_JIRA_TOKEN` | Yes | Jira API token |
-| `LOKI_JIRA_PROJECT_KEY` | No | Default Jira project key |
+| `LOKI_JIRA_EPIC_KEY` | No | Epic that run events are synced to |
+
+These are read by `src/integrations/sync-subscriber.js`. The Jira user email is
+passed to `JiraApiClient` in code (see below); no environment variable carries it.
+
+Known issue on main: `src/integrations/sync-subscriber.js` constructs `JiraApiClient`
+without the `email` and `apiToken` it requires, so Jira auto-sync from these
+variables does not start. Construct `JiraApiClient({ baseUrl, email, apiToken })`
+in code until that is fixed.
 
 ### Configuration
 
@@ -187,9 +194,7 @@ curl -X POST "$LOKI_TEAMS_WEBHOOK_URL" \
 
    ```bash
    export LOKI_JIRA_URL="https://company.atlassian.net"
-   export LOKI_JIRA_EMAIL="user@company.com"
    export LOKI_JIRA_TOKEN="your-api-token"
-   export LOKI_JIRA_PROJECT_KEY="PROJ"
    ```
 
 3. **Epic Sync:**
@@ -202,7 +207,7 @@ curl -X POST "$LOKI_TEAMS_WEBHOOK_URL" \
 
    const api = new JiraApiClient({
      baseUrl: process.env.LOKI_JIRA_URL,
-     email: process.env.LOKI_JIRA_EMAIL,
+     email: 'user@company.com',
      apiToken: process.env.LOKI_JIRA_TOKEN,
    });
 
@@ -250,11 +255,11 @@ curl -X POST "$LOKI_TEAMS_WEBHOOK_URL" \
 
 ```bash
 # Test Jira API access
-curl -u "$LOKI_JIRA_EMAIL:$LOKI_JIRA_TOKEN" \
+curl -u "user@company.com:$LOKI_JIRA_TOKEN" \
   "$LOKI_JIRA_URL/rest/api/3/myself" | python3 -m json.tool
 
 # Test epic fetch
-curl -u "$LOKI_JIRA_EMAIL:$LOKI_JIRA_TOKEN" \
+curl -u "user@company.com:$LOKI_JIRA_TOKEN" \
   "$LOKI_JIRA_URL/rest/api/3/issue/PROJ-123" | python3 -m json.tool
 ```
 
@@ -282,9 +287,12 @@ curl -u "$LOKI_JIRA_EMAIL:$LOKI_JIRA_TOKEN" \
 
 | Variable | Required | Description |
 |----------|----------|-------------|
-| `LOKI_LINEAR_API_KEY` | Yes | Linear personal API key |
+| `LOKI_LINEAR_TOKEN` | Yes | Linear personal API key |
 | `LOKI_LINEAR_TEAM_ID` | No | Default team ID for issue creation |
-| `LOKI_LINEAR_WEBHOOK_SECRET` | No | Webhook signing secret for inbound events |
+| `LOKI_LINEAR_PROJECT_ID` | No | Project that run events are synced to |
+
+The webhook signing secret is not an environment variable; set `webhook_secret`
+under `integrations.linear` in `.loki/config.yaml`.
 
 ### Configuration
 
@@ -295,7 +303,7 @@ curl -u "$LOKI_JIRA_EMAIL:$LOKI_JIRA_TOKEN" \
 2. **Set Environment Variables:**
 
    ```bash
-   export LOKI_LINEAR_API_KEY="lin_api_your_key_here"
+   export LOKI_LINEAR_TOKEN="lin_api_your_key_here"
    export LOKI_LINEAR_TEAM_ID="your-team-id"
    ```
 
@@ -304,7 +312,7 @@ curl -u "$LOKI_JIRA_EMAIL:$LOKI_JIRA_TOKEN" \
    ```javascript
    const { LinearClient } = require('./src/integrations/linear/client');
 
-   const client = new LinearClient(process.env.LOKI_LINEAR_API_KEY);
+   const client = new LinearClient(process.env.LOKI_LINEAR_TOKEN);
 
    // Fetch a project with all issues
    const project = await client.getProject('project-id');
@@ -338,14 +346,15 @@ curl -u "$LOKI_JIRA_EMAIL:$LOKI_JIRA_TOKEN" \
 
 5. **Webhook Handler (optional):**
 
-   Configure Linear to send webhooks to your Loki Mode instance for bidirectional sync.
+   Configure Linear to send webhooks to your Loki Mode instance. Signatures are
+   verified when `webhook_secret` is set (`src/integrations/linear/sync.js`).
 
 ### Verification
 
 ```bash
 # Test Linear API access
 curl -X POST https://api.linear.app/graphql \
-  -H "Authorization: $LOKI_LINEAR_API_KEY" \
+  -H "Authorization: $LOKI_LINEAR_TOKEN" \
   -H "Content-Type: application/json" \
   -d '{"query": "{ viewer { id name } }"}'
 ```

package/docs/enterprise/migration.md

@@ -1,4 +1,4 @@
-# Loki Mode v5.51.0 -- Migration Guide
+# Loki Mode Migration Guide
 
 ## Upgrading from v5.50.0 to v5.51.0
 
@@ -76,10 +76,7 @@ See `docs/enterprise/sdk-guide.md` for installation and usage.
 | `LOKI_TEAMS_WEBHOOK_SECRET` | (unset) | Teams webhook shared secret |
 | `LOKI_OIDC_ISSUER` | (unset) | OIDC identity provider URL |
 | `LOKI_OIDC_CLIENT_ID` | (unset) | OIDC client ID |
-| `LOKI_OIDC_CLIENT_SECRET` | (unset) | OIDC client secret |
-| `LOKI_OIDC_REDIRECT_URI` | (unset) | OIDC redirect URI |
-| `LOKI_CORS_ORIGINS` | localhost | Allowed CORS origins |
-| `LOKI_API_RATE_LIMIT` | 100 | API rate limit (requests/min) |
+| `LOKI_DASHBOARD_CORS` | localhost | Allowed CORS origins |
 
 ### Existing Environment Variables (Unchanged)
 
@@ -101,12 +98,11 @@ These variables from v5.50.0 continue to work identically:
 | `LOKI_TLS_CERT` | (unset) | TLS certificate path |
 | `LOKI_TLS_KEY` | (unset) | TLS key path |
 | `LOKI_JIRA_URL` | (unset) | Jira Cloud base URL |
-| `LOKI_JIRA_EMAIL` | (unset) | Jira user email |
 | `LOKI_JIRA_TOKEN` | (unset) | Jira API token |
-| `LOKI_JIRA_PROJECT_KEY` | (unset) | Default Jira project key |
-| `LOKI_LINEAR_API_KEY` | (unset) | Linear API key |
+| `LOKI_JIRA_EPIC_KEY` | (unset) | Jira epic that run events sync to |
+| `LOKI_LINEAR_TOKEN` | (unset) | Linear API key |
 | `LOKI_LINEAR_TEAM_ID` | (unset) | Linear team ID |
-| `LOKI_LINEAR_WEBHOOK_SECRET` | (unset) | Linear webhook secret |
+| `LOKI_LINEAR_PROJECT_ID` | (unset) | Linear project that run events sync to |
 | `LOKI_GITHUB_SYNC` | (unset) | Enable GitHub sync |
 
 ### API Changes

package/docs/enterprise/performance.md

@@ -1,4 +1,4 @@
-# Loki Mode v5.51.0 -- Enterprise Performance Tuning
+# Loki Mode Enterprise Performance Tuning
 
 ## Overview
 
@@ -233,11 +233,8 @@ uvicorn dashboard.server:app --workers 4 --host 0.0.0.0 --port 57374
 
 Dashboard API rate limits protect against abuse:
 
-```bash
-# Default rate limits are built into the API layer
-# Override via env vars if needed
-export LOKI_API_RATE_LIMIT="100"  # requests per minute
-```
+Rate limits are built into the API layer (10 requests/min on control endpoints,
+60 on rate-limited read endpoints) and are not configurable by environment variable.
 
 ### Static Asset Caching
 

package/docs/enterprise/sdk-guide.md

@@ -1,4 +1,4 @@
-# Loki Mode v5.51.0 -- SDK Guide
+# Loki Mode SDK Guide
 
 Official Python and TypeScript SDKs for the Autonomi Control Plane API. Both SDKs have zero external dependencies -- they use only standard library features.
 

package/docs/enterprise/security.md

@@ -1,4 +1,4 @@
-# Loki Mode v5.51.0 -- Enterprise Security
+# Loki Mode Enterprise Security
 
 ## Overview
 
@@ -167,27 +167,18 @@ When both variables are set, the dashboard server binds on HTTPS only. Self-sign
 
 ### Rate Limiting
 
-The API enforces rate limits per token/IP:
-
-| Endpoint Group | Default Limit |
-|----------------|---------------|
-| Read operations | 100 req/min |
-| Write operations | 30 req/min |
-| Auth operations | 10 req/min |
-
-Rate limit headers are included in every response:
-```
-X-RateLimit-Limit: 100
-X-RateLimit-Remaining: 95
-X-RateLimit-Reset: 1708520460
-```
+The dashboard API applies in-process rate limits (`_RateLimiter` in
+`dashboard/server.py`): 10 requests/min on control endpoints and 60
+requests/min on rate-limited read endpoints. Exceeding them returns HTTP 429.
+The limits are not configurable by environment variable, and no
+`X-RateLimit-*` headers are sent.
 
 ### CORS
 
 CORS is configured via environment variables:
 
 ```bash
-export LOKI_CORS_ORIGINS="https://dashboard.company.com,https://admin.company.com"
+export LOKI_DASHBOARD_CORS="https://dashboard.company.com,https://admin.company.com"
 ```
 
 Default behavior: `localhost` origins are allowed for development. In production, explicitly set allowed origins.
@@ -228,7 +219,7 @@ This is a deliberate fail-closed design. Invalid or missing signatures always re
 
 ## Audit Logging
 
-### Hash-Chained Tamper-Evident Logs
+### Hash-Chained Audit Logs
 
 Audit logs use SHA-256 hash chains for tamper evidence. Each entry's hash depends on the previous entry's hash, creating an immutable chain from the genesis record.
 

package/docs/exit-codes.md

@@ -50,6 +50,20 @@ immediately instead of burning `backoffLimit`. Requires Kubernetes 1.31+.
 Both the bash runner and the Bun runner (`LOKI_SDK_LOOP`) implement this
 identically; a parity test asserts they agree status for status.
 
+## `loki quick`
+
+| Code | Meaning |
+|---|---|
+| 0 | The run completed and its diff did not weaken the tests |
+| 3 | The diff weakened the tests (a skip marker added in a test file, a test runner config changed, or an existing test file deleted or renamed). The receipt headline is NOT VERIFIED and names what was weakened, for example `NOT VERIFIED (tests weakened: skip added in sum.test.js)` |
+| other nonzero | The run itself failed; this code is passed through unchanged |
+
+Code 3 only ever raises an exit of 0, in quiet and `LOKI_VERBOSE=1` modes alike;
+it never lowers another nonzero code. Edited assertion lines are disclosed in
+the receipt (`tests_integrity:assertions_edited`) and keep exit 0. A NOT VERIFIED
+headline caused by unproven gates alone also keeps exit 0. The signal is the
+`tests_integrity` item in the proof's `honesty.degraded`, not the headline text.
+
 ## `loki verify`
 
 | Code | Verdict |

package/docs/git-workflow.md

@@ -19,7 +19,7 @@ When enabled, Loki Mode automatically:
 
 1. Creates a feature branch: `loki/session-<timestamp>-<pid>`
 2. Performs all agent work on the feature branch
-3. Creates a PR at session end (if GitHub CLI is available)
+3. Creates a PR at session end when `LOKI_AUTO_PR=1` (and GitHub CLI is available)
 4. Requires manual review and merge to main
 
 ### Feature Branch Naming
@@ -62,25 +62,8 @@ Delete feature branch
 
 | Variable | Default | Description |
 |----------|---------|-------------|
-| `LOKI_BRANCH_PROTECTION` | `false` | Enable automatic feature branch workflow |
-| `LOKI_BASE_BRANCH` | `main` | Target branch for PRs (or `master` if detected) |
-| `LOKI_BRANCH_PREFIX` | `loki/session-` | Prefix for auto-created branches |
-| `LOKI_AUTO_PR` | `true` | Automatically create PR at session end |
-| `LOKI_PR_TEMPLATE` | - | Path to PR description template |
-
-### Configuration File
-
-```yaml
-# .loki/config.yaml
-git:
-  branch_protection:
-    enabled: true
-    base_branch: main
-    branch_prefix: loki/session-
-    auto_pr: true
-    squash_merge: true
-    delete_after_merge: true
-```
+| `LOKI_BRANCH_PROTECTION` | `true` | Run agent work on an auto-created `loki/session-<timestamp>-<pid>` branch |
+| `LOKI_AUTO_PR` | off | Set to `1` to push the session branch and open a PR at session end |
 
 ## Manual Git Workflow
 
@@ -126,7 +109,7 @@ git push origin feature/my-feature
 
 ### Automatic PR Creation
 
-When `LOKI_AUTO_PR=true` and GitHub CLI is installed:
+When `LOKI_AUTO_PR=1` and GitHub CLI is installed:
 
 ```bash
 # Loki Mode automatically runs at session end
@@ -137,47 +120,6 @@ gh pr create \
   --head loki/session-20260215-143022-12345
 ```
 
-### PR Description Template
-
-Create a template for consistent PR descriptions:
-
-```markdown
-# .loki/pr-template.md
-
-## Changes
-
-<!-- Auto-generated summary of changes -->
-
-## Tasks Completed
-
-<!-- List of completed tasks from task queue -->
-
-## Quality Gates
-
-- [ ] All tests passing
-- [ ] Code review completed
-- [ ] No security vulnerabilities
-- [ ] Documentation updated
-
-## Cost
-
-Estimated cost: $X.XX USD
-
-## Session Info
-
-- Start: YYYY-MM-DD HH:MM:SS
-- End: YYYY-MM-DD HH:MM:SS
-- Duration: X hours
-- Iterations: X
-- Provider: claude/cline/codex/aider/opencode
-```
-
-Set template path:
-
-```bash
-export LOKI_PR_TEMPLATE=.loki/pr-template.md
-```
-
 ## Agent Action Audit
 
 All Git operations performed by agents are logged to `.loki/logs/agent-audit.jsonl`:

package/docs/network-security.md

@@ -6,19 +6,9 @@ Network egress control and isolation for Loki Mode deployments.
 
 This guide covers network-level security controls for restricting outbound network access from Loki Mode containers and pods to only the AI API endpoints required for operation.
 
-## Environment Variables
-
-**None of the variables below are implemented. Do not rely on them.** They are
-reserved names for a planned application-level enforcement layer, and no
-runtime code reads any of them today. Network security is enforced entirely at
-the infrastructure level, using the Docker network and Kubernetes NetworkPolicy
-recipes in the rest of this guide.
-
-| Variable | Default | Description | Status |
-|----------|---------|-------------|--------|
-| `LOKI_NETWORK_EGRESS_POLICY` | `unrestricted` | `unrestricted` (default), `ai-only` (restrict to AI APIs), `none` (block all outbound) | Planned, target TBD |
-| `LOKI_ALLOWED_HOSTS` | (empty) | Comma-separated list of additional hostnames to allow when egress policy is `ai-only` | Planned, target TBD |
-| `LOKI_BLOCK_METADATA_ENDPOINT` | `false` | Block cloud metadata endpoint (169.254.169.254) from within the application | Planned, target TBD |
+Loki Mode has no application-level egress setting: no runtime code restricts
+outbound hosts. Network security is enforced entirely at the infrastructure
+level, using the Docker network and Kubernetes NetworkPolicy recipes below.
 
 ## Docker Network Isolation
 

package/docs/plans/ULTRAPLAN-FORGE-BAAS.md

@@ -25,7 +25,7 @@ Loki Mode today is a **multi-agent autonomous orchestrator**, not a BaaS. It own
 - An auth layer (`dashboard/auth.py`, `web-app/auth.py`) supporting Bearer tokens, OIDC (Google/Azure/Okta), bcrypt password hashing, RBAC scopes
 - A working completion-council with anti-sycophancy, 3-reviewer parallel review, devil's-advocate fallback
 - A healing-mode for legacy systems (v6.67+) with friction-as-semantics
-- 41 specialized agent types and a queue system
+- Specialized agent types and a queue system
 
 **The gap:** every backend primitive Loki owns is for orchestrating the agent. None of it is for the *application the agent is building*. When `loki start ./prd.md` builds "a Twitter clone with login and image uploads", the agent has to invent the auth flow, choose a DB, set up storage, wire Stripe, etc. - and the user has to run a parallel set of tools (Supabase, Stripe, Cloudflare R2) to support the resulting app.
 

package/docs/prd-purple-lab-platform-v2.md

@@ -165,7 +165,7 @@ URL bar showing current preview path, Refresh button, Open in New Tab button.
 Based on feedback:
 - Memory System Viewer (power-user debug tool, not customer-facing)
 - Full Integrations page (keep GitHub only, defer Jira/Linear/Slack/Teams)
-- 41-agent grid (most sessions have 1-3 agents active; show compact list instead)
+- Agent grid (most sessions have 1-3 agents active; show compact list instead)
 - Code Review panel (let quality gates surface findings inline)
 - Collaboration/multiplayer (acknowledged as future need, not v1)
 - Database provisioning (out of scope for v1)

package/docs/prd-purple-lab-platform.md

@@ -137,8 +137,6 @@ Each card:
 
 Integrations available:
 - **GitHub**: Connect repo, import issues, create PRs (`loki github`, `loki run`)
-- **Jira**: Bidirectional sync (`LOKI_JIRA_*` env vars)
-- **Linear**: Issue sync (`LOKI_LINEAR_*` env vars)
 - **Slack**: Notifications + slash commands (`LOKI_SLACK_*`)
 - **Teams**: Adaptive Cards notifications (`LOKI_TEAMS_*`)
 - **OpenTelemetry**: Trace export (`loki telemetry`)
@@ -197,7 +195,7 @@ Each gate: name, status (pass/fail/pending), details expandable
 
 ### Agent Activity
 
-Real-time grid showing which of the 41 agent types are active:
+Real-time grid showing which agent types are active:
 - Agent name, type, domain, model tier (Opus/Sonnet/Haiku)
 - Current task
 - Status (working/idle/completed)

package/docs/research-2026-07/GAP-ANALYSIS-BACKLOG.md

@@ -65,7 +65,7 @@ Acceptance criteria:
 Validation: Fixture repos: (A) spec names endpoint /orders that exists -> no finding; (B) spec names /orders but no handler -> High finding; (C) plaintext password store -> invariant finding. Measure false-positive rate on 3 clean real repos (must be zero). Prove accuracy lift on the FrontierCode-style benchmark (rank 12): source-grounded checklists should catch wrong-but-internally-consistent implementations that prose-only checklists pass.
 
 ### #3 Annotate-before-act: pre-committed expected-outcome ledger, diffed against reality at verify time (loki-mode, high/L)
-Before running verification for a change/checklist-item, the runtime writes a tamper-evident ledger of EXPECTED observable outcomes (e.g. 'GET /health -> 200 {status:ok}', 'test X fails before fix, passes after', 'endpoint Y should now exist'). At verify time, actual results are compared to the pre-committed prediction; any expectation silently dropped or contradicted becomes a finding. Reuse the proof-verify canonical-hash + drift pattern so the ledger is tamper-evident and edits-after-the-fact are detectable. Forces a falsifiable prediction, cutting self-serving post-hoc rationalization.
+Before running verification for a change/checklist-item, the runtime writes a hash-chained ledger of EXPECTED observable outcomes (e.g. 'GET /health -> 200 {status:ok}', 'test X fails before fix, passes after', 'endpoint Y should now exist'). At verify time, actual results are compared to the pre-committed prediction; any expectation silently dropped or contradicted becomes a finding. Reuse the proof-verify canonical-hash + drift pattern so the ledger is tamper-evident and edits-after-the-fact are detectable. Forces a falsifiable prediction, cutting self-serving post-hoc rationalization.
 Acceptance criteria:
 - .loki/expectations/<iter>.json written BEFORE the verify/checklist run, each entry {id, statement, check_ref, expected}, canonicalized and hashed like proof-generator
 - loki verify (or the completion gate) reads the ledger and emits a finding for any expectation with no matching executed check, or whose actual contradicts expected

package/docs/show-hn-post.md

@@ -2,13 +2,13 @@
 
 ## Title
 
-Show HN: Loki Mode - PRD in, tested code out (41 agent roles, 8 quality gates, RARV self-verification)
+Show HN: Loki Mode - PRD in, tested code out (8 quality gates, RARV self-verification)
 
 ## Body
 
 I built Loki Mode because I got tired of the copy-paste loop between AI coding assistants and my terminal. I wanted to hand over a PRD and get back a working, tested codebase -- not perfect, but a solid starting point.
 
-**What it does:** You give it a Product Requirements Document. It breaks the work into tasks across 41 specialized agent roles organized into 8 domains (engineering, operations, business, data, product, growth, review, orchestration) -- prompt-defined specifications the orchestrator adopts per phase, with parallel review (blind council) and optional worktree streams on Claude Code, sequential on other providers -- and runs every iteration through a self-verification loop called RARV: Reason, Act, Reflect, Verify. The idea is that the system catches its own mistakes before you have to.
+**What it does:** You give it a Product Requirements Document. It breaks the work into tasks across specialized agent roles (engineering, operations, business, data, product, growth, review, orchestration) -- prompt-defined specifications the orchestrator adopts per phase, with parallel review (blind council) and optional worktree streams on Claude Code, sequential on other providers -- and runs every iteration through a self-verification loop called RARV: Reason, Act, Reflect, Verify. The idea is that the system catches its own mistakes before you have to.
 
 **Quality gates:** 8 automated gates including 3-reviewer blind review (agents review each other's work without seeing prior reviews), anti-sycophancy checks (a devil's advocate pass on unanimous approvals), and mock/mutation detection. These are not foolproof, but they catch a surprising number of issues that single-pass generation misses.
 
@@ -20,9 +20,8 @@ I built Loki Mode because I got tired of the copy-paste loop between AI coding a
 
 **Research foundation:** The architecture draws from Anthropic's Constitutional AI (principles-based self-critique), DeepMind's Scalable Oversight via Debate, and OpenAI's Agents SDK patterns (guardrails, tripwires, handoffs). References to specific papers are in the repo.
 
-**What it does NOT do:** It does not deploy anything. It generates deployment configs (Helm, Docker Compose, Terraform), but a human deploys. Complex domain logic will need human review. The system can and does make mistakes, especially on novel problems. Token costs scale with project complexity. Our SWE-bench numbers (299/300 patches generated) measure output, not resolution -- the official evaluator has not been run, so the actual fix rate is unknown and likely significantly lower than the generation rate. The HumanEval score is self-reported with max 3 retries per problem.
+**What it does NOT do:** It does not deploy anything. It generates deployment configs (Helm, Docker Compose, Terraform), but a human deploys. Complex domain logic will need human review. The system can and does make mistakes, especially on novel problems. Token costs scale with project complexity. There is no published benchmark score.
 
-**Test suite:** 683 npm tests, 631 pytest tests, 16 shell tests. Self-reported HumanEval score of 162/164 (98.78%).
 
 Built solo. BUSL-1.1 source-available.
 

package/docs/siem-integration.md

@@ -8,7 +8,7 @@ Loki Mode supports integration with enterprise SIEM systems for:
 
 - Centralized security monitoring
 - Real-time threat detection
-- Compliance reporting (SOC2, HIPAA, PCI-DSS)
+- Audit evidence for your own compliance reporting
 - Incident response
 - Forensic analysis
 
@@ -385,7 +385,6 @@ logs:
     tags:
       - env:production
       - team:security
-      - compliance:soc2
 
 # Process JSON logs
 logs_config:
@@ -487,14 +486,13 @@ in your SIEM, where the correlation and retention rules already live.
 To pull an evidence slice locally for an auditor:
 
 ```bash
-AUDIT=~/.loki/dashboard/audit/audit.jsonl
+AUDIT=~/.loki/dashboard/audit   # one audit-YYYY-MM-DD.jsonl file per day
 
-# Access events in a date range (SOC2 / HIPAA evidence)
-jq -s 'map(select(.timestamp >= "2026-01-01" and .timestamp <= "2026-12-31"))' \
-  "$AUDIT" > audit-evidence.json
+# Events in a date range
+cat "$AUDIT"/audit-*.jsonl | jq -s 'map(select(.timestamp >= "2026-01-01" and .timestamp <= "2026-12-31"))' > audit-evidence.json
 
-# Token lifecycle events (PCI-DSS Requirement 8)
-jq -c 'select(.event | startswith("auth.token."))' "$AUDIT"
+# Token lifecycle events
+cat "$AUDIT"/audit-*.jsonl | jq -c 'select(.resource_type == "token")'
 ```
 
 Verify the hash chain before handing the file over. There is no
@@ -592,8 +590,8 @@ logger -n syslog.example.com -P 514 "Test from Loki Mode"
 echo $LOKI_AUDIT_SYSLOG_HOST
 loki syslog test
 
-# Check for forwarding errors
-loki enterprise audit tail --event syslog.error
+# Check recent audit entries
+loki enterprise audit tail
 ```
 
 ### Format Issues

package/docs/test-scenarios/edge-cases.md

@@ -1,7 +1,7 @@
 # Loki Mode Edge Case Test Scenarios
 
 Agent 12 - Scenario Writing: Edge Cases, Error Paths, Concurrent Usage
-Version: v6.71.1 | Date: 2026-03-24
+Date: 2026-03-24
 
 ---
 
@@ -55,7 +55,7 @@ Version: v6.71.1 | Date: 2026-03-24
 **Given** an autonomous session is running at iteration 15 of 1000
 **When** the network connection drops (DNS resolution fails, API timeout)
 **Then** the system should:
-- The provider CLI (claude/codex/gemini) exits with a non-zero exit code
+- The provider CLI (claude/codex/cline/aider/opencode) exits with a non-zero exit code
 - `run_autonomous()` captures the exit code in `$exit_code` (run.sh:9406)
 - Rate limit detection runs via `is_rate_limited()` (checks for common rate limit strings)
 - If failover is enabled (`LOKI_FAILOVER=true`), attempt `attempt_provider_failover()`

package/docs/test-scenarios/enterprise-scenarios.md

@@ -52,7 +52,7 @@ Source: `.github/workflows/loki-ci-example.yml:41-44`
 ### TW-04: Handoff Between Human and AI Coding
 
 ```
-GIVEN a loki autonomous session is running (iteration 5 of 20)
+GIVEN a Loki autonomous session is running (iteration 5 of 20)
   AND the human developer notices a design issue
 WHEN the developer creates .loki/PAUSE signal file
 THEN the session pauses after the current RARV iteration completes
@@ -66,7 +66,7 @@ Source: `autonomy/run.sh:7897` (check_human_intervention)
 ### TW-05: Project Template Sharing Across Team
 
 ```
-GIVEN the team uses loki templates (13 types: saas, cli, discord-bot, etc.)
+GIVEN the team uses Loki PRD templates (saas, cli, discord-bot, etc.)
   AND the team lead wants to standardize on a custom template
 WHEN the lead creates a PRD template at templates/custom-team.md
   AND commits it to the shared repository
@@ -195,7 +195,7 @@ Source: `skills/parallel-workflows.md`
 ### GI-02: Meaningful AI Commit Messages
 
 ```
-GIVEN a loki session has completed a RARV iteration
+GIVEN a Loki session has completed a RARV iteration
   AND the iteration modified 4 files
 WHEN the autonomous system commits changes
 THEN the commit message follows the format: "<type>: <description>"
@@ -437,7 +437,7 @@ Source: `.github/workflows/release.yml:238-496`
 
 ```
 GIVEN the dashboard WebSocket endpoint is available at /ws
-  AND a CI pipeline is running a loki session
+  AND a CI pipeline is running a Loki session
 WHEN the WebSocket client connects
 THEN real-time events are streamed including:
      - iteration_start / iteration_complete

package/docs/v10/BOARD.md

@@ -629,7 +629,9 @@ Source: ~/git/autonomi-dev/research/2026-09-30-adoption/SWARM-PROMPT-ADOPTION.md
 | E-159 | Pre-existing secret-scan gaps found by the E-157 r2 opus reviewer: (a) an evil merge, a merge commit whose OWN content adds a secret (merge -s ours --no-commit, token in the merge commit), is invisible to both the PARENT..SHA range scan and the --all scan (only `gitleaks dir` found it); (b) pinned gitleaks 8.30.0 exits 0 when its internal git log fails (invalid range), a latent fail-open. Fix: --diff-merges=first-parent (or -m) in --log-opts for both modes or a working-tree scan at the release SHA; guard `git rev-list RANGE` success or treat `[git] fatal` as failure | scripts/security-audit-gitleaks.sh, workflows, tests | HIGH | evil-merge and bad-range fixtures fail the scan | merged@2026-10-01T03:03Z | CI-health engineer after E-157 r3; r1 opus REJECT 5f33451d: stdin merge scan false-positives on real history (v10.5.13..14 rc 1), Wall checks skip in CI |
 | E-160 | D46 runner contention (peer steer 02:11Z): a green train SHA fast-forwarded to main re-runs Tests (8 shards), Bun Parity, Security Audit and First-run gate on the identical SHA, doubling runner load and queueing the next train. Proposal: on push to main, a first job checks for a successful run of the same workflow at the same SHA from a train/** push and, if found, exits success recording the reused run id (D28: same SHA = same tree); any SHA not train-tested runs in full. CTO call FIRST: OPERATING-MODEL says "Tier B full verification on every main commit (never cancelled on main)"; confirm reuse does not weaken Release required-ci, branch-conditional steps (train vs main), or the Security Audit range (base tag config). Sequence after E-157 r4 (same files) | .github/workflows/test.yml, bun-parity.yml, security-audit.yml, tests/test_release_required_ci.py | HIGH | main push of a train-green SHA records reuse and finishes in under 1 min; an untested SHA runs in full; a train-red SHA is not reused | ready@2026-10-01T02:10Z | CTO decision first; after E-157 |
 | E-161 | INCIDENT 02:46Z: an opus reviewer ran `git checkout --detach <tag>` x7 plus a `.gitleaksignore` overwrite in the SHARED main checkout (reflog 02:46:04Z to 02:46:38Z). Cause: its run-owned clone dir was deleted, the next `cd` into a new clone failed, and the shell cwd fell back to the main checkout; every later command ran there. Restored by the Chief of Staff (`git checkout main`, fafe50dd, clean). Guard: v10-guard.sh (PreToolUse) blocks `git checkout`/`git switch`/`git reset`/`git worktree remove` and writes to tracked files when cwd resolves to the main checkout and the caller is an agent (not the leader session); agent prompts use `cd DIR` followed by an exit-on-failure check. Test: a hook test with cwd=main checkout blocks a detached checkout and allows it in a worktree | scripts/v10-guard.sh, tests | HIGH | detached checkout in main checkout blocked; same in a worktree allowed | ready@2026-10-01T02:47Z | GUARDS.md entry |
-| E-162 | Founder "faster" (03:05Z): slice CI runs only Tier A plus diff-selected suites (the existing Tier A selection), Bun Parity and the structural guards; the full 8-shard Tests stays on train/** and main, and the train stays the release verdict. Frees runners and targets about 2 min slice CI | .github/workflows/test.yml (slice-* job matrix only), tests | HIGH | slice-* push runs no 8-shard matrix; train/** and main still run all 8 shards; a slice touching a suite runs that suite | ready@2026-10-01T03:01Z | after E-157 r4 (same file) |
+| E-162 | Founder "faster" (03:05Z): slice CI runs only Tier A plus diff-selected suites (the existing Tier A selection), Bun Parity and the structural guards; the full 8-shard Tests stays on train/** and main, and the train stays the release verdict. Frees runners and targets about 2 min slice CI | .github/workflows/test.yml (slice-* job matrix only), tests | HIGH | slice-* push runs no 8-shard matrix; train/** and main still run all 8 shards; a slice touching a suite runs that suite | merged@2026-10-01T05:22Z | after E-157 r4 (same file) |
+| E-165 | tests/test-mirofish-integration.sh line 413 runs `autonomy/loki start --no-mirofish` in the repo root: a live autonomous build that ran about 45 min, switched a worktree branch to loki/session-* and committed a docs change (found by DOC-02). Guard: the test must run against a run-owned fixture repo with a stub provider and LOKI_NO_BROWSER=1, never the repo root; add a structural guard that no test launches start/run against REPO_ROOT | tests/test-mirofish-integration.sh, a structural guard | HIGH | the test never runs loki start in the repo root; guard catches a planted case | ready@2026-10-01T04:07Z | P0 guard (D26) |
+| E-166 | Jira auto-sync never starts: src/integrations/sync-subscriber.js builds JiraApiClient without the required email and apiToken, so LOKI_JIRA_URL plus LOKI_JIRA_TOKEN do nothing (DOC-02 added a known-issue note to the setup docs). Fix the wiring or remove the advertised auto-sync | src/integrations/sync-subscriber.js, tests | MEDIUM | with env set, the subscriber constructs a working client (mocked API) | ready@2026-10-01T04:07Z | none |
 | D49-auto | Auto-promote to latest on Post-Release Smoke success (founder D49) | .github/workflows/promote.yml, tests/test_release_next_tag.py | HIGH | smoke-success from Release promotes; manual smoke never promotes; not-lower guard | merged@2026-10-01T03:03Z | opus APPROVE 5510b8c8. Follow-ups (D49-auto-b): not-lower guard fails OPEN on an npm error (make it fail closed); loki-mode-sdk latest has no not-lower guard; a newer queued promote can replace a pending one in a release burst |
 | D51-A3 | Headless `loki backlog owner/repo --all/--label/--issues` plus loki.yaml (schema, validator, env overrides) | autonomy/lib/backlog.py, autonomy/lib/loki_yaml.py, autonomy/loki, schemas/loki-yaml.schema.json, tests/test-backlog.sh | HIGH | backlog 47/0 | merged@2026-10-01T03:11Z | sonnet APPROVE 14ff9ae2; follow-up D51-A3b: `loki_yaml.py show` echoes a token pasted into git.token_env (redact x-secret-ref fields); no-parser test case; re-run of a failed issue discards its kept worktree |
 | D51-A4 | Slack on the v10 path (PR opened, BLOCKED, finished), webhook from the env var named by LOKI_SLACK_WEBHOOK_ENV, URL redacted, 5s bounded post | loki-ts/src/e10ext/slack_events.ts, engine10/supervisor.ts, tests | MEDIUM | slack tests 40/0 | merged@2026-10-01T03:11Z | sonnet APPROVE adb838b2; one labelled test message after it ships |
@@ -640,20 +642,20 @@ Source: ~/git/autonomi-dev/research/2026-09-30-adoption/SWARM-PROMPT-ADOPTION.md
 | A-115 | TIER 0 (steer 22:50Z). FALSE VERIFIED ON MAIN (A-112 opus reviewer, c10 on 275b4fc0): a conftest.py that skips the target test (and the unrelated red one) seals VERIFIED rc=0, "2 passed, 2 skipped", nothing disclosed. Seal accuracy: a relevant check with more skipped tests than base, or a diff touching conftest.py / pytest.ini / pyproject [tool.pytest] / jest or node test config, must not count as a pass or as progress; list it in NOT PROVEN | loki-ts/src/engine10/stages/verify.ts, failures.ts, tests | HIGH | c10 and e9 fixtures seal FAILED or NOT VERIFIED | released@2026-10-01T00:52Z | core at the 5000 cap: needs an offset (A-150) Released in v10.5.13 (merge bdb332e3 is an ancestor of v10.5.13). |
 | A-115b | A-115 opus notes: (1) an honest fix that also appends a new test to a relevant test file, in a repo with an unrelated red test, ends STALLED/FAILED instead of PARTIAL: the edited file is excluded from progress so the unrelated red is never subtracted; allow progress when the file's pre-existing target ids went red to green; (2) the node base-count fallback sums every `pass N`/`fail N` line, so a base test printing them inflates the count (safe-direction false PARTIAL); take the last pass and last fail lines | loki-ts/src/engine10/stages/verify.ts, verify_weak.test.ts | HIGH | both fixtures | released@2026-10-01T01:53Z | Released in v10.5.15 (merge 945f58ec is an ancestor of v10.5.15). |
 | A-119 | P0 FALSE VERIFIED ON MAIN (A-115b opus reviewer, reproduced on bba2e5ec): rename the target test file and weaken its expectation (sum.test.js => sum.spec.test.js with 6 changed to 5), add a comment to sum.js: rc=0 Outcome VERIFIED, receipt shows node:sum.spec.test.js pass, sum.js still buggy. verify only sees relevant test files that still exist on head; seal writes `weakened test: sum.test.js` (seal.ts:205) but that line never downgrades the verdict. Fix: seal's `weakened test:` downgrades to PARTIAL like verify's not_proven | loki-ts/src/engine10/stages/seal.ts, tests | HIGH | rename-and-weaken fixture: not VERIFIED, rc!=0 | released@2026-10-01T01:53Z | Tier 0 Released in v10.5.15 (merge c41a2b83 is an ancestor of v10.5.15). |
-| A-119b | A-119 opus review (REJECT on pre-existing holes, A-119 landed as a strict improvement): weakening still ends VERIFIED via (1) a helper file a base test imports (eq=()=>{}), (2) snapshot or fixture edits (__snapshots__/*.snap, tests/fixtures/*.json), (3) tests isTestFile (testmap.ts:51) does not recognise: __tests__/*.js, mocha test/*.js, cargo tests/*.rs, including rename to .bak. Also: verdictOf returns ALREADY_SATISFIED before the weakened downgrade when implement says already_done; package.json jest testPathIgnorePatterns and vite.config.ts test.exclude skip config detection. Fix: widen the seal.ts weakTests predicate to any changed/deleted base path under test/, tests/, __tests__/, __snapshots__/, fixtures dirs plus non-test files a base test imports; check weakened before the already_done early return; add vite.config and in-block jest keys to CFG detection | loki-ts/src/engine10/stages/seal.ts, verify.ts (CFG only), tests | HIGH | each repro gives not-VERIFIED; source-only fix and new test stay VERIFIED | building@2026-10-01T02:18Z | |
+| A-119b | A-119 opus review (REJECT on pre-existing holes, A-119 landed as a strict improvement): weakening still ends VERIFIED via (1) a helper file a base test imports (eq=()=>{}), (2) snapshot or fixture edits (__snapshots__/*.snap, tests/fixtures/*.json), (3) tests isTestFile (testmap.ts:51) does not recognise: __tests__/*.js, mocha test/*.js, cargo tests/*.rs, including rename to .bak. Also: verdictOf returns ALREADY_SATISFIED before the weakened downgrade when implement says already_done; package.json jest testPathIgnorePatterns and vite.config.ts test.exclude skip config detection. Fix: widen the seal.ts weakTests predicate to any changed/deleted base path under test/, tests/, __tests__/, __snapshots__/, fixtures dirs plus non-test files a base test imports; check weakened before the already_done early return; add vite.config and in-block jest keys to CFG detection | loki-ts/src/engine10/stages/seal.ts, verify.ts (CFG only), tests | HIGH | each repro gives not-VERIFIED; source-only fix and new test stay VERIFIED | rejected@2026-10-01T05:12Z | |
 | A-117 | FALSE VERIFIED IN `loki verify` (A-130 r2 opus reviewer): on a run whose events.jsonl was tampered (append, edit, truncate, delete), the run now ends FAILED (A-130) but the receipt on disk still says VERIFIED with no tamper mark, because the worker sealed it before the supervisor detected the tamper; `loki verify` prints verdict: VERIFIED rc=0. Fix: record the tamper on the receipt via the registered receipt.addendum event (hash-chained) or have verify check the event log hash; verify must say TAMPERED and exit non-zero | loki-ts/src/engine10/verify_cmd.ts, supervisor.ts or seal.ts, tests | HIGH | tampered-log fixture: loki verify TAMPERED rc!=0 | merged@2026-10-01T02:50Z | after A-130 (supervisor.ts); r2: opus REJECT, tail truncation erases post-seal tamper, fix = signed final log line |
-| A-118 | Exit-honest policy gap on the DEFAULT path (A-115 r2 finding): legacy `loki quick` prints `Evidence Receipt: NOT VERIFIED` yet exits rc 0 on a run whose target test was skipped; G1 exit-honest counts a skipped test as green, so it does not catch this. CTO call: should legacy quick exit non-zero on NOT VERIFIED when a relevant test was skipped/weakened, and should G1 count skipped as not-green? | autonomy/run.sh (quick exit path), scripts/first-run-gate.sh G1 | HIGH | skipped-target legacy run exits non-zero; G1 treats skipped as not green | building@2026-10-01T02:15Z | D47 decided: rc 3 on tests_integrity failed (skip added, runner config changed, test file deleted/renamed); assertion edits disclosed rc 0; G1 green needs pass 2 fail 0, 9b asserts rc 3. Files: proof-generator.py, run.sh after generate_proof_of_run, first-run-gate.sh, docs/exit-codes.md. Blocks promote of `latest`; built df404970, opus review |
+| A-118 | Exit-honest policy gap on the DEFAULT path (A-115 r2 finding): legacy `loki quick` prints `Evidence Receipt: NOT VERIFIED` yet exits rc 0 on a run whose target test was skipped; G1 exit-honest counts a skipped test as green, so it does not catch this. CTO call: should legacy quick exit non-zero on NOT VERIFIED when a relevant test was skipped/weakened, and should G1 count skipped as not-green? | autonomy/run.sh (quick exit path), scripts/first-run-gate.sh G1 | HIGH | skipped-target legacy run exits non-zero; G1 treats skipped as not green | merged@2026-10-01T05:12Z | D47 decided: rc 3 on tests_integrity failed (skip added, runner config changed, test file deleted/renamed); assertion edits disclosed rc 0; G1 green needs pass 2 fail 0, 9b asserts rc 3. Files: proof-generator.py, run.sh after generate_proof_of_run, first-run-gate.sh, docs/exit-codes.md. Blocks promote of `latest`; built df404970, opus review |
 | A-112b | A-112 readability debt: subtractBase in verify.ts was folded to reach 4999 of 5000 core lines (9 lines over 200 chars, longest 347; un/progress/base-run loop each on one line). Unfold when A-150 frees budget; no behaviour change | loki-ts/src/engine10/stages/verify.ts | MEDIUM | budget test plus verify_prered unchanged | ready@2026-09-30T22:37Z | after A-150 |
 | A-113b | A-110 opus notes on A-113: (1) under the CLI invoker (LOKI_E10_INVOKER=cli) the provider child stderr never reaches the fatal classifier (the *-impl.stderr.log is empty), so a credit/auth failure printed on plain stderr gives stop:null and burns the fix rounds; (2) machine.ts re-records the previous signature when a verify crashes, so a crashed verify counts toward a stall. Fix both in session.ts/machine.ts, with end-to-end tests through the real worker | loki-ts/src/engine10/session.ts, machine.ts, tests | HIGH | CLI stderr credit line stops fatal; crashed verify does not count as a stall repeat | released@2026-10-01T01:19Z | keep the A-110 escalated emit; the A-110 reviewer plugin probe is a good e2e template Released in v10.5.14 (merge 0377398d is an ancestor of v10.5.14). |
 | A-121 | v10 signs and verifies natively (item 3) | see plan A-121 | HIGH | first-run-gate assertion per plan card | released@2026-10-01T00:52Z | Wave per plan section 5; one writer per file. Released in v10.5.13 (merge 08b31271 is an ancestor of v10.5.13). |
 | A-122 | Delete the GPG signing layer (item 3, deletion) | see plan A-122 | HIGH | first-run-gate assertion per plan card | released@2026-10-01T00:52Z | Wave per plan section 5; one writer per file. Released in v10.5.13 (merge cb738c36 is an ancestor of v10.5.13). |
-| A-121b | A-121 opus note: a receipt downgrade exits 0. Anyone can edit the body, recompute receipt_sha256 and null the jwt to get UNSIGNED rc 0 on `loki verify`, and the legacy deploy gate refuses UNSIGNED but the v10 verify does not. Decide the signed-by-default policy: once a local key exists, UNSIGNED on a receipt from this machine exits non-zero (or the receipt records its kid outside the hashed body) | loki-ts/src/engine10/verify_cmd.ts, stages/seal.ts, tests | HIGH | downgrade fixture exits non-zero | building@2026-10-01T02:33Z | D47 decided: UNSIGNED exits 3 on both engines (verify_cmd.ts EXIT_BY_VERDICT, autonomy/verify.sh _verify_receipt_digest), --allow-unsigned / LOKI_VERIFY_ALLOW_UNSIGNED=1 accepts with explicit line; update tests/test-engine10-live-pr.sh 115-122; verify never creates a key |
+| A-121b | A-121 opus note: a receipt downgrade exits 0. Anyone can edit the body, recompute receipt_sha256 and null the jwt to get UNSIGNED rc 0 on `loki verify`, and the legacy deploy gate refuses UNSIGNED but the v10 verify does not. Decide the signed-by-default policy: once a local key exists, UNSIGNED on a receipt from this machine exits non-zero (or the receipt records its kid outside the hashed body) | loki-ts/src/engine10/verify_cmd.ts, stages/seal.ts, tests | HIGH | downgrade fixture exits non-zero | released@2026-10-01T03:00Z | D47 decided: UNSIGNED exits 3 on both engines (verify_cmd.ts EXIT_BY_VERDICT, autonomy/verify.sh _verify_receipt_digest), --allow-unsigned / LOKI_VERIFY_ALLOW_UNSIGNED=1 accepts with explicit line; update tests/test-engine10-live-pr.sh 115-122; verify never creates a key |
 | A-121c | A-121b opus finding B: legacy `loki verify` passes a WELL-FORMED token with an unknown kid at rc 0 (`attestation: UNCHECKED`, `VERDICT: VERIFIED`) with or without the local key; engine10 gives rc 2. A forger can always mint such a token, so on legacy a downgrade-to-foreign-kid is a pass. D47 kept legacy UNCHECKED unchanged because it also covers honest cross-machine verification. CTO call: make legacy UNCHECKED non-zero (parity with engine10 rc 2), now that D48 row 2 adds `loki verify --pubkey` as the honest cross-machine path? Also: a missing .loki/state/last-proof-id.txt makes legacy verify skip the receipt check entirely and pass (pre-existing, A-134) | autonomy/loki (_deploy_receipt_verdict, verify), tests | HIGH | unknown-kid forged token exits non-zero on legacy; honest cross-machine path documented | ready@2026-10-01T02:33Z | CTO decision first; after A-121b |
 | A-110 | One named outcome, fixed exit ladder, --json (items 1 and 5) | see plan A-110 | HIGH | first-run-gate assertion per plan card | released@2026-10-01T00:52Z | Wave per plan section 5; one writer per file. Released in v10.5.13 (merge 47ac1ccc is an ancestor of v10.5.13). |
 | A-112 | Baseline subtract: judge only the delta (item 5) | see plan A-112 | HIGH | first-run-gate assertion per plan card | released@2026-10-01T00:52Z | Wave per plan section 5; one writer per file. Released in v10.5.13 (merge 69f1a910 is an ancestor of v10.5.13). |
 | A-123 | Doctor: only the selected provider blocks, one Ready line (item 3) | see plan A-123 | MEDIUM | first-run-gate assertion per plan card | released@2026-10-01T00:52Z | Wave per plan section 5; one writer per file. Released in v10.5.13 (merge 275b4fc0 is an ancestor of v10.5.13). |
 | A-134 | Legacy: receipt after the final commit, chatter behind --verbose (item 2) | see plan A-134 | MEDIUM | first-run-gate assertion per plan card | released@2026-10-01T00:52Z | Wave per plan section 5; one writer per file. Released in v10.5.13 (merge 7d3edf96 is an ancestor of v10.5.13). |
-| A-134b | A-134 opus notes: (1) standalone autonomy/verify.sh prints no attestation line (only `loki verify` has _deploy_receipt_verdict); print `attestation: UNCHECKED (run via loki verify)` instead of silence; (2) the quiet failure tail grep `[Ff]ailed` matched the RALPH system-prompt line and printed ~1.5k chars; anchor to `^\[(ERROR|WARN)\]` or cap line length; (3) the quiet inner run starts as a background job so its stdin is /dev/null even from a TTY: pause-mode keypress resume changes for quiet runs; (4) `loki quick --verbose` is also the A-122 cmd_quick flag, done | autonomy/verify.sh, autonomy/run.sh | MEDIUM | each note has a test | building@2026-10-01T02:24Z | |
+| A-134b | A-134 opus notes: (1) standalone autonomy/verify.sh prints no attestation line (only `loki verify` has _deploy_receipt_verdict); print `attestation: UNCHECKED (run via loki verify)` instead of silence; (2) the quiet failure tail grep `[Ff]ailed` matched the RALPH system-prompt line and printed ~1.5k chars; anchor to `^\[(ERROR|WARN)\]` or cap line length; (3) the quiet inner run starts as a background job so its stdin is /dev/null even from a TTY: pause-mode keypress resume changes for quiet runs; (4) `loki quick --verbose` is also the A-122 cmd_quick flag, done | autonomy/verify.sh, autonomy/run.sh | MEDIUM | each note has a test | merged@2026-10-01T05:22Z | |
 | A-134c | A-134b r1 review finding: provider call sites in autonomy/run.sh (mainline claude -p at about 25455/25460, provider_invoke_argv about 1050/1053) do not redirect stdin, so under LOKI_VERBOSE=1 (and any non-quiet path) a parent stdin pipe that never closes blocks `claude -p` reading stdin (pre-existing). Fix: `< /dev/null` at provider invocations that pass the prompt as an argument | autonomy/run.sh (provider call sites only), providers/*.sh, tests | MEDIUM | never-closing stdin pipe: verbose `loki quick` completes under timeout 60 | ready@2026-10-01T01:37Z | |
 | A-130 | v10 quiet by default (item 2) | see plan A-130 | MEDIUM | first-run-gate assertion per plan card | released@2026-10-01T01:19Z | Wave per plan section 5; one writer per file. Released in v10.5.14 (merge a518bfea is an ancestor of v10.5.14). |
 | A-130b | A-130 Reason line prints first_error from a failing check verbatim (capped at 200 chars, control chars stripped) but unredacted: a `ghp_` token in a test failure line reaches the terminal. No TS redactor is reachable from engine10 core (only autonomy/lib/proof_redact.py). Port the token patterns to a small TS helper outside core or redact first_error where it is captured in verify | loki-ts/src (util), verify.ts or output.ts, tests | MEDIUM | ghp_/sk- token in first_error prints redacted | released@2026-10-01T02:27Z | ; sonnet APPROVE be50510f (redaction before cap, parity with proof_redact.py) Released in v10.5.16 (merge f214a0fa is an ancestor of v10.5.16). |

package/docs/v10/GUIDE.md

@@ -140,9 +140,11 @@ provider names (`claude`, `codex`, `cline`, `aider`); it is not supported.
 
 Once v10 becomes the default (docs/v10/DECISIONS.md, D29), `loki`, `loki
 status`, `loki verify` and `loki dashboard` with no `LOKI_ENGINE` set will
-mean the v10 commands described above. The previous engine stays fully
-reachable: `loki legacy <args>` and `LOKI_ENGINE=legacy` both route to it,
-unchanged. Nothing is removed at the flip.
+mean the v10 commands described above. The previous engine stays
+reachable through `LOKI_ENGINE=legacy` (bin/loki sends every value other
+than `v10` to it), unchanged. Nothing is removed at the flip. A separate
+legacy alias command is planned (docs/v10/ENGINE.md, E-31) but is not on
+main.
 
 That flip has not happened on main as of this guide. The opt-in line near
 the top of this file and of README.md's section is the one place that