simplify-code-base run a7b8fa: 52 iterations of folding duplicated decisions onto single seams #96

Merged

weiwen merged 52 commits from gnhf/simplify-code-base-r-a7b8fa into main 2026-08-13 13:38:58 +08:00

Conversation 0 Commits 52 Files changed 65 +4947 -3665

weiwen commented 2026-08-13 13:32:02 +08:00

Owner

Copy link

Output of a long-running simplify-code-base pass (run a7b8fa, 52 iterations). Each commit is one iteration: pick a lens, find every place the codebase spells the same decision more than once, fold the copies onto one seam, and pin whatever contract turned out to have no test. Every iteration is atomic and self-contained, so this reads best commit-by-commit; it is expected to squash-merge.

65 files, +4947/-3665.

Bugs the folding surfaced

Deduplication kept turning up copies that had already drifted apart. These are the ones where the drift was live behaviour, not just noise:

• just check had been red on main since 2026-08-13 at its very first step (cargo fmt --check), so every CI run failed and the needs: check image publish never ran (gnhf 38). The gate is now green, and widened to cover the other two languages in the tree — every tracked *.nix through nixfmt --check and every tracked *.sh through shellcheck -x, both pinned through the flake (gnhf 39).
• Persisted schedules were orphaned on the live deployment: #90's blanket TOML sweep renamed schedules.json to schedules.toml in config.rs alone (gnhf 17).
• An HTTP-only deployment fired no schedule at all, because the schedule timer was gated on a Telegram dispatcher it had stopped depending on (gnhf 25).
• Scheduled send/prompt lost markdown rendering and pagination in #67 — a scheduled prompt reply over Telegram's per-message cap was rejected outright (gnhf 24).
• The sudo credential hard link silently degraded to a copy on every spawn after 2eaf3ca: linking straight at the destination hit EEXIST (b0d13e7).
• A missing config on the packaged deployment reported "Read-only file system" instead of the missing file, because Config::load create-if-absent ran against a deliberately read-only /etc (gnhf 23).
• api- chat targets passed schedule creation and were then dropped at every fire — creation validated less than fire requires (gnhf 21).
• The Rich markdown path measured the unsanitized source against Telegram's cap, so a live page whose appended closers pushed it over the limit was sent anyway (gnhf 20).
• A sandbox-escape shape the test suite had already drifted into, closed by folding PiSpawnConfig's include_sudo_only_skills / agent_auth_path into SpawnMode itself (gnhf 10, finished in 33).
• Four inert config knobs wired up: message_burst_debounce_ms (gnhf 1), [telegram.voice].max_duration_secs and [logging].format (gnhf 2).
• A test-only ETXTBSY flake measured at 274/4000, closed at its write side by routing executable-script writes through a child process; the production retry loop that had been papering over it is gone (gnhf 48).

Dead code removed

Mechanisms whose last producer or caller was deleted upstream and never followed through: the scheduled-push delivery channel whose only producer #67 removed a month prior (gnhf 4), the [[pi.models]] fallback list whose entries past [0] were never read (gnhf 5), the secret_env capability-gated-secret forwarding left always-empty by #90 (gnhf 6, 47), the ChatId::TelegramDm addressing axis superseded by ADR 0023's Sender (gnhf 3), the deployment-side sandbox-account provisioning orphaned by #94's privilege-drop removal (gnhf 8, 9), and the Node/TypeScript toolchain stranded by the .sandcastle agent loop's removal (gnhf 30).

Seams introduced

state_file::{write_atomic, install_atomic}, schedule::{Verb, Selector}, control_plane::{Partition, Destination}, pi::{read_bounded_line, bwrap_command, pi_store_command}, telegram::markdown::Splitter, telegram::view::{send_page, inline_content}, session::run_ephemeral_kind, chat_id::ChatSession, main's Target/Selection clap groups, transcribe::MODEL_FILES, test_script::write_executable, and a shared tests/hitl/common.sh.

Docs

Prose that had drifted from the code it describes: extensions-as-per-user-capability and the fixed evie service account (gnhf 31), the setuid/setgid privilege drop #94 removed including three docs falsely claiming bwrap builds its namespace unprivileged (gnhf 8), and the two agent-facing triage docs pointing at the removed loop's phantom stages (gnhf 30). Touches README, CONTEXT.md, ADR 0011/0023, flake.nix, and the config template.

