Skip to content

chore(demo): add the demo GIF recorder - #336

Open
eFAILution wants to merge 1 commit into
betafrom
chore/demo-gif-recorder
Open

eFAILution wants to merge 1 commit into
betafrom
chore/demo-gif-recorder

Conversation

@eFAILution

Copy link
Copy Markdown
Owner

Summary

  • Adds the scripts that recorded the new README GIFs, so we can redo them after UI changes with cd scripts/demo-gifs && npm install && npm run record.
  • They drive a packaged VSIX in a throwaway profile under /tmp/gch-demo and write out/<scene>.gif plus a review sheet with one frame per second for checking nothing private shows up.
  • Own package.json and lockfile, so the extension's install and bundle don't change. scripts/** was already in .vscodeignore, and vsce ls shows nothing from scripts/ in the VSIX.
  • .ai/ gets a record_demo_gifs workflow, an architecture entry, a decision on hosting the GIFs as user-attachments, and a troubleshooting entry. index.yaml regenerated.
  • Link related issue(s): n/a

Change Type

  • feat
  • fix
  • refactor
  • docs
  • test
  • chore

Context

User-facing impact

  • None. Maintainer tooling only.

GitLab scope

  • gitlab.com

Affected areas

  • Docs only

Validation

Local checks

  • npx eslint --max-warnings 0 . (added a lint block for scripts/demo-gifs/**/*.mjs)
  • npm audit in scripts/demo-gifs: 0 vulnerabilities
  • Full npm run record from a clean work dir produced all five GIFs, matching the ones in the README

Manual test notes

  • macOS only for now, and it has to run outside a command sandbox since VS Code needs its mach port and debug port.

Breaking Changes

  • No breaking changes

Risk and Rollback

  • Main risks: VS Code UI changes breaking a scene. Failure modes are in .ai/errors.yaml (demo_gif_recording_fails).
  • Rollback strategy: revert the commit.

Release Notes Draft

  • n/a, internal tooling.

Checklist

  • Branch is up to date with target branch
  • Commit messages follow conventional commits
  • Added/updated docs for behavior or settings changes
  • Added/updated tests for new behavior
  • No secrets or tokens in code, logs, screenshots, or test fixtures

Scripts under scripts/demo-gifs drive a packaged VSIX in a throwaway VS
Code profile over CDP and encode each scene to a GIF, plus a per-second
review sheet for the privacy check. They have their own package.json and
are already excluded from the VSIX by scripts/** in .vscodeignore.

Documents the workflow, layout, decision, and failure modes in .ai/.
@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

🛡️ Security Hardening Pipeline Results

Branch: chore/demo-gif-recorder
Commit: 2bca637

Workflow Run: 525
Branch: chore/demo-gif-recorder
Commit: 2bca637

Scan Status

Scanner Status
bandit ⏭️ skipped
checkov ⏭️ skipped
clamav ⏭️ skipped
codeql ✅ PASS
container ⏭️ skipped
dependency-review ✅ PASS
gitleaks ✅ PASS
grype ⏭️ skipped
lint ⏭️ skipped
opengrep ⏭️ skipped
osv ✅ PASS
sbom ⏭️ skipped
supply-chain ⏭️ skipped
trivy-container ⏭️ skipped
trivy-iac ⏭️ skipped
zap ⏭️ skipped

✅ All enabled scanners completed successfully.

Summaries Collected: 4

Scanner Results

🔬 CodeQL SAST (Javascript)

Status: Completed

Findings Summary

Critical High Medium Low Total
0 0 0 0 0

No security findings detected for Javascript.

Artifacts: CodeQL Reports (Javascript)

🔗 Dependency Review

Status: ✅ No issues found

No vulnerable or license-violating dependencies detected in this PR.
📋 View full report

🔑 Gitleaks (Secrets)

No 🔑 Gitleaks (Secrets) findings summary was produced.

📦 OSV (Dependencies)

No 📦 OSV (Dependencies) findings summary was produced.


Generated by Argus


Generated by Argus

This branch has not been deployed

No deployments
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.

1 participant