Skip to content

docs: add compiler-smoke-e2e to architecture trees in AGENTS.md and docs/ado-script.md#1674

Draft
github-actions[bot] wants to merge 1 commit into
mainfrom
docs/add-compiler-smoke-e2e-to-tree-f8a17fb594d01e1c
Draft

docs: add compiler-smoke-e2e to architecture trees in AGENTS.md and docs/ado-script.md#1674
github-actions[bot] wants to merge 1 commit into
mainfrom
docs/add-compiler-smoke-e2e-to-tree-f8a17fb594d01e1c

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Agent Documentation Update

Findings

Area Issue File(s)
Architecture tree (accuracy) scripts/ado-script/src/compiler-smoke-e2e/ was absent from the scripts/ado-script/src/ subtree, even though the sibling test harnesses executor-e2e/ and trigger-e2e/ were already listed AGENTS.md, docs/ado-script.md

Applied Fixes

  • Added compiler-smoke-e2e/ entry to the scripts/ado-script/src/ tree in AGENTS.md with a description matching the pattern used for the other test-only harnesses
  • Added a callout note in docs/ado-script.md (alongside the existing executor-e2e and trigger-e2e callouts) explaining that compiler-smoke-e2e is not a shipped bundle and pointing to the ADO pipeline definition in tests/compiler-smoke-e2e/
  • Added compiler-smoke-e2e/ to the file tree in docs/ado-script.md

Notes

Verified against scripts/ado-script/src/compiler-smoke-e2e/index.ts docstring, which confirms it is a test-harness module not shipped in ado-script.zip. The orchestrator stages the current compiler candidate as a supply-chain.pipeline-artifact across the five lock-file fixtures and asserts they all go green; the corresponding ADO pipeline definition lives in tests/compiler-smoke-e2e/.

All other directories in scripts/ado-script/src/ were already present in both trees. No source-code files were changed.


Created by the agent-documentation maintainer workflow.

Generated by Agent Documentation Maintainer · 218.3 AIC · ⌖ 12.2 AIC · ⊞ 8.7K ·

…ocs/ado-script.md

The test-only compiler smoke orchestrator in
scripts/ado-script/src/compiler-smoke-e2e/ was missing from both the
AGENTS.md architecture tree and the docs/ado-script.md file tree,
even though its sibling test harnesses (executor-e2e/, trigger-e2e/)
were already documented. This gap meant agents reading the architecture
would not know the directory existed or how it related to the ADO
pipeline definition in tests/compiler-smoke-e2e/.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
2 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants