PROCESS: require signed target-project issue comments and explicit issue-language policy #12

Problem

Parallel agent work on target-project issues exposed another canon gap:

• comments on target-project GitHub issues are not explicitly required to be signed by agent role/model in the current canonical docs;
• the canon also does not explicitly state which language should be used for issue comments when a target project has a dominant working language.

This creates two recoverability problems:

1. a fresh agent cannot reliably tell which agent/role authored a specific comment;
2. issue discussions can drift between languages instead of following the target project's working language.

Why local edits are not enough

A local edit to AGENTS.md in one session does not make this rule canonical. Per framework rules, this needs an explicit shared discussion artifact and then a reviewed promotion path.

Proposed canon change

Add target-issue comment rules to AGENTS.md and/or OPERATIONS.md

Suggested text:

Target-Project Issue Comment Discipline

When agents comment on GitHub issues in a target project:

• every comment must be signed at the end using — Роль (Модель) or the equivalent role/model format in the target language;
• comments should use the working language of the target project;
• if the target-pack specifies an issue language explicitly, that setting overrides the default heuristic;
• comments should move the issue toward its next artifact rather than leave anonymous or free-floating discussion.

Suggested default language rule

If the target-pack does not specify issue language explicitly, default to the primary language used in the target repository's README and active issue discussions.

Why this matters

This improves zero-start continuity for parallel work:

• authorship becomes visible inside the artifact itself;
• mixed-agent discussions stay attributable;
• contributors and future agents know which language to expect;
• issue threads remain aligned with project norms instead of tool defaults.

Requested outcome

Decide whether this should become explicit canon and where it should live (AGENTS.md, OPERATIONS.md, or both).

Expected next artifact if accepted

A docs-only PR updating the canonical files with the agreed wording.