Verification

nix develop .#ci -c just check passes on the branch tip: 539 tests, 0 failed, exit 0. That is the whole CI gate, so this is green in CI.

Review notes

• No issue to close: this run was not ticket-driven.
• Wire-format changes to review with care: control_plane's ControlRequest (gnhf 45, 49, and the flattened Target/Selection in main.rs's CLI), and the schedules.json filename restoration (gnhf 17) which affects an existing live state file.
• Config surface changes: [[pi.models]] collapsed back to scalar pi.provider/pi.model, [pi.capability_env] and [sandbox] gone, four SessionManagerConfig path fields now required.

Output of a long-running `simplify-code-base` pass (run `a7b8fa`, 52 iterations). Each commit is one iteration: pick a lens, find every place the codebase spells the same decision more than once, fold the copies onto one seam, and pin whatever contract turned out to have no test. Every iteration is atomic and self-contained, so this reads best commit-by-commit; it is expected to squash-merge. 65 files, +4947/-3665. ## Bugs the folding surfaced Deduplication kept turning up copies that had already drifted apart. These are the ones where the drift was live behaviour, not just noise: - **`just check` had been red on `main` since 2026-08-13** at its very first step (`cargo fmt --check`), so every CI run failed and the `needs: check` image publish never ran (gnhf 38). The gate is now green, and widened to cover the other two languages in the tree — every tracked `*.nix` through `nixfmt --check` and every tracked `*.sh` through `shellcheck -x`, both pinned through the flake (gnhf 39). - **Persisted schedules were orphaned on the live deployment**: #90's blanket TOML sweep renamed `schedules.json` to `schedules.toml` in `config.rs` alone (gnhf 17). - **An HTTP-only deployment fired no schedule at all**, because the schedule timer was gated on a Telegram dispatcher it had stopped depending on (gnhf 25). - **Scheduled `send`/`prompt` lost markdown rendering and pagination** in #67 — a scheduled prompt reply over Telegram's per-message cap was rejected outright (gnhf 24). - **The sudo credential hard link silently degraded to a copy** on every spawn after `2eaf3ca`: linking straight at the destination hit `EEXIST` (`b0d13e7`). - **A missing config on the packaged deployment reported "Read-only file system"** instead of the missing file, because `Config::load` create-if-absent ran against a deliberately read-only `/etc` (gnhf 23). - **`api-` chat targets passed schedule creation and were then dropped at every fire** — creation validated less than fire requires (gnhf 21). - **The Rich markdown path measured the unsanitized source against Telegram's cap**, so a live page whose appended closers pushed it over the limit was sent anyway (gnhf 20). - **A sandbox-escape shape the test suite had already drifted into**, closed by folding `PiSpawnConfig`'s `include_sudo_only_skills` / `agent_auth_path` into `SpawnMode` itself (gnhf 10, finished in 33). - **Four inert config knobs** wired up: `message_burst_debounce_ms` (gnhf 1), `[telegram.voice].max_duration_secs` and `[logging].format` (gnhf 2). - **A test-only ETXTBSY flake** measured at 274/4000, closed at its write side by routing executable-script writes through a child process; the production retry loop that had been papering over it is gone (gnhf 48). ## Dead code removed Mechanisms whose last producer or caller was deleted upstream and never followed through: the scheduled-push delivery channel whose only producer #67 removed a month prior (gnhf 4), the `[[pi.models]]` fallback list whose entries past `[0]` were never read (gnhf 5), the `secret_env` capability-gated-secret forwarding left always-empty by #90 (gnhf 6, 47), the `ChatId::TelegramDm` addressing axis superseded by ADR 0023's `Sender` (gnhf 3), the deployment-side sandbox-account provisioning orphaned by #94's privilege-drop removal (gnhf 8, 9), and the Node/TypeScript toolchain stranded by the `.sandcastle` agent loop's removal (gnhf 30). ## Seams introduced `state_file::{write_atomic, install_atomic}`, `schedule::{Verb, Selector}`, `control_plane::{Partition, Destination}`, `pi::{read_bounded_line, bwrap_command, pi_store_command}`, `telegram::markdown::Splitter`, `telegram::view::{send_page, inline_content}`, `session::run_ephemeral_kind`, `chat_id::ChatSession`, `main`'s `Target`/`Selection` clap groups, `transcribe::MODEL_FILES`, `test_script::write_executable`, and a shared `tests/hitl/common.sh`. ## Docs Prose that had drifted from the code it describes: extensions-as-per-user-capability and the fixed `evie` service account (gnhf 31), the setuid/setgid privilege drop #94 removed including three docs falsely claiming bwrap builds its namespace unprivileged (gnhf 8), and the two agent-facing triage docs pointing at the removed loop's phantom stages (gnhf 30). Touches `README`, `CONTEXT.md`, ADR 0011/0023, `flake.nix`, and the config template. ## Verification `nix develop .#ci -c just check` passes on the branch tip: 539 tests, 0 failed, exit 0. That is the whole CI gate, so this is green in CI. ## Review notes - No issue to close: this run was not ticket-driven. - Wire-format changes to review with care: `control_plane`'s `ControlRequest` (gnhf 45, 49, and the flattened `Target`/`Selection` in main.rs's CLI), and the `schedules.json` filename restoration (gnhf 17) which affects an existing live state file. - Config surface changes: `[[pi.models]]` collapsed back to scalar `pi.provider`/`pi.model`, `[pi.capability_env]` and `[sandbox]` gone, four `SessionManagerConfig` path fields now required.

weiwen added the

ready-for-human

label 2026-08-13 13:32:02 +08:00

weiwen added 52 commits 2026-08-13 13:32:02 +08:00

gnhf 1: Fixed the inert message_burst_debounce_ms config knob by threading it into collect_burst, and collapsed the redundant 11-argument burst-sender construction path into the existing TelegramDeps::burst_sender helper. 7d6d86767b

gnhf 2: Wired the last two inert config knobs ([telegram.voice].max_duration_secs and [logging].format), both left half-plumbed by the #90 config restructure, and added validation plus tests locking each in place. f2dddde9a4

gnhf 3: Deleted the never-constructed ChatId::TelegramDm addressing axis — a second DM-session identity model superseded by ADR 0023's Sender axis — removing the variant, its two dead constructors, its parse branch, and the four match arms that only existed to reject it. 1d496cad88

gnhf 4: Deleted the orphaned scheduled-push delivery channel (DeliveryItem, delivery_consumer, deliver_silent) whose only producer was removed by PR #67 a month ago, leaving a consumer task idling on a receiver nobody wrote to. e4b4ec43b3

gnhf 5: Collapsed the never-implemented [[pi.models]] fallback list — a plural config surface whose doc promised fallbacks but whose entries past [0] were never read — back to scalar pi.provider/pi.model, which also repairs the Nix module's documented example. e1befab7db

gnhf 6: Deleted the vestigial secret_env capability-gated-secret forwarding parameter — always empty in production since #90 removed [pi.capability_env] and its resolver — along with the dangling forwarded_secret_names doc references, five tombstone comments, and four operator-facing docs still instructing readers to configure the deleted table. 60053ea5e9

gnhf 7: Made ControlPlane's session_manager and schedule_store non-optional, deleting two guard macros and the two unreachable error responses they existed to emit. 931dfa2146

gnhf 8: Deleted the vestigial user/group privilege-drop fields on VouchedUser and corrected the source comments, config template, ADRs and module maps still describing the setuid/setgid reuid that #94 removed, including three that falsely claimed bwrap builds its namespace unprivileged. 65b301d23f

gnhf 9: Deleted the deployment-side sandbox-account provisioning that #94's privilege-drop removal orphaned (the image entrypoint's EVIE_SANDBOX_USERS /etc/passwd machinery, the NixOS module's evie drop account and its three dead config keys) and narrowed the 0711/0644 permission widenings the drop had required, including two set_permissions(0o711) calls in control_plane.rs that were overriding systemd's RuntimeDirectoryMode at every boot. 706d62659e

