Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[workshop-sync] side-quest-25-01-audit-reference.md: wrong artifact file names (safeoutputs.jsonl, mcp-logs/) and unverifiable "⌖ AIC" terminolo

已关闭 适合新手
#4,451 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
84/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
javascript
领域
documentation

调研方向

从 workshop/side-quest-25-01-audit-reference.md 入手,将制品名称和 AIC 术语与引用的制品以及审计、成本管理文档进行对照。更新列出的文件名、MCP 日志指南和分类器 AIC 的措辞,使其与这些参考资料一致。当 workshop 文件使用文档中规定的名称,并在 Model Routing 的上下文中描述分类器 AIC 时,工作即告完成。

由索引模型根据 Issue 内容生成。

描述

documentation

Workshop file reviewed

workshop/side-quest-25-01-audit-reference.md

Problem

  1. The agent artifact file table lists:

| safeoutputs.jsonl | Every safe-output declaration the agent emitted |

The live reference/artifacts/ doc names this file agent_output.json, not safeoutputs.jsonl — that filename does not appear anywhere in the artifacts documentation.

  1. The same table lists:

| mcp-logs/ | One log file per MCP server, listing every tool call and result |

Searching the raw HTML of both reference/artifacts/ and reference/audit/ for "mcp-logs" and "mcp_logs" returns zero matches. The documented structure for MCP/network traffic is the firewall-audit-logs artifact (downloaded via --artifacts mcp, per the Artifact Sets table: "mcp → firewall-audit-logs → MCP gateway traffic logs") or sandbox/firewall/logs/api-proxy-logs/ within the unified agent artifact — not a per-MCP-server mcp-logs/ directory.

  1. The file repeatedly uses a "⌖ AIC" / "Threat-detection AIC" metric:

**Threat-detection AIC (⌖ AIC)** — credits consumed by the firewall's threat-detection model, reported separately from agent inference
| ⌖ AIC | 3 | (in the sample audit report)
The **⌖ AIC** column in gh aw logs output shows credits consumed by the threat-detection model

Exhaustive searches of reference/audit/, reference/cost-management/, and the full gh aw CLI help snapshot found zero matches for "⌖" or "Threat-detection AIC". The actual documented term is "classifier AIC", part of the Model Routing summary for routed runs — a distinct concept from firewall threat detection.

Current correct behaviour

  • Safe-output data file: agent_output.json (per reference/artifacts/ → "agent" artifact section)
  • MCP/network traffic logs: firewall-audit-logs artifact or sandbox/firewall/logs/api-proxy-logs/ (per Artifact Sets table)
  • AIC routing terminology: "classifier AIC" (per reference/cost-management/ and reference/audit/), not "⌖ AIC" / "Threat-detection AIC"

The --parse flag, log.md/firewall.md output filenames, network.allowed frontmatter syntax, and the gh aw audit <run-id> --parse / gh aw logs <workflow-id> --artifacts all command forms in this file are all accurate and need no changes.

Suggested fix

  • Replace safeoutputs.jsonl with agent_output.json in the artifact file table.
  • Replace the mcp-logs/ row and the "Explore MCP tool calls" exercise with the documented sandbox/firewall/logs/api-proxy-logs/ path or firewall-audit-logs artifact (--artifacts mcp), and update the .github/aw/logs/<run-id>/mcp-logs/ path reference accordingly.
  • Replace "Threat-detection AIC (⌖ AIC)" and all "⌖ AIC" mentions (including in the sample report table and checkpoint) with the documented "classifier AIC" terminology, correcting the description to match its Model Routing context (routed runs only), or remove the bullet if no direct equivalent exists.

References: https://github.github.com/gh-aw/reference/artifacts/, https://github.github.com/gh-aw/reference/audit/, https://github.github.com/gh-aw/reference/cost-management/ (all confirmed reachable, HTTP 200)

Generated by 🔍 Workshop Sync Check · copilot · auto · 239.5 AIC · ⌖ 8.28 AIC · ⊞ 9.2K · ◷

  • expires on Oct 12, 2026, 5:49 AM UTC
主要语言
JavaScript
星标
55
派生
36
平均合并
2 天 8 小时
30 天内合并 PR
17

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

githubnext/gh-aw-workshop 的其他 Issue

查看 githubnext/gh-aw-workshop 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。