Skip to content

Harden public Unity localization safety and release workflow - #3

Merged
timeance merged 2 commits into
mainfrom
agent/tmp-font-compatibility
Jul 14, 2026
Merged

timeance merged 2 commits into
mainfrom
agent/tmp-font-compatibility

Conversation

@timeance

Copy link
Copy Markdown
Owner

Summary

  • contain manifest targets and payloads within their declared game/package roots, rejecting absolute, drive-relative, UNC, traversal, NUL, and resolved link-escape paths
  • stage and validate Unity writeback before transactional commit, with source-change detection, per-file backups, rollback, PathID/object verification, manifest relocation, and explicit opt-in for raw fallback
  • keep raw UTF-8 candidates audit-only by default instead of exposing them as translator-facing rows
  • make the AiNiee bridge fail closed with atomic cache writes, cooperative locking, unique backups, index/hash/source/status validation, and explicit partial-review mode
  • support app-local TTF/OTF/TTC runtime fonts, with validation, backup/rollback, provenance and SHA-256 reporting
  • document a redistributable Noto-first font release policy while excluding Arial Unicode assets without explicit redistribution permission
  • add CI, bounded dependencies, Unity version detection, PowerShell 5.1-compatible instructions, and expanded public-repository documentation

Why

The public workflow previously relied on several optimistic assumptions around manifest paths, partial translation state, direct Unity asset mutation, and font availability. These changes make unsafe or ambiguous states explicit failures and give users a practical app-local font path without encouraging redistribution of unlicensed assets.

Validation

  • python -m unittest discover: 29 tests passed, 1 skipped because the current Windows process cannot create symlinks
  • both skills pass quick_validate
  • Python 3.12 compileall passes
  • all 18 Unity CLI entry points accept --help
  • CI YAML parses successfully
  • git diff --check passes

Remaining runtime validation

This change has not yet been canary-tested inside the target Unity game. IL2CPP runtime behavior and cross-version compatibility of static TMP SDF bundles still require testing against representative games before those paths can be described as universally compatible.

@timeance
timeance force-pushed the agent/tmp-font-compatibility branch from 5346315 to 9fa7d2a Compare July 14, 2026 20:41
@timeance
timeance marked this pull request as ready for review July 14, 2026 20:42
@timeance
timeance merged commit 603553b into main Jul 14, 2026
4 checks passed
@timeance
timeance deleted the agent/tmp-font-compatibility branch July 14, 2026 20:43
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