gnhf 10: Folded the two PiSpawnConfig fields that restated what SpawnMode already decides (pi_argv's include_sudo_only_skills bool and the Sandboxed-only agent_auth_path) into the mode itself, closing a sandbox-escape shape that the test suite had already drifted into. ab1ee60393

gnhf 11: Collapsed the guest-reply turn's two parallel Options (view/query_id, exactly one of which is ever Some) into a single GuestTarget enum, deleting the two unreachable else arms that existed only to answer for the impossible both-None state. 0024834a71

telegram: drop Route::Session's never-read capabilities payload, collapsing resolve_guest_message into resolve_message with addressed = true 7df3aadffb

users: fold users.toml's second skill-grant surface into Capability::Skill at load, collapsing SpawnTarget's parallel skills field and extension_and_skill_dirs's second resolution loop, and correct the README/control-skill capability vocabulary still advertising the withdrawn network/extensions/<name> grants 3cfdf47d23

pi: fold the sandboxed-session and sandboxed-script Command builders into one bwrap_command seam, making the env_clear that keeps the daemon's root environment out of a bwrap spawn structural rather than a per-caller obligation stated in the memfd helper's doc, and pin the previously untested visible argv of the script path ddb9970874

gnhf 15: Folded ScheduleStore::save and UserRegistry::persist — the run's last cross-module textual duplicate, two hand-rolled copies of the same create-parent + temp + rename dance — into a single state_file::write_atomic seam, and fixed the fixed-temp-name race and with_extension misuse both copies shared. 9295430b88

session: restore the sudo credential hard link that 2eaf3ca broke by linking straight at the destination, folding the install into a state_file::install_atomic seam so the link is retried through a fresh scratch name on every spawn instead of hitting EEXIST and silently degrading to a copy b0d13e77e1

gnhf 17: Restored the Schedule store's schedules.json path that #90's blanket TOML sweep renamed to schedules.toml in config.rs alone, which had orphaned the live deployment's persisted schedules, and removed the store's second spelling of the file name so the derived path is the only place it is written. b3023ef132

pi: fold the three spellings of pi's in-home provider-credential path into one agent_auth_in_home seam - the bwrap overlay target, the reserved mount a per-user bind may not shadow, and the Sudo path's physical install, which must agree exactly or the overlay becomes shadowable - and clear the four doc-comment defects rustdoc already flagged, including bwrap_argv's 31-line doc that cee2416's push_bind extraction stranded on the four-line helper 63a01bfead

control_plane: fold the four hand-spelled ControlPlane constructions into one with_deliverer seam - the #[cfg(test)] twin of new that re-listed all ten fields, the raw test struct literal that re-listed them a third time with a dangling self_weak, and the five identical recording-plane preambles - and restore manager_with_fake_ephemerals doc comment that test_managers insertion stranded on the wrong function 2b17e6a5f6

gnhf 20: Folded telegram/markdown.rs's two parallel pagination pipelines (which ADR 0011 had explicitly chosen not to share) into one Splitter parameterized by renderer/measure/cap, fixing the Rich path's habit of measuring the unsanitized source against Telegram's cap so a live page whose appended closers pushed it over the limit was sent anyway. 24a092b03a

gnhf 21: Closed the gap where schedule creation validated less than schedule fire requires — an api- chat target persisted happily and was then dropped at every fire — and folded the four spellings of the send|prompt|run grammar into one schedule::Verb enum. 13e69aede9

gnhf 22: Folded the HITL harness's three divergent binary/config-render spellings into one common.sh seam, deleted the two template keys whose mechanisms were removed months ago (__SANDBOX_USER__, [rpc]), and gave the rendered template its first schema-drift test. 726e4c4732

gnhf 23: Split the create-if-absent write out of Config::load into a daemon-only load_or_create, so a missing config on the packaged deployment (whose unit deliberately makes /etc read-only) reports the missing file instead of masking it as a "Read-only file system" write failure, and folded main.rs's hardcoded state-root fallback into resolve_state_dir. 1080ec3e24

gnhf 24: Routed scheduled send/prompt fires through the Deliverer seam the immediate verbs already use, restoring the markdown rendering and pagination #67 dropped (a scheduled prompt reply over Telegram's per-message cap was rejected outright), and folded ControlPlane's two constructors into one now that the deliverer is built once and shared. e9f64a2ffd

gnhf 25: Made the Deliverer seam total with an unconfigured_deliverer null object, deleting ControlPlane's Option deliverer branch and un-gating the schedule timer from the Telegram dispatcher it stopped depending on last iteration, so an HTTP-only deployment no longer silently fires no schedule at all. 2721c5bae9

gnhf 26: Folded the cross-module duplicate of the 20-field SessionManagerConfig test fixture into one crate-shared session::test_manager_config, and cut Schedule's six hand-spelled test literals down to one per module. a95197d887

gnhf 27: Replaced the use_draft/live_edit boolean pair that telegram/mod.rs's streaming path derived from DeliveryContext::streaming_mode and threaded as parameters into three functions that already held the mode, so every decision point now matches on StreamingMode exhaustively. 8ec29ce222

gnhf 28: Folded pi.rs's three extension-provisioning subprocess spellings into one pi_store_command builder plus two bounded runners (which also gives pi install the --no-approve its two siblings pass), and gave the inverse pair extension_install_source/extension_package_name one shared spelling of the source-scheme predicate they must agree on. 54548fb306

gnhf 29: Deleted the middle layer of the Telegram delivery-knob mirror: TelegramDeps no longer restates the five TelegramConfig values (plus client/manager) that existed only to be copied into a DeliveryContext at two hand-spelled 9-field sites, and now holds the one context build_deps derives from config. 7bf74530cf

gnhf 30: Deleted the Node/TypeScript toolchain and Justfile recipes stranded by the .sandcastle agent loop's removal a month ago, repaired the broken build-docker-image recipe, and repointed the two agent-facing triage docs off the loop's phantom stages onto the .pi/workflows/implement-issue.ts workflow that actually runs. 6097c0c6c2

gnhf 31: Repaired the six surviving prose claims across README, flake.nix, config.rs and pi.rs that still described extensions as a per-user Capability grant and the NixOS unit as running under a fixed evie account, both of which the code stopped doing (ADR 0023's extensions-are-global amendment and #94's privilege-drop removal). 4f47d0eddb

gnhf 32: Made the four SessionManagerConfig path fields that the daemon always derives from the State Root non-optional, deleting the three None arms only test fixtures could reach and correcting config.rs's claim that a missing provider credential merely skips the sandbox bind when it in fact fails every turn. a78f09bdc0

gnhf 33: Made SpawnMode::Sandboxed's agent_auth_path non-optional now that resolved_agent_auth canonicalizes the credential before both production spawns, and finished the tolerance iteration 32 found dead by turning the credential overlay into a hard --ro-bind. 6d5cb6db97

gnhf 34: Folded the three spellings of the sherpa-onnx model file set (config.rs's validation list, transcribe.rs's download list, and Transcriber's four joined PathBuf fields) into one transcribe::MODEL_FILES table, and moved the sherpa invocation onto a testable sherpa_argv builder. 6ebb4c9cbd

gnhf 35: Collapsed main.rs's three near-identical interface-racing wrappers (run_telegram_and_http, run_telegram_only, run_http_only) into one JoinSet of the enabled interfaces, removing a 2x2-minus-one dispatch matrix and the two divergent spawn disciplines it ran under. 992b19f6c7

gnhf 36: Folded control_plane.rs's two hand-spelled unix-socket lifecycles (the unscoped daemon endpoint and each per-session scoped socket) into one bind_unix_socket seam plus one serve(listener, scope) accept loop, making the 0700-directory/0600-socket permission contract structural and giving it its first test coverage. 5df93e1386

gnhf 37: Folded pi.rs's two open-coded bounded stdout line reads (read_agent_response and drain_aborted) into one read_bounded_line seam returning a three-outcome PiLine, making the per-line OOM cap and the idle timeout one contract instead of two copies that had already drifted on their error wording. edb0322cce

gnhf 38: Repaired the repo's own just check gate, red on main since 2026-08-13 at its first step (cargo fmt --check) so every CI run was failing and the needs: check image publish never ran, and widened the gate to the two checks this run had been running by hand every iteration. 332a2b627a

gnhf 39: Widened the repo gate past Rust to the other two languages it ships (nixfmt --check and shellcheck -x, both pinned through the flake), and repaired the ~40 lines of nixfmt drift the two NixOS/home-manager modules had accumulated while nothing checked them. 78906b3819

gnhf 40: Folded session.rs's two Ephemeral Session entry points (run_ephemeral and run_ephemeral_isolated) onto one run_ephemeral_kind seam parameterized by an Ephemeral confinement, so the test-process factory is consulted in one place rather than at two different depths, and gave the isolated summarizer its first test. d6ef991301

gnhf 41: Gave telegram/mod.rs's StreamState the chat_id half of the destination it already stored thread_id for, deleting that parameter from four of its methods plus finish_streaming_turn and folding the four duplicate draft-refresh call chains onto two seams. 3c776badce

gnhf 42: Wired the three real captured pi --mode rpc transcripts under tests/fixtures/pi-rpc/ into pi.rs's test module, closing the gap where 1.3 MB of verbatim wire data documented as test fixtures was read by nothing while every parser regression was hand-transcribed inline. cdc7273b3d

gnhf 43: Collapsed the duplicate block-opening and preview signals pi's two coexisting RPC schemas each emitted for the same content, gating message_start on the assistant role and routing every preview send through one send_if_new dedup. db3cc61c80

gnhf 44: Folded the five hand-spelled row-selection predicates inside ScheduleStore onto one Selector (chat, topic filter, optional name, owner), so the per-sender scoping the untrusted socket rests on is a required field of the selection rather than a rule each accessor restates, and pinned the topic-scoped upsert that had no test. 151fb7ba88

gnhf 45: Folded the scoped-caller narrowing that control_plane.rs's three schedule verbs each restated (own topic, own sender) into a single Partition built from the request's ambient scope, deleting two helpers and three hand-written Selector literals, and pinned the topic half of that narrowing which no test covered. fc0727b3ad

gnhf 46: Folded the fired-schedule destination that main.rs threaded as three separate parameters (parsed chat, its derived numeric Telegram id, frozen topic) into one FireTarget resolved in a single place, replaced the hand-written re-spelling of ChatId::telegram_numeric_id, and pinned the resolution no test covered. 7d99f5b33e

gnhf 47: Closed the handed-down "capability-gated secret" doc-bitrot starter across pi.rs/users.rs (a forwarding mechanism #90 deleted) and gave the bwrap --args memfd delivery those docs describe its first test, closing a gap where dropping the rewind broke every sandboxed spawn with the whole suite green. 1d912bd953

gnhf 48: Closed the handed-down ETXTBSY flake at its write side by folding three duplicate executable-script test writers onto one test_script::write_executable seam that writes via a child process, then deleted the production retry loop and the fused four-in-one test that had been papering over that test-only race. f5153167d5

gnhf 49: Folded the chat+topic destination that main.rs's CLI restated across seven subcommands (14 #[arg] declarations, 8 hand-written help strings) onto one Target/Selection pair of flattened clap groups, restoring the $EVIE_CHAT_ID fallback documentation to the three verbs whose help had drifted away from it, and pinned that contract per flag. 5001757c6d

gnhf 50: Folded the numeric Telegram chat id that telegram/mod.rs threaded beside the SessionKey already naming it into one ChatSession minted by resolve_message, deleting fourteen parameter positions across the message/turn path (and one too_many_arguments allow) plus the two hand-written "same key, other sudo slot" re-spellings, and pinned the pairing no test covered. 9cfb072ece

gnhf 51: Deleted the last three hand-rebuilds of a SessionKey the caller already held, folding them onto one SessionManager::clear_both_sudo_slots(key) and a Route::DropUnaddressed(ChatSession), which also removed SessionManager::clear_session entirely since http.rs's http_key already named the key it was re-deriving. 5450939ee7

gnhf 52: Folded the MarkdownFormat-to-wire-payload decision that was spelled five times across three files onto one view::send_page/view::inline_content pair, deleting the GuestAnswer vocabulary that restated ViewOp's existing Option<MarkdownFormat> convention and the second hand-written copy of markdown_v2_mode. bcfd5d1617

weiwen merged commit c623634b91 into main 2026-08-13 13:38:58 +08:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

epic

Large body of work that groups related issues or PRs into a single initiative; not intended for direct implementation until broken down into smaller tasks.

  

in-review

Agent opened a PR; tracked there — no action needed on the issue

  

ready-for-agent

PRD ready for an agent to implement

  

ready-for-human

Implemented; awaiting human review/merge

No labels

epic

in-review

ready-for-agent

ready-for-human

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

weiwen/evie!96

No description provided.