Repository navigation
Refactor/english doc comments - #141
Merged
Merged
Conversation
Introduce unified English comment rules (docs/COMMENT_CONVENTIONS.md) and a set of i18n tooling scripts for extracting, checking, and repairing message keys/tokens across the workspace.
Apply the new comment conventions across all crates: translate rustdoc comments, utoipa descriptions, and error/ignore messages to English, and update test fixtures accordingly. String literals that intentionally exercise i18n (e.g. mock data) are left as-is per docs/COMMENT_CONVENTIONS.md.
) Add an optional markdown `description` to bugs, end-to-end: - migration 0111 adds the `description` column to ms_bug - domain NewBug/Bug carry description; create/update use cases and the pg/in_memory/http adapters persist and return it - web: MarkdownEditor for create/edit, MarkdownRenderer in a read-only detail drawer opened on row click Fix the empty assignee dropdown: useMemberOptions now merges project members with the global user directory, so a handler can always be selected even when a project has no members. Handler names link to /user.
…p bumps) (#140) * feat(delivery): DeepCode (DEEPCODE) executor + per-executor run guide - ExecutorKind::DeepCode end to end: domain enum (ALL remains the single authoritative kind list), in-memory + Redis queues, agent-runtime backend (deepcode exec --json, DEEPCODE_CMD override), CLI normalize, MCP dispatch schema, web executor labels - docs/EXECUTORS(.zh-CN).md + USAGE(.zh-CN).md: DeepCode run recipe, env override and backend tables - verified: cargo check/test on delivery + agent-runtime + shepherd-cli, web tsc typecheck; a real deepcode CLI run was not exercised here * chore(deps): upgrade h2 to 0.4.16 and rustls to 0.23.45 per cargo audit - RUSTSEC-2026-0258 (h2 unbounded empty DATA frames): h2 0.4.15 -> 0.4.16 - RUSTSEC-2026-0285 (rustls TLS 1.3 handshake across encryption levels): rustls 0.23.40 -> 0.23.45, rustls-webpki 0.103.13 -> 0.103.15 * feat(server): Jev (TypeSafe System One) verification judge - JevJudge implements Judge: one noul question per acceptance criterion in a single POST to the TypeSafe System One endpoint; passes only when every probability reaches SHEPHERD_JEV_THRESHOLD (default 0.8) - build_judge() priority: Jev (SHEPHERD_JEV_API_KEY, falls back to TYPESAFE_API_KEY) -> LLM judge -> SHEPHERD_JUDGE_URL HTTP -> accept-all; HTTP/parse errors fail closed - docs/USAGE(.zh-CN).md: judge config table + fail-closed note
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.
No description provided.