Skip to content

[docs] Update glossary - daily scan - #49117

Merged
pelikhan merged 1 commit into
mainfrom
glossary-daily-scan-2026-07-30-2b8fcb0fa90a7a65
Jul 30, 2026
Merged

[docs] Update glossary - daily scan#49117
pelikhan merged 1 commit into
mainfrom
glossary-daily-scan-2026-07-30-2b8fcb0fa90a7a65

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Warning

threat detection engine error
The threat detection engine encountered an error and could not complete analysis. This is a tooling failure, not a security finding.

Details

The threat detection engine failed to produce results.

Review the workflow run logs for details.

Overview

Docs-only update to the glossary (docs/src/content/docs/reference/glossary.md), adding definitions for recently introduced safe-output concepts. No code changes.

Key Changes

  • Safe Output Messages: extended definition to document new AI cost/detection context variables ({ai_model}, {ai_credits}, {ai_credits_formatted}, {agent_ai_credits_formatted}, {evals_ai_credits_formatted}, {threat_detection_ai_credits_formatted}, {detection_conclusion}, {detection_reason}) usable in custom footer templates.
  • Egress Context Validation (MCE1)(new entry): documents the safe-output handler safeguard (Safe Outputs Specification requirement MCE1) that validates a required triggering context (PR/issue/discussion number) before writing NDJSON, applied to close_pull_request, merge_pull_request, mark_pull_request_as_ready_for_review, add_reviewer, reply_to_pull_request_review_comment, close_issue, add_labels, remove_labels, update_discussion, and close_discussion.
  • Implausible Shallow Range Guard(new entry): documents a push-to-pull-request-branch safety check that detects shallow-clone (fetch-depth: 1) artifacts causing git rev-list to report an implausible commit range, guarded by a 100-commit threshold.
Details
  • File: docs/src/content/docs/reference/glossary.md
  • Change type: modified (additive only)
  • Impact: medium (clarifies documentation/spec terminology, no runtime behavior change)
  • Breaking: no

Next Actions

None — documentation-only change ready to merge.

Generated by PR Description Updater for #49117 · auto · 39.2 AIC · ⊞ 6.8K ·

Daily scan for 2026-07-30. Added 3 new glossary entries:
- Implausible Shallow Range Guard: documents the fail-fast check in
push-to-pull-request-branch that detects when a shallow clone
causes git rev-list to report the entire local history as the
commit range (commit 2c32514).
- Egress Context Validation (MCE1): documents the safe-output handler
safeguard that validates triggering context before writing NDJSON,
applied to 10 handlers to prevent hard-fails on scheduled runs
(commit 6e66359).
- Updated Safe Output Messages entry to mention the individual AI
cost and detection footer template variables (commit 9f0e737).
Candidates reviewed but not added: Copilot SDK stability change
(existing glossary entry already accurate, no experimental wording
to remove), bundle prerequisite SHA linearization, cache lightweight
agentic workflow logs, goroutinemissingrecover linter,
stringsconcatloop accumulator pattern, ValidateExecutablePath/
ResolveExecutablePath (all internal implementation details or
contributor-only tooling, not user-facing documentation terms).
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actionsgithub-actionsBot added documentation Improvements or additions to documentation glossary labels Jul 30, 2026
@pelikhan
pelikhan merged commit 78fd190 into mainJul 30, 2026
2 checks passed
@pelikhan
pelikhan deleted the glossary-daily-scan-2026-07-30-2b8fcb0fa90a7a65 branch July 30, 2026 11:02
@github-actions

Copy link
Copy Markdown
ContributorAuthor

🎉 This pull request is included in a new release.

Release: v0.84.1

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

Labels

documentationImprovements or additions to documentationglossary

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@pelikhan