Recorded 2026-10-15. Environment: Linux x86-64 authoring container; Node.js 22.16.0; Python 3.13.5; global TypeScript 5.8.3. These are execution-environment observations, not a recommended universal application toolchain.
| Check | Result | Scope / evidence |
|---|---|---|
| Dependency-free Node tests | 45/45 passed | TAP output |
| Python tooling tests | 14/14 passed | Output; same shared tooling suite is distributed in each skill |
| TypeScript declaration consumer | Passed | Command/output; pure graph/bridge declarations, including expected compile errors |
| TS/TSX syntax transpilation | 6 files passed | Output; no dependency resolution/typechecking |
| JavaScript syntax | 2 files passed | Per-file results; node --check |
| Bundle structure, local links, JSON and hashes | Passed | Local targets/reachability, JSON, basic frontmatter and complete SHA-256 manifest; no external HTTP requests |
The graph tests exercise canonical parsing, byte/node/edge/label/coordinate bounds, Unicode labels, IDs, unknown schema/types, endpoints/ports, cardinality, cycles, reconnect exclusion, deletion, iterative large-graph traversal, immutable history, branching, and history limits.
The Python tests cover read-only manifests, skipped dependency/symlink paths, scan/size limits, malformed inputs, heuristic reporting, npm-lock distinction, catalog lookup, and local-link resolution. They do not establish a complete static security analysis or parse every package-manager lock format.
React and React Flow packages were not installed. The UI was not checked against their actual declarations, built with Vite, rendered in a browser, or exercised with Playwright/assistive technology. Third-party integration sketches, layout/collaboration adapters, and SSR behavior were not runtime-tested. No backend, workflow executor, production persistence, or collaborative undo is supplied.
Registry access from the execution container failed with DNS resolution errors. Current official documentation was accessible through web research, but that is not the same as installing dependencies. No lockfile was fabricated and no unverified Electron release number was supplied. No penetration test, complete accessibility audit, external-link crawler, commercial-license audit, or exhaustive library compatibility matrix was executed.
The source register identifies documents actually reviewed; catalog discovery pointers are explicitly not contemporaneous maintenance/API endorsements. Original procedures and test designs are engineering recommendations. Passing mocked/pure tests does not prove browser, Electron, OS, signing, or update enforcement.
MANIFEST.json protects packaged file integrity relative to the recorded hashes; it is not a signature proving publisher identity. It excludes itself. The externally supplied ZIP checksums cover archives. The local validator checks a basic frontmatter subset and reference reachability, not the complete upstream Agent Skills specification.
Use the validation record to record resolved dependencies, supported target environments, actual type/build/runtime tests, negative cases, packaged-stage checks, and residual risks. Keep each unexecuted stage explicitly marked Not run. Do not promote this report into a production certification.