[codex] expose repository discovery metadata

[moose-lab]

Summary

• Add agent-facing and LLM/crawler discovery entry points for DevLog.
• Document DeepWiki and Zread indexing status without making .devin/wiki.json a baseline requirement.
• Add a repository-discovery guard test and package metadata for public indexing.

Validation

• git diff --staged --check
• TZ=Asia/Shanghai bun run test (275/275 pass)
• bun run typecheck
• Pre-commit hook reran git diff --cached --check && bun run typecheck && TZ=Asia/Shanghai bun run test successfully.

[claude]

Claude finished @moose-lab's task in 1m 16s —— View job

---

PR Review

• Gather context
• Read changed files
• Review for correctness, cross-platform safety, security, type safety, and test coverage
• Post findings

---

Findings

• [should-fix] src/core/__tests__/repository-discovery.test.ts:68-71 — The wiki.json content assertions (wiki.pages?.some(page => page.title === "Architecture Overview") etc.) are hardcoded title checks that only run when .devin/wiki.json happens to exist. If that optional file is ever added with different titles, the test fails with no warning. Since the file is explicitly optional, either remove the content assertions entirely (just validate JSON parses and has repo_notes/pages keys), or add a comment explaining the expected schema. As written, anyone adding .devin/wiki.json with different page titles will hit a surprise test failure. Fix this →

• [should-fix] src/core/__tests__/repository-discovery.test.ts:10 — const root = process.cwd() makes all file resolution dependent on the working directory at test execution time. The AGENTS.md convention (TZ=Asia/Shanghai bun run test) implies running from the repo root, so this works in practice, but a CWD change (e.g., running bun test src/... from a subdirectory) produces silent wrong-path errors. Consider anchoring to new URL('../../../..', import.meta.url).pathname for robustness.

• [nit] src/core/__tests__/repository-discovery.test.ts:80 — assert.match(readme, /optional/i) is too loose; the word "optional" could appear in any sentence. A tighter pattern like /\.devin\/wiki\.json.*optional|optional.*\.devin\/wiki\.json/is ties the assertion to the actual claim. Currently passes, but won't catch regressions if the phrasing changes.

• [nit] AGENTS.md:7 — "Superpowers v5.1.0" will rot fast. Since this is a guide file agents are supposed to keep current, pinning a version here may cause confusion if the plugin updates without the file being updated. Consider dropping the version number or noting it should be kept in sync.

---

Summary: This is a clean documentation/metadata PR. The guard-test pattern is well-chosen for ensuring discovery files stay in place. No correctness bugs, no security issues, no unsafe casts worth blocking on. The two should-fix items are about test fragility, not runtime behavior.

Verdict: APPROVE (with the wiki.json assertion cleanup recommended before the file is ever committed to this repo)