Skip to content

dominant language inconsistency: reports PLAINTEXT while composition table shows JAVASCRIPT 53.8% #2555

Closed

Description

@squid-protocol

Summary

Scan of expressjs/express (141 .js files, examples/lib/test dirs) reports internally inconsistent language classification:

Observed (MACRO STATE):

  • Dominant Lang: PLAINTEXT

Expected (COMPOSITION table same report):

  • JAVASCRIPT: 43 files / 1167 LOC / 53.8% (highest by both file count and LOC)
  • PLAINTEXT: 5 files / 1 LOC / 6.2%

The dominant-language field is computed over a different population than the scanned/composition population, producing a contradiction within a single report.

Reproduction

galaxyscope --llm-only /path/to/expressjs/express
# Scanner: examples, lib, test directories (141 .js files total)
# Expected: Dominant Lang should be JAVASCRIPT, not PLAINTEXT

Engine: GitGalaxy Scope vlatest (Delta Mode), contemporary with main 8880281.

Secondary defect: .js file over-exclusion

Same scan shows EXCLUDED ARTIFACTS section lists:

  • .js: 98x "Excluded (System Exclusion, Hidden Directory, or Dynamic Ignored Dir)"

This excludes 98 of 141 .js files (69%), silently dropping most of test/ and examples/ directories. Same over-exclusion family as #2512 and #2415 (aperture/census gates).

Tertiary defect: extension string artifact

Same exclusion section logs:

  • no_extension: 1x "Excluded (Unsupported Extension: '.txt"')"

Extension string carries a trailing double-quote character, suggesting a quoting artifact in extension extraction.

Labels

  • bug
  • core-engine
  • threat: false-negative
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

    scope:frontierMapped, not yet built: eras/commands/regions the burned estates don't use (Gap Atlas)

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions