TAAC_2026

Retrieve and analyze GitHub Actions CI/CD logs. Use when the user provides a GitHub Actions run URL (e.g. https://github.com/OWNER/REPO/actions/runs/RUN_ID) and needs to diagnose CI failures, view raw logs, or summarize build results. Works with or without the raw logs direct URL.

Use when: inspecting TAAC/Taiji platform pages on taiji.algo.qq.com, especially model training instances, checkpoint pages, metrics plots, TensorBoard-like scalars, browser MCP sessions, authenticated cookies, or direct platform API calls. Prefer API data over screenshots.

Use when changing TAAC PCVR experiment packages or shared PCVR runtime code under experiments/, src/taac2026/domain, src/taac2026/application, or src/taac2026/infrastructure, including model contracts, experiment discovery, packaging, training/evaluation/inference hooks, and accelerator-backed modeling behavior.

Use before running TAAC repository Python commands, pytest, console scripts, packaging/docs CLIs, or run.sh, and when working on local setup, uv/CUDA dependency flow, online training or inference bundles, package contents, platform Python execution, or environment/debug docs.

Use when editing or reviewing TAAC docs, zensical configuration, generated site artifacts, GitHub Pages deployment workflows, docs CI behavior, or questions about whether documentation changes deploy correctly.

Use when Dev Container attach is slow, VS Code Remote Containers leaves stale helper processes, /tmp/.X11-unix has many displays, /root/.vscode-server has old versions/logs, or extension caches need safe cleanup inside a dev container.