Repository navigation
docs: sync glossary + Russian README to image system (PRD-030 follow-up) - #124
Merged
Merged
Conversation
Tactical follow-up to #121 (PR #122) — agent context files and the Russian README still described the legacy `dist/` + `dist-experimental/` shape. Bring them in line with what `develop` actually ships: - README.ru.md: new "Образы (images)" section mirroring README.md; package summary in "Что получаешь" notes the per-image bundle. - docs/agents/domain.md: replace "legacy dist/" + "opt-in dist-experimental/" entries with image / feature-flag definitions; document `--experimental` as deprecated alias. - docs/agents/paths.md: top-level table swaps `dist-experimental/` for `dist-nightly/` + `config/`; tarball inventory now reads from `config/images.json`. No code changes — `bin/`, `scripts/`, `template/` untouched, smoke unchanged. Tactical depth per rule 11 (doc copy-edit, no public behaviour change), so no new Forgeplan artifact required; references the existing PRD-030 / RFC-026 / ADR-005 chain. Refs: PRD-030, RFC-026, ADR-005, #121 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.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.
Summary
Tactical follow-up to #121 (PR #122). Three doc files still described the
legacy
dist/+dist-experimental/shape — bring them in line withwhat
developactually ships post-PR-#122.README.ru.md— new "Образы (images):stable(по умолчанию) иnightly" section mirroringREADME.md; updated "Что получаешь" line to mention the per-image bundle.docs/agents/domain.md— replace legacydist/+ opt-indist-experimental/entries with Image + Feature flag definitions, and document--experimentalas a deprecated alias.docs/agents/paths.md— top-level table swapsdist-experimental/fordist-nightly/+config/; tarball inventory now referencesconfig/images.jsonfor the canonical image list.Why
docs/agents/*.mdare auto-loaded by thefpl-skillsskill set. Stale terms there mean every future agent invocation starts with an inaccurate mental model of the package shape — exactly the kind of drift rule 11 (Forgeplan as single source of truth) is meant to prevent. PRD-030 already activated; this PR closes the doc gap without re-opening the artifact discipline.Scope
No code changes —
bin/,scripts/,template/untouched. Smoke status from PR #122 still applies. Tactical depth per rule 11 (docs without behaviour change), so no new Forgeplan artifact required.Test plan
grep -rn 'dist-experimental\|--experimental' docs/shows only the--experimentaldeprecated alias mention indomain.md.git diff --statis bounded to the three doc files.Refs: PRD-030, RFC-026, ADR-005, #121
🤖 Generated with Claude Code