Skip to content

Unblock CI: mark the one legacy Russian file - #51

Closed
gHashTag wants to merge 1 commit into
mainfrom
ci/unblock-cyrillic
Closed

Unblock CI: mark the one legacy Russian file#51
gHashTag wants to merge 1 commit into
mainfrom
ci/unblock-cyrillic

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

check-cyrillic fails on .claude/skills/gardener/SKILL.md and has been failing on main, so every pull request to this repository starts red on a file it does not touch.

The checker prescribes the remedy in its own error message:

If this is an intentional legacy Russian document, add this header to the first line:
  LEGACY: Russian-language document — translation pending

Applied verbatim, as a YAML comment immediately after name: — that places it inside the 500-character window check_cyrillic.py actually reads (LEGACY_HEADER in content[:500]) while leaving the frontmatter syntactically intact. Both verified: the checker now passes and the frontmatter still parses.

Nothing is translated, and no other file is touched. This records what the file already is, which is what the header exists for.

Separate from #50 deliberately, so the proofs PR stays scoped to proofs and this can be judged on its own.

🤖 Generated with Claude Code

check-cyrillic fails on .claude/skills/gardener/SKILL.md and has failed
on main for an unknown period, so every pull request to this repository
starts red on a file it does not touch.

The checker states the remedy itself: add the LEGACY header. Applied
verbatim, as a YAML comment immediately after the name field so that it
lands inside the 500-character window the checker reads and leaves the
frontmatter syntactically intact -- verified both, and the frontmatter
still parses.

Nothing is translated and nothing else is touched. This only records
what the file already is, which is what the header is for.
@gHashTag

Copy link
Copy Markdown
Owner Author

Folded into #50 instead. The two were complementary — this branch fixed check-cyrillic but branched from main and so lacked #50's signature-gate and claims-ledger fixes, while #50 had those and not this. Cherry-picked here so one pull request goes green on its own rather than two that each need the other.

@gHashTag gHashTag closed this Aug 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant