Skip to content

Technical Source Coverage

Daniel Neto edited this page Oct 29, 2026 · 1 revision

Technical documentation coverage

Review date: 2026-10-29. This is static source inspection and editorial tracing, not a runtime test report.

Source baselines

  • Streamer: 7d48f2dfc0289236718a3f9fba7c5ffecff4a37f.
  • Encoder: f05d252659279de90511c1ab2b783bafb0f6f995.
  • Each plugin's own revision/version and any source changes are recorded on its technical page.

Inventory coverage

Item Count
source files 3169
php files 2584
named symbols 10422
plugins 132
streamer plugins 80
independent plugins 40
local plugins 12

The generator reads available PHP/SQL/JavaScript implementation files from tracked component sources and local extensions. It excludes private deployment configuration/media, dependency trees, minified assets, locale catalogs, editor stubs and tests from implementation inventories. Test filenames are linked separately when their names match a plugin; those files were not executed by generation. The generated symbols are file-scoped inventories and do not certify visibility, reachability or behavior.

Analysis depth

All available plugin main files and implementation files were scanned for declarations and literal reference patterns. Behavioral guides trace major workflows using source. This does not mean every line received an independent semantic audit. Dynamic parameters, runtime-generated SQL, computed defaults, reflection, external binaries and provider internals cannot be fully described by literal extraction.

Not validated by this task

  • Live ingest/transcoding, destination playback/archive, recording completeness and audiovisual output.
  • Real conversion/transfers, multi-Streamer callback execution, cloud storage and payment-provider delivery.
  • Authenticated UI/mobile/provider flows and deployment-specific settings or loaded runtime extensions.
  • Public availability of new wiki pages before commit/push, or successful production AI ingestion.

Reproduction

The maintenance guide documents the read-only source extractor and reference generator. source-manifest.json stores relative source hashes and owning component revisions; it contains no installation settings or function bodies. A hash match validates the inventory input, not the correctness of a behavioral claim.

Maintenance workflow · Technical index.

Clone this wiki locally