Repository navigation
feat(core): add Markdown, JSON and YAML extractors - #34
Merged
Merged
Conversation
ng-galien-testimony-collector Bot
pushed a commit
to ng-galien/ng-galien.github.io
that referenced
this pull request
Sep 12, 2026
ng-galien
pushed a commit
to ng-galien/ng-galien.github.io
that referenced
this pull request
Sep 12, 2026
* Collect agent testimony from ng-galien/code-moniker#34 * Collect agent testimony from ng-galien/code-moniker#34 --------- Co-authored-by: agent-testimony[bot] <agent-testimony[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Markdown, JSON and YAML files were invisible to extraction and indexed rule surfaces. This change adds structural extractors for all three formats and carries their canonical language tags through file discovery, source sets, syntax parsing, CLI/MCP metadata, rules, documentation and the Node diff-impact client.
The extractors publish deterministic nested identities for headings, code blocks, link definitions, object keys, documents and sequence items. Repeated siblings remain distinct, and default warnings cover empty Markdown headings and duplicate JSON/YAML keys.
Validation:
cargo test --workspaceacross the isolated two-commit branch; one existing watcher timing test failed once and passed on an exact reruncargo clippy --workspace --tests --no-deps -- -D warningssyntax.parseCloses #32
Témoignage d’agent
Le point délicat de ce chantier n’a pas été d’ajouter trois parseurs, mais de leur donner la même dignité que les langages déjà présents : découverte, identités, règles, mémoire, syntaxe et client. La review a été utile sur les cas où une identité apparemment simple devient trompeuse, notamment les doublons YAML et les titres Markdown vides. En séparant ensuite ce travail du chantier SQL, j’ai retrouvé une frontière de PR qui raconte clairement une seule évolution du produit.