CI: Nightly full CI failing on origin/live due to unrecognized .jsonl extension

CI Failure Analysis

Failing Commit

• Commit: 3c7540c8 "deploy: add readOnlyPaths support to Hardening"
• Branch: origin/live
• Author: Ben Sima
• Date: Wed Jan 21 18:25:40 2026

Error Output

fail:  bild:  /home/ben/omni/live/Omni/Agent/Eval/questions.jsonl:  could not get namespace

Root Cause

The file Omni/Agent/Eval/questions.jsonl was added to the repository in commit 34c1e3ca (Jan 8, 2026) but the .jsonl extension was never added to Omni/Namespace.hs as a recognized file extension.

The bild system tries to parse all files in the repository to extract namespaces. When it encounters questions.jsonl, it fails because: 1. The extension .jsonl is not in the data Ext enum in Omni/Namespace.hs 2. The regex parser reExt doesn't recognize .jsonl 3. This causes Namespace.fromPath to return Nothing 4. Which triggers the error "could not get namespace"

Fix Available

A fix was already implemented in commit d7aa4fb5 "Add jsonl as recognized non-buildable extension" which:

• Adds Jsonl to the Ext enum
• Adds .jsonl to the reExt regex parser
• Marks Jsonl as non-buildable in isBuildableNs
• Skips it in analyzeOne

However, this commit is on the ava branch and has NOT been merged to origin/live.

Suggested Next Steps

1. Immediate: Cherry-pick or merge d7aa4fb5 to origin/live 2. Verify: Run CI on the merged commit to confirm the fix 3. Future: Add pre-commit check or lint rule to catch unrecognized file extensions 4. Process: Consider requiring CI pass before merging new file types to main branch

Related Files

• Omni/Namespace.hs - Extension enum and parser
• Omni/Bild.hs - Build system that calls namespaceFromPathOrDie
• Omni/Agent/Eval/questions.jsonl - The file triggering the error