feat: upstream PR #23 stack onto purified (#1274 DuckDB + #1251 artifact + #1284 Omnigent)

[diazMelgarejo]

CI & integration notes (appended)

Tip: 2742addb — docs strict-link fixes for zensical-excluded paths (ARCHITECTURE.md superpowers links, rename-catalogue script link).

Parallel agent fixes already on branch:

• ec11bca6 — periscope-v1-plan.md machine-local path → ./v1-ui-spec.md
• 821b9855 — visualizer planning docs → periscope-spec.md
• 494beba5 — commit-clean test harness aligned with orama guard bundle

Docs orphan-branch mirrors (fork origin, reference-only — not in this PR diff):

Branch	SHA	Upstream match
docs-assets	7c7dbd0f	kenn-io/agentsview ✓
docs-generated-assets	71d86172	kenn-io/agentsview ✓

hydrate-assets.sh now resolves from origin without upstream fallback. Refresh mirrors the same way as agentsview: re-push upstream SHAs via docs/assets/update-static-assets-branch.sh / docs/screenshots/update-generated-assets-branch.sh.

CI run 30427743559 on 2742addb: docs, scripts, frontend, frontend-node-25, integration, e2e, lint, coverage, Desktop Unit Tests (Windows) — pass; Go Test (ubuntu/windows) and Benchmark Gate still pending at last check.

  

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 988a5f8f-8736-4c77-b677-07728b5eca81

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[ecc-tools]

Analyzing 200 commits...

[ecc-tools]

Analysis Complete

Generated ECC bundle from 1 commits | Confidence: 50%

View Pull Request #27

Repository Profile

Attribute	Value
Language	Go
Framework	Not detected
Commit Convention	conventional
Test Directory	separate

Changed Files (15)

Metric	Value
Files changed	15
Additions	396
Deletions	5

Top hotspots

Path	Status	+/-
internal/config/paths.go	added	+75 / -0
internal/config/config_test.go	modified	+53 / -0
internal/server/resume_handler_test.go	modified	+40 / -0
internal/config/config_duckdb_tilde_test.go	added	+37 / -0
internal/pathutil/home_test.go	added	+35 / -0

Top directories

Directory	Files	Total changes
internal/config	4	194
cmd/periscope	7	103
internal/pathutil	2	63
internal/server	2	41

Analysis Depth Readiness (commit-history, 7%)

ECC Tools uses this to decide whether recommendations should stay at commit-history/setup guidance or expand into CI, security, harness, reference-set, AI-routing, and team backlog work.

Area	Status	Evidence / Next Step
Commit history	Partial	1 commits sampled
CI/CD signals	Missing	Add workflow files or CI troubleshooting evidence so ECC Tools can reason about pipeline setup.
Security evidence	Missing	Add AgentShield, audit, SARIF, SBOM, or security review evidence so recommendations can cover security posture.
Harness configuration	Missing	Add Claude, Codex, OpenCode, Zed, dmux, MCP, plugin, or cross-harness config evidence for harness-agnostic recommendations.
Reference/eval evidence	Missing	Add fixtures, golden traces, reference sets, or evaluator benchmarks so deeper recommendations have regression evidence.
AI routing and cost controls	Missing	Add model-routing, budget, usage, or cost-control files before relying on AI-heavy automation recommendations.
Team handoff and project tracking	Missing	Add roadmap, runbook, project, Linear, or follow-up tracking docs so generated work can land in a team queue.

Reference Set Readiness (0/7, 0%)

Area	Status	Evidence / Next Step
Deep analyzer corpus	Missing	Add analyzer fixture, golden, benchmark, or reference-set files that can catch analyzer regressions.
RAG/evaluator comparison	Missing	Add retrieval or evaluator reference-set comparison fixtures with expected ranking behavior.
PR salvage/review corpus	Missing	Add stale-PR, review-thread, reopen-flow, or salvage reference cases for queue cleanup automation.
Discussion triage corpus	Missing	Add public discussion triage fixtures, golden cases, or reference sets for informational, answered, and no-response classifications.
Harness compatibility	Missing	Add cross-harness, adapter-compliance, or harness-audit evidence for Claude, Codex, OpenCode, Zed, dmux, and agent surfaces.
Security evidence	Missing	Attach security evidence such as SBOMs, SARIF, audit reports, or AgentShield evidence packs.
CI failure-mode evidence	Missing	Add captured CI failure logs, dry-run fixtures, or troubleshooting docs for common workflow failure modes.

Likely Future Issues (4)

Severity	Signal	Why it may show up
HIGH	Regression coverage may lag behind the diff	14 generic code paths changed; 0 test files changed
MEDIUM	Runtime config changes may ship without example or template updates	4 runtime config paths changed; 0 example or template config files changed
HIGH	Auth or permission changes may ship without security regression coverage	1 auth/permission paths changed; 0 auth-focused integration or e2e tests changed
HIGH	Security-sensitive changes may ship without scanner evidence	1 security-sensitive paths changed; 0 security scanner or security-focused validation artifacts changed

• Regression coverage may lag behind the diff: The PR changes multiple code paths but does not touch any obvious test files.
• Runtime config changes may ship without example or template updates: The PR changes runtime config or deployment settings but does not update any obvious example env file or config template.
• Auth or permission changes may ship without security regression coverage: The PR changes auth, session, middleware, or permission-sensitive files without touching any obvious auth-focused integration or end-to-end tests.
• Security-sensitive changes may ship without scanner evidence: The PR touches billing, secrets, auth, webhooks, agent, or CI-sensitive surfaces without adding obvious security scanner, code scanning, or security-focused validation evidence.

Suggested Follow-up Work (4)

Type	Suggested title	Targets
PR	test: add regression coverage for cmd/periscope/duckdb.go + cmd/periscope/import.go	cmd/periscope/duckdb.go, cmd/periscope/import.go
PR	chore: sync config templates for internal/config/config.go + internal/config/config_duckdb_tilde_test.go	internal/config/config.go, internal/config/config_duckdb_tilde_test.go
PR	test: add auth coverage for cmd/periscope/session.go	cmd/periscope/session.go
PR	security: add scanner evidence for cmd/periscope/session.go	cmd/periscope/session.go

• test: add regression coverage for cmd/periscope/duckdb.go + cmd/periscope/import.go: Backfill regression coverage before another change set lands on the touched code paths.
• chore: sync config templates for internal/config/config.go + internal/config/config_duckdb_tilde_test.go: Backfill example env files or config templates before a fresh setup drifts from the shipped runtime surface.
• test: add auth coverage for cmd/periscope/session.go: Backfill auth or permission regression coverage before another access-control change lands on the touched surface.
• security: add scanner evidence for cmd/periscope/session.go: Backfill explicit scanner or code-scanning evidence before another security-sensitive change lands on the touched surface.

Copy-ready bodies

test: add regression coverage for cmd/periscope/duckdb.go + cmd/periscope/import.go

## Summary
- Add regression coverage for the recently touched code paths before more changes stack on top.

## Why
- Backfill regression coverage before another change set lands on the touched code paths.

## Touched paths
- `cmd/periscope/duckdb.go`
- `cmd/periscope/import.go`

## Validation
- Add or extend focused tests that exercise the touched paths.
- Run the affected test suite and verify the new coverage closes the gap.

chore: sync config templates for internal/config/config.go + internal/config/config_duckdb_tilde_test.go

## Summary
- Update the example env files, sample configs, or deployment templates that should mirror the changed runtime configuration surface.

## Why
- Backfill example env files or config templates before a fresh setup drifts from the shipped runtime surface.

## Touched paths
- `internal/config/config.go`
- `internal/config/config_duckdb_tilde_test.go`

## Validation
- Update the repo example env file or config template that should reflect the new runtime settings.
- Run the setup, boot, or deployment validation flow that depends on the changed config surface.

test: add auth coverage for cmd/periscope/session.go

## Summary
- Add auth, session, or permission regression coverage for the recently changed security-sensitive surface.

## Why
- Backfill auth or permission regression coverage before another access-control change lands on the touched surface.

## Touched paths
- `cmd/periscope/session.go`

## Validation
- Add or extend integration / e2e coverage for the changed auth, session, middleware, or permission surface.
- Exercise allowed and denied flows, invalid or expired credentials, or equivalent access-control boundary cases.

security: add scanner evidence for cmd/periscope/session.go

## Summary
- Add security scanner or code-scanning evidence for the recently changed security-sensitive surface.

## Why
- Backfill explicit scanner or code-scanning evidence before another security-sensitive change lands on the touched surface.

## Touched paths
- `cmd/periscope/session.go`

## Validation
- Run or add the relevant security scanner, code scanning, secret scanning, or dependency/security review check for the touched surface.
- Attach the scanner output, SARIF/code-scanning result, or focused security regression test to the follow-up PR.
- Confirm the changed auth, billing, webhook, secret-handling, agent, or CI surface has an explicit pass/fail gate.

Generated Instincts (15)

Domain	Count
git	4
code-style	9
testing	2

After merging, import with:

/instinct-import .claude/homunculus/instincts/inherited/periscope-instincts.yaml

Files

• .claude/ecc-tools.json
• .claude/skills/periscope/SKILL.md
• .agents/skills/periscope/SKILL.md
• .agents/skills/periscope/agents/openai.yaml
• .claude/identity.json
• .codex/config.toml
• .codex/AGENTS.md
• .codex/agents/explorer.toml
• .codex/agents/reviewer.toml
• .codex/agents/docs-researcher.toml
• .claude/homunculus/instincts/inherited/periscope-instincts.yaml

---

_{ECC Tools | Everything Claude Code}