maintain-accessibility-skillslisted

# Maintain Accessibility Skills Apply the matching workflow below. Preserve the exact checkout and dirty baseline before changing history or staging files. ## Add a tracked-file hygiene scanner 1. Define the scanner's boundary as Git-tracked files. 2. Exclude the scanner's own path if its source must contain the forbidden pattern. 3. Stage the scanner, then run it. An untracked scanner cannot prove its behavior after commit. 4. Manually inspect the commit message, pull request body, and issue comments because the tracked-file gate cannot see them. Do not claim a local pass proves the committed gate works unless the scanner was staged during the test. ## Prove history-rewrite safety 1. Locate the exact reset, rebase, or rewrite operation in the reflog. 2. Identify the commit immediately before the operation. 3. Diff that tree against the current tree. 4. Describe the observed delta precisely before saying no work was lost. A clean status and empty stash list do not prove a history rewrite was safe. ## Split mixed work into focused commits 1. Read every changed and untracked file before proposing the split. 2. Back up files that contain more than one theme. 3. Split mixed files at hunk level instead of assigning the whole file to the first theme. 4. Run project validators on new fixtures and data before committing them. 5. Compare the final committed state with the backup to detect dropped or duplicated content. 6. Run the full applicable suite after the split is compl