Conversation
The `experiment` artifact (`constants.ExperimentArtifactName = "experiment"`) was missing from the Artifacts reference page. Add it to: - Quick Reference table (with constant, type, and description) - Artifact Sets table (`--artifacts experiment`) - New `## experiment` section with contents, CLI usage, and cross-reference Also include `experiment` in the multi-file artifact list in the Naming Compatibility prose. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds missing documentation for the experiment artifact and the corresponding --artifacts experiment CLI artifact set in the Artifacts reference.
Changes:
- Added
experimentto the Quick Reference artifacts table (constant/type/description) - Added
experimentto the Artifact Sets table and documented CLI usage - Added a dedicated
## experimentsection and updated Naming Compatibility prose to mentionexperiment
Show a summary per file
| File | Description |
|---|---|
| docs/src/content/docs/reference/artifacts.md | Documents the experiment artifact end-to-end (tables + dedicated section + compatibility note) |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/1 changed files
- Comments generated: 2
Comment on lines
+185
to
186
| Single-file artifacts are automatically flattened to root level regardless of their artifact directory name. Multi-file artifacts (`firewall-audit-logs`, `agent`, `activation`, `experiment`) retain their directory structure. | ||
|
|
Comment on lines
35
to
36
| | `firewall` | `firewall-audit-logs` | Network policy and firewall audit data | | ||
| | `mcp` | `firewall-audit-logs` | MCP gateway traffic logs | |
This was referenced May 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
{
"title": "Self-healing documentation fixes from issue analysis - 2026-05-02",
"body": "### Self-Healing Documentation Fixes\n\nThis PR was automatically created by the Daily Documentation Healer workflow.\n\n### Gaps Fixed\n\n-
experimentartifact missing fromdocs/src/content/docs/reference/artifacts.md— theExperimentArtifactNameconstant (experiment) and its corresponding CLI artifact set (--artifacts experiment) were not documented anywhere in the Artifacts reference page.\n\n### Changes Made\n\n- Addedexperimentrow to the Quick Reference table (constant, type, description)\n- Addedexperimentrow to the Artifact Sets table (--artifacts experiment)\n- Added a new## experimentsection with contents, CLI usage example, and cross-reference to the A/B Experiments guide\n- Updated the multi-file artifact list in the Naming Compatibility prose to includeexperiment\n\n### Root Cause\n\nDDUw's artifact constant check scanspkg/constants/constants.goandpkg/constants/job_constants.goforArtifactNameconstants and verifies each value appears inartifacts.md. TheExperimentArtifactNameconstant would be caught by this scan. However, DDUw has no equivalent check forArtifactSetconstants inpkg/cli/logs_artifact_set.go, so theexperimentset name never appeared in the Artifact Sets table.\n\nDDUw Improvement Suggestions
\n\n### DDUw Improvement Suggestions\n\nAdd a second scan in DDUw Step 2 (Artifact constant check):\n\nbash\ngrep -Pn 'ArtifactSet\\w+\\s*ArtifactSet\\s*=' pkg/cli/logs_artifact_set.go\n\n\nFor eachArtifactSetconstant found, verify that the set name value appears in the Artifact Sets table indocs/src/content/docs/reference/artifacts.md. If a set is missing, treat it as a documentation gap and add it.\n\nSuggested wording to add after the existing artifact constant check in DDUw Step 2:\n\n> Also run:\n>bash\n> grep -Pn 'ArtifactSet\\w+\\s*ArtifactSet\\s*=' pkg/cli/logs_artifact_set.go\n>\n> For each constant found, verify that the set name value is listed in the Artifact Sets table indocs/src/content/docs/reference/artifacts.md. If a set is missing from the table, treat it as a documentation gap and add it.\n\nghCLI was not available in this run (bash allowlist restrictsghto specific patterns). Theexperimentgap was identified via the local artifact constant check in Step 2 of the healer workflow.","branch": "doc-healer/experiment-artifact-2026-05-02",
"base": "main"
}