github-featured/wanshuiyin--auto-claude-code-research-in-sleep

Files

T

SyntaxSmith 95308a6a82 chore: point #358 placeholder references at the actual PR number (#366 )

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-14 19:46:23 +08:00

6.3 KiB

Raw Permalink Blame History

Wiki helper resolution chain

Canonical resolution chain for the research-wiki helper. Used by every SKILL that touches the wiki — never hard-code python3 tools/research_wiki.py, because that silently fails when <project>/tools/ is not on disk (the post-install_aris.sh default), exactly the failure mode that left a real user's research-wiki/ empty for a week.

The chain

cd "$(git rev-parse --show-toplevel 2>/dev/null || pwd)" || exit 1
ARIS_REPO="${ARIS_REPO:-$(awk -F'\t' '$1=="repo_root"{print $2; exit}' .aris/installed-skills.txt 2>/dev/null)}"
# Layer 4: global pointer file written by the installer/updater at
# ~/.aris/repo (#366) — covers global copy-installs with no project manifest.
if [ -z "${ARIS_REPO:-}" ] && [ -f "$HOME/.aris/repo" ]; then
    ARIS_REPO=$(cat "$HOME/.aris/repo" 2>/dev/null) || true
fi
WIKI_SCRIPT=".aris/tools/research_wiki.py"
[ -f "$WIKI_SCRIPT" ] || WIKI_SCRIPT="tools/research_wiki.py"
[ -f "$WIKI_SCRIPT" ] || { [ -n "${ARIS_REPO:-}" ] && WIKI_SCRIPT="$ARIS_REPO/tools/research_wiki.py"; }

After the chain runs, exactly one of two outcomes:

[ -f "$WIKI_SCRIPT" ] → helper located, use as python3 "$WIKI_SCRIPT" <subcommand>
[ ! -f "$WIKI_SCRIPT" ] → helper missing; pick a variant below

Variant A — hard-fail (for `/research-wiki` itself)

The skill is the wiki tool. If the helper is missing, fail loudly.

[ -f "$WIKI_SCRIPT" ] || {
  echo "ERROR: research_wiki.py not found at .aris/tools/, tools/, \$ARIS_REPO/tools/, or via ~/.aris/repo." >&2
  echo "       Fix one of:" >&2
  echo "         1. rerun 'bash tools/install_aris.sh' from the ARIS repo (creates .aris/tools symlink, refreshes ~/.aris/repo)" >&2
  echo "         2. rerun 'bash tools/smart_update.sh' (refreshes ~/.aris/repo)" >&2
  echo "         3. export ARIS_REPO=<path-to-ARIS-repo>" >&2
  echo "         4. cp <ARIS-repo>/tools/research_wiki.py tools/" >&2
  exit 1
}

Variant B — warn + skip (for caller skills)

Used by /idea-creator, /result-to-claim, /research-lit, /arxiv, /alphaxiv, /deepxiv, /exa-search, /semantic-scholar. The skill's primary output (idea ranking, claim verdict, paper summary) must still be delivered to the user; only the wiki side-effect is skipped.

[ -f "$WIKI_SCRIPT" ] || {
  echo "WARN: research_wiki.py not found at .aris/tools/, tools/, \$ARIS_REPO/tools/, or via ~/.aris/repo." >&2
  echo "      Primary output will still be produced; wiki update is skipped." >&2
  echo "      Fix: rerun 'bash tools/install_aris.sh' or 'smart_update.sh' (refreshes ~/.aris/repo), export ARIS_REPO, or 'cp <ARIS-repo>/tools/research_wiki.py tools/'." >&2
  WIKI_SCRIPT=""
}

After Variant B, every helper invocation must be guarded:

[ -n "$WIKI_SCRIPT" ] && python3 "$WIKI_SCRIPT" ingest_paper research-wiki/ --arxiv-id "$id"

Why four locations and not one

Four locations correspond to four legitimate install / dev paths:

Location	When applicable
`.aris/tools/research_wiki.py`	After running `bash tools/install_aris.sh` in the user project (Phase 0 symlink, added in #174 / #192)
`tools/research_wiki.py`	(a) Manual copy of the helper into the user project (a documented temporary workaround); (b) running a SKILL from inside the ARIS repo itself
`$ARIS_REPO/tools/research_wiki.py`	Env var explicitly set, or auto-resolved from `.aris/installed-skills.txt`'s `repo_root` field
`$ARIS_REPO/tools/research_wiki.py` via `~/.aris/repo`	Global pointer file written by `install_aris.{sh,ps1}` / `smart_update.{sh,ps1}` (#366); the only layer that resolves for a global copy-install (`~/.claude/skills/research-wiki`) where none of the first three apply — there is no project-local `.aris/`, no `tools/` copy, and no manifest to read `ARIS_REPO` from

Order matters: the symlinked install is preferred because the symlink auto-tracks upstream tool fixes; the manual copy is second because it catches users who haven't run install_aris.sh; the manifest-derived env var is next because a project-local manifest is more precise than a global pointer; the global pointer file is last because it is per-user rather than per-project and only fires when the first three all miss.

What NOT to add

❌ A layer that searches up the directory tree for tools/ — too much path magic, surprising failure modes.
❌ A layer at /usr/local/share/... or another OS-specific system path — ~/.aris/repo already covers the global-install gap with a single per-user file, no OS branching needed.
❌ Adding ~/.codex/skills/research-wiki/research_wiki.py — that's Codex-side global install, lives in the Codex mirror's chain (skills/skills-codex/...), not the CC chain.

~/.aris/repo (layer 4, #366) is the one exception to the earlier "no 4th layer" stance in this doc's history: it exists because the installer/updater now writes it, giving the previously-missing precedent. If a 5th layer is ever proposed, it should still meet the same bar — a concrete writer, not just a hopeful lookup — rather than an implicit env var or path-walk.

⚠️ Do not wrap the chain in `set -e` / `set -eu`

The ${ARIS_REPO:-$(awk ...)} substitution propagates the inner awk exit code to set -e even when stderr is suppressed with 2>/dev/null. awk returns non-zero (2 on most macOS systems) when its input file does not exist — which is the common case (no .aris/installed-skills.txt yet). With set -e enabled, the chain will exit silently with code 2 before reaching the [ -f ... ] checks, masking the real failure mode and breaking the manual-copy fallback.

If a SKILL author wants strict-mode safety, restructure the manifest read instead:

if [ -z "${ARIS_REPO:-}" ] && [ -f .aris/installed-skills.txt ]; then
    ARIS_REPO=$(awk -F'\t' '$1=="repo_root"{print $2; exit}' .aris/installed-skills.txt 2>/dev/null) || true
fi

But the simpler answer is: don't enable strict mode for the resolver preamble. SKILL bash blocks do not run with set -e by default and the rest of the helper invocations all use explicit [ -n "$WIKI_SCRIPT" ] && ... guards anyway.

6.3 KiB Raw Permalink Blame History