docs(i18n): add Polish localization scout - #3121
Conversation
Signed-off-by: Dante <duanjl.china@gmail.com>
ECC Tools / Security EvidenceCommit: Security evidence gate passed (success) No security-sensitive scanner-evidence gap detected. Mode: enforce Scanned 22 changed file(s). No missing scanner-evidence signal was detected. Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / PR Risk TaxonomyCommit: PR taxonomy review recommended (neutral) Detected 2 PR taxonomy bucket(s): Install Manifest Integrity, CI/CD Recommendation. Scanned 22 changed file(s). Roadmap taxonomy buckets: Install Manifest IntegrityInstall manifests, plugin metadata, and shipped skills should stay synchronized with user-facing setup guidance. Signals:
Paths:
CI/CD RecommendationCI, dependency, coverage, and contract signals should be routed into follow-up checks or verification work. Signals:
Paths:
Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / Reference Set ReadinessCommit: Reference set readiness gaps detected (neutral) Reference evidence present for 0/7 areas (0%) across 22 changed file(s). This check is based on files changed in this PR. Repository-level readiness is still reported by
Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / Hosted Promotion ReadinessCommit: Hosted promotion readiness passed (success) No hosted promotion evidence gaps detected across 22 changed file(s); 0 corpus scenarios had matching evidence. This check compares PR file changes against the evaluator/RAG promotion corpus in No evaluator corpus scenarios matched this PR. Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (37)
🧰 Additional context used📓 Path-based instructions (3)Lightweight agents with frequent invocation Pair programming and code generation Worker agents in multi-agent systems Main development work Orchestrating multi-agent workflows Complex coding tasks Complex architectural decisions Maximum rea...📄 CodeRabbit inference engine (.cursor/rules/common-performance.md) Files:
NEVER hardcode secrets in source code - ALWAYS use environment variables or a secret manager📄 CodeRabbit inference engine (.cursor/rules/common-security.md) Files:
Do not hardcode secrets, API keys, passwords, or tokens📄 CodeRabbit inference engine (.github/copilot-instructions.md) Files:
🔇 Additional comments (1)
📝 SummarySummary by CodeRabbit
WalkthroughThe PR adds Polish documentation and terminology guidance, links Polish README files from existing language selectors, includes the files in published packages, and adds Polish locale installation metadata, aliases, and tests. ChangesPolish localization
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~12 minutes Change: Feature Sequence Diagram(s)sequenceDiagram
participant CLI
participant resolveInstallPlan
participant InstallManifests
participant PolishDocs
CLI->>resolveInstallPlan: --locale pl-PL
resolveInstallPlan->>InstallManifests: resolve locale:pl and docs-pl
InstallManifests-->>resolveInstallPlan: docs/pl source and install target
resolveInstallPlan->>PolishDocs: plan docs/pl/README.md installation
Merge Risk: ⚪ Minimal · up to The Polish documentation and locale installation support are internally consistent, with no identified user-facing or publishing failure blocking merge. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 2 functions across 2 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
ECC Tools / Security EvidenceCommit: Security evidence gate passed (success) No security-sensitive scanner-evidence gap detected. Mode: enforce Scanned 22 changed file(s). No missing scanner-evidence signal was detected. Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / PR Risk TaxonomyCommit: PR taxonomy review recommended (neutral) Detected 2 PR taxonomy bucket(s): Install Manifest Integrity, CI/CD Recommendation. Scanned 22 changed file(s). Roadmap taxonomy buckets: Install Manifest IntegrityInstall manifests, plugin metadata, and shipped skills should stay synchronized with user-facing setup guidance. Signals:
Paths:
CI/CD RecommendationCI, dependency, coverage, and contract signals should be routed into follow-up checks or verification work. Signals:
Paths:
Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / Reference Set ReadinessCommit: Reference set readiness gaps detected (neutral) Reference evidence present for 0/7 areas (0%) across 22 changed file(s). This check is based on files changed in this PR. Repository-level readiness is still reported by
Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / Hosted Promotion ReadinessCommit: Hosted promotion readiness passed (success) No hosted promotion evidence gaps detected across 22 changed file(s); 0 corpus scenarios had matching evidence. This check compares PR file changes against the evaluator/RAG promotion corpus in No evaluator corpus scenarios matched this PR. Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
What Changed
docs/pl/: a Polish getting-started and core-concepts guide plus a terminology glossary.docs-plandlocale:pl, with bothplandpl-PLinstaller aliases, and included the locale in the npm publish surface.The Polish guide records English source commit
8321021cand its exact translated scope. It links the complete English README rather than presenting this first increment as a full translation.Why This Change
This implements the scout proposed by @majevva in #3096 and follows their correction to use the short
pldirectory code. It also follows the owner guidance and merged German precedent in #1980/#2029: keep new locale docs underdocs/<locale>/, establish terminology, make the locale discoverable, and register installer support in the same bounded PR.The initial guide deliberately focuses on setup, the major ECC surfaces, safety, and the translation workflow. Further translation can continue incrementally by domain without creating another large overlapping localization PR.
Refs #3096
Testing Done
node tests/run-all.js)Focused repository checks completed:
node tests/lib/locale-install.test.js— 12 passed, 0 failednode tests/lib/install-manifests.test.js— 41 passed, 0 failednode scripts/ci/validate-install-manifests.js— validated 38 modules, 85 components, and 7 profilesnode tests/scripts/npm-publish-surface.test.js— 2 passed, 0 failedmarkdownlint 'docs/pl/**/*.md'— cleangit diff --check— cleanThe aggregate
npm testwas not run because this documentation/manifest slice was covered by the focused checks above and the repository aggregate currently includes local UI/E2E paths outside this run's allowed validation scope.Type of Change
fix:Bug fixfeat:New featurerefactor:Code refactoringdocs:Documentationtest:Testschore:Maintenance/toolingci:CI/CD changesSecurity & Quality Checklist
If you changed dependencies or
package.json(bin/files/ deps)yarn install --mode=update-lockfile;yarn.lockremained unchanged.If you added a skill, command, agent, hook, or CLI tool
Not applicable; this adds a documentation locale and installer manifest entries.
Documentation