feat(troubleshoot): signature frontmatter for pending playbook PRs (merge LAST)#1837
Draft
dmorosanu wants to merge 29 commits into
Draft
feat(troubleshoot): signature frontmatter for pending playbook PRs (merge LAST)#1837dmorosanu wants to merge 29 commits into
dmorosanu wants to merge 29 commits into
Conversation
…leshooting playbooks
…d process names not covered by other PRs (ui-automation, web, orchestrator-foreground, runtime-exceptions)
…ul-replay scenario
…hful-replay scenario
…ure faithful-replay scenario
…vailable playbook
…activity playbooks
…onnect-failed replay scenarios
…fest docs to avoid resolution bias
…s + PDF replay tests
…encrypted/no-OCR playbook signatures
…xception 401 replay scenario
…e-captured UiPathOCRInvalidApiKey (AggregateException)
…rrect encrypted signature to live PdfException 'The password is incorrect.'
… correct connection signatures to live RfcConfigurationException
…ivityException) replay scenario
… (connection-config + invalid-key ARE stageable locally)
…notes from shipped playbooks (client-facing content describes the failure, not our test process)
…/file-folder/queue playbooks and OCR activities knowledge base
…/copy-file/queue replay scenarios (all pass 1.0)
…cked signatures PR # Conflicts: # skills/uipath-troubleshoot/references/summary.md
…gnatures PR # Conflicts: # skills/uipath-troubleshoot/references/summary.md
…ding playbook PRs
dmorosanu
force-pushed
the
feat/troubleshoot-pr-playbooks-signatures
branch
from
766a21a to
245d0a0
Compare
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
1 participant
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.
What
v2 signature frontmatter (+ regenerated
signature-index.md) for the 27 playbooks introduced by the pending troubleshoot PRs — the piece that makes those playbooks routable under the #1820 architecture. Extracted during a local compatibility validation in which all 28 scenarios from those PRs passed against v2 (26× 1.000, details in the table below).Merge order — do NOT merge before its dependencies
This branch = #1820 (
feat/troubleshoot-v2) + temporary merges of #1813, #1798, #1776, #1767, #1732, #1727, #1713 + one real commit (766a21aad, the frontmatter + index). Merge it last, after #1820 and all seven PRs above have landed. Because the repo squash-merges, the diff shown here will keep displaying the dependencies' content until they land — once they do, update this branch from main and the diff collapses to just the frontmatter/index commit.Validation (local, judge-graded, v2 skill + these playbooks)
Lint state on this branch: 242 playbooks, 753 signatures, 22 silent, zero findings; index freshness check passes.
Note for the dependency PRs
Each of the seven PRs will hit a small
references/summary.mdconflict when rebasing onto v2 (the file is now the "Domain Catalog" with routing moved tosignature-index.md) — the resolution is a plain union of domain sections, already done once inside this branch's merge commits for reference.