Skip to content

Epic: Harden the strict structural-signature test suite (non-extraction-pillar rules) per language #1069

Closed

Description

@squid-protocol

Why

This epic is a #518-lineage follow-on addressing structural test rigor gaps found in a fresh audit (2026-08-05) of the 45 tests/extraction/languages/test_<lang>_strict.py files against their corresponding LANGUAGE_DEFINITIONS rules in gitgalaxy/standards/language_standards.py.

Epic #518 (closed 2026-08-01) established the per-language _strict.py test suite for all non-None structural signatures — but that audit followed a premise that only 6 languages had prior coverage, and coverage depth was checked at suite-completion time only, not against a rigor baseline.

Epic #813 (closed 2026-08-03) hardened the four extraction gauntlets (func_start/args/class_start/_dependency_capture) using an explicit valid/invalid/pathological three-tier methodology with strong depth requirements (10-15+ cases per rule). The founding audit rejected as "dangerously sparse" the prior state: "2-3 cases per tier, 1 pathological case" — the same rigor bar was never applied retroactively to this epic's sibling _strict.py suite.

A read-only re-audit (2026-08-05) found five systematic gaps in the non-extraction-pillar structural signatures:

  1. Zero-ReDoS gap: 6 languages (haskell, kotlin, lua, ruby, scala, swift) have literally zero assert_redos_immune(...) calls anywhere in their _strict.py files.
  2. Single-timeout vs. scaling-ratio rigor: 37 of 45 languages rely solely on the weaker assert_redos_immune (single payload, single 1.0s timeout) rather than _best_of_timing (geometric-growth scaling-ratio method — the actual methodology how_to_add_a_language.md's Strict Testing Prompt mandates for Rule 14 adjacent-quantifier-overlap detection).
  3. Missing signature coverage, especially AI/ML pack: python is missing 19 signatures including its entire AI/ML extension pack (llm_api, llm_orchestrator, llm_vector_store, dl_frameworks, etc.), javascript 16 (same AI/ML pack), and others.
  4. Ghost-prevention gap (negative-case testing): 17 of 45 languages have >70% of their _SIMPLE_CASES paired with None (zero false-positive testing), mirroring exactly the "invalid — Ghost Prevention" tier gap epic Epic: Harden the four extraction gauntlets (function/args/class/dependency) per language #813 found and fixed in the sibling extraction pillars.
  5. Single-case-per-signature depth: almost every language has exactly one case per signature key — none approach the 10-15+ case depth the extraction gauntlets now require.

Scope

This epic covers ONLY the non-extraction-pillar _strict.py test files — do NOT conflate with #813's extraction-gauntlet work (func_start/args/class_start/_dependency_capture are #813's domain). The rules in scope here are: branch, io, safety_bypasses, cryptography, hardcoded_secrets, regex_execution, serialization_parsing, time_date_logic, ipc_rpc_bridges, api, bitwise_ops, closures, comprehensions, encapsulation, exfiltration_camouflage, hardware_bridge, import, lazy_evaluation, llm_api, llm_orchestrator, llm_vector_store, memory_scraping, ml_traditional, structural_boundaries, test, vectorized_math, and others not in the extraction-pillar set.

Reference docs

  • gitgalaxy/standards/how_to_add_a_language.md — the canonical spec for structural signature semantics and the full recurring-bug-class checklist (16 numbered engine rules).
  • tests/extraction/how_to_harden_extraction.md — the extraction-gauntlet methodology epic Epic: Harden the four extraction gauntlets (function/args/class/dependency) per language #813 established; this epic borrows its three-tier valid/invalid/pathological template.
  • tests/extraction/languages/_strict_harness.py — shared ReDoS-testing helpers: assert_redos_immune (weak, single-timeout) and _best_of_timing (strong, scaling-ratio).

Sub-issues

Related epics:

Resolution

All 5 sub-issues closed 2026-08-05/06:

tests/extraction/how_to_harden_strict_signatures.md and the audit_strict_coverage.py / verify_candidates.py / redos_scaling_check.py tooling built for this epic (PR #1075) remain checked in for the next language or bug-class sweep.

Activity

  1. added
    epicLarge-scale architectural milestone or multi-issue initiative
    testingUnit, integration, and E2E pipeline verification
    core-engineModifications to the central physics and parsing engine
    on Aug 5, 2026
  2. added a commit that references this issue on Aug 5, 2026
  3. squid-protocol commented on Aug 6, 2026

    @squid-protocol
    OwnerAuthor

    Sub-issue #1071 (ReDoS geometric scaling coverage) has been fully resolved and closed via PR #1083. We committed the global diagnostic tool to permanently document the safety proof in the codebase.

  4. squid-protocol commented on Aug 6, 2026

    @squid-protocol
    OwnerAuthor

    All 5 sub-issues (#1070-#1074) closed — see the Resolution section added to the issue description for per-sub-issue PR links and the #1074 golden-master impact summary. Epic complete.

  5. added this to the v2.4.8 milestone on Aug 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    core-engineModifications to the central physics and parsing engineepicLarge-scale architectural milestone or multi-issue initiativetestingUnit, integration, and E2E pipeline verification

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions