[PR #7334] fix(cli): state each option default once in help output #7819

New issue

Open

opened 2026-11-05 01:47:54 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-11-05 01:47:54 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7334
Author: @akushonkamen
Created: 10/26/2026
Status: 🔄 Open

Base: main ← Head: fix/7306-duplicate-help-defaults

---

📝 Commits (3)

• f600732 fix(cli): state each option default once in help output
• 68f9017 style(cli): apply oxfmt to captureCommands
• 645f693 chore: retrigger ci after main recovery

📊 Changes

4 files changed (+67 additions, -6 deletions)

View changed files

📝 src/cli/binaryDiagnosticsCommands.ts (+6 -6)
📝 src/cli/captureCommands.ts (+9 -0)
📝 src/cli/signalCommands.ts (+6 -0)
➕ tests/boundary/cli/helpDefaultAnnotation.test.ts (+46 -0)

📄 Description

Summary

Six CLI commands printed an option default twice in --help output: once as prose inside the option description and once as the automatic (default: …) annotation the help renderer appends when the option has a schema default. This removes the redundant prose from the CLI-layer option descriptions so each default is stated exactly once, and adds a boundary test covering all six commands.

Fixes #7306

Problem and expected behavior

Smallest trigger: node scripts/rea.mjs inspect-byte-entropy --help prints --block-size <number> Power-of-two block size from 256 to 65536 bytes (default 4096) (default: 4096). The violated invariant is that an option's help presents its default once. Both annotations carried the same value in the same units, so the defect was purely presentational redundancy across 11 entries in six commands: inspect-byte-entropy (--block-size, --offset), inspect-devicetree (four --max-* options), decode-signal-recording (--line_offset), inspect-packet-capture (--match_offset), inspect-packet-fields (--kind, --offset), and inspect-signal-decoders (--offset).

Change and scope

The redundant text lived in two layers:

• src/cli/binaryDiagnosticsCommands.ts — the CLI-layer .describe() overrides themselves appended (default N); those clauses are dropped.
• src/cli/captureCommands.ts and src/cli/signalCommands.ts — the commands spread shared domain-schema shapes, whose descriptions say "default 0" / "defaults to protocols". Following the existing pattern in those files (the CLI-layer limit overrides), the affected fields are re-described at the CLI wiring layer with the default mention removed.

The domain schemas and the MCP tool contracts are intentionally unchanged, so machine-readable schema defaults and advertised tool descriptions are untouched. No help content beyond the duplicated default wording is altered.

Contribution scope: not applicable; ordinary presentation fix within the existing CLI surface.

Contract and boundary impact

• Semantic owner and earliest changed stage: CLI help presentation (transport/projection layer); consumers are human CLI readers only.
• Contribution scope fit and linked maintainer decision: not applicable.
• CLI and MCP/tool-catalog contract: CLI help text only; MCP tool descriptions, input schemas and defaults unchanged. Generated catalogs are unaffected (verified: no artifact/catalog files changed).
• Provider, bridge, target-format, or platform compatibility: none.
• Evidence, artifact, provenance, or reconstruction contract: not applicable.
• Target selection, authority, upstream behavior, and cleanup details: not applicable.
• Generated metadata: none; no build outputs committed.

Expected effects: documentation or usability only; no target interaction.

• Documentation or usability only; no target interaction.

Evidence and regression coverage

• Tests added or updated: tests/boundary/cli/helpDefaultAnnotation.test.ts runs --help for the six affected commands and asserts that no help line restates the automatic (default: …) annotation's value in its description (matching (default X), default X, or defaults to X prose before the automatic annotation).
• Base reproduction or other evidence: on base revision 077de9259 the new test fails with exactly the reported lines, e.g. --block-size <number> Power-of-two block size from 256 to 65536 bytes (default 4096) (default: 4096) and --offset <number> Window start as a decimal file byte offset (default 0) (default: 0); after the fix it passes.
• User-visible CLI/MCP output: inspect-byte-entropy --help now shows --block-size <number> Power-of-two block size from 256 to 65536 bytes (default: 4096); the same single-annotation presentation applies to the other ten entries.
• Remaining proof gaps: the test enumerates the six commands from the issue, not a complete catalog audit; other commands could carry similar wording but none were reported.

Boundary regressions: not applicable (no boundary or lifecycle behavior changed).

Validation performed

• npx vitest run tests/boundary/cli/helpDefaultAnnotation.test.ts — red on base (failed with the two byte-entropy duplicate lines and the equivalent duplicates in the other five commands), green after the fix.
• npx vitest run tests/boundary/cli/ — 1198 passed; 33 failures in 11 files are pre-existing environment issues on this machine (local Node is 24.21.0 while supported_runtime requires ^24.22.1, and IDA/Hopper/provider probes are absent); none touch the six affected commands or help rendering.
• node scripts/rea.mjs <command> --help for the six commands against a local build — all exit 0 with each default shown once.

Compatibility, safety, and release

• Breaking changes or migration steps: none; help text only.
• Real Hopper/Ghidra, browser, or OS coverage: not applicable.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: not applicable; no target interaction.

Author readiness

Human owner: @akushonkamen

• I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
• I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
• I declare this PR ready for initial maintainer review.

Before merge

• This PR addresses a concrete problem or an agreed enhancement.
• Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
• The PR has one focused outcome and the title follows type(scope): outcome.
• Related issue is linked, or the reason for not linking one is stated above.
• Tests cover changed observable behavior and meaningful failure paths.
• Owning docs, contracts, and generated metadata are updated where needed.
• User-visible CLI/MCP changes include representative output.
• I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

---

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/7334 **Author:** [@akushonkamen](https://github.com/akushonkamen) **Created:** 10/26/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/7306-duplicate-help-defaults` --- ### 📝 Commits (3) - [`f600732`](https://github.com/morluto/rea/commit/f6007329d13723184b7662b8e582591181b15463) fix(cli): state each option default once in help output - [`68f9017`](https://github.com/morluto/rea/commit/68f9017786fff43db014e2c999e34ce007c2b2ca) style(cli): apply oxfmt to captureCommands - [`645f693`](https://github.com/morluto/rea/commit/645f693e422b1dcaf0f6ebd69cf566af446e87f5) chore: retrigger ci after main recovery ### 📊 Changes **4 files changed** (+67 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `src/cli/binaryDiagnosticsCommands.ts` (+6 -6) 📝 `src/cli/captureCommands.ts` (+9 -0) 📝 `src/cli/signalCommands.ts` (+6 -0) ➕ `tests/boundary/cli/helpDefaultAnnotation.test.ts` (+46 -0) </details> ### 📄 Description ## Summary Six CLI commands printed an option default twice in `--help` output: once as prose inside the option description and once as the automatic `(default: …)` annotation the help renderer appends when the option has a schema default. This removes the redundant prose from the CLI-layer option descriptions so each default is stated exactly once, and adds a boundary test covering all six commands. Fixes #7306 ## Problem and expected behavior Smallest trigger: `node scripts/rea.mjs inspect-byte-entropy --help` prints `--block-size <number> Power-of-two block size from 256 to 65536 bytes (default 4096) (default: 4096)`. The violated invariant is that an option's help presents its default once. Both annotations carried the same value in the same units, so the defect was purely presentational redundancy across 11 entries in six commands: `inspect-byte-entropy` (`--block-size`, `--offset`), `inspect-devicetree` (four `--max-*` options), `decode-signal-recording` (`--line_offset`), `inspect-packet-capture` (`--match_offset`), `inspect-packet-fields` (`--kind`, `--offset`), and `inspect-signal-decoders` (`--offset`). ## Change and scope The redundant text lived in two layers: - `src/cli/binaryDiagnosticsCommands.ts` — the CLI-layer `.describe()` overrides themselves appended `(default N)`; those clauses are dropped. - `src/cli/captureCommands.ts` and `src/cli/signalCommands.ts` — the commands spread shared domain-schema shapes, whose descriptions say "default 0" / "defaults to protocols". Following the existing pattern in those files (the CLI-layer `limit` overrides), the affected fields are re-described at the CLI wiring layer with the default mention removed. The domain schemas and the MCP tool contracts are intentionally unchanged, so machine-readable schema defaults and advertised tool descriptions are untouched. No help content beyond the duplicated default wording is altered. Contribution scope: not applicable; ordinary presentation fix within the existing CLI surface. ## Contract and boundary impact - Semantic owner and earliest changed stage: CLI help presentation (transport/projection layer); consumers are human CLI readers only. - Contribution scope fit and linked maintainer decision: not applicable. - CLI and MCP/tool-catalog contract: CLI help text only; MCP tool descriptions, input schemas and defaults unchanged. Generated catalogs are unaffected (verified: no artifact/catalog files changed). - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: not applicable. - Target selection, authority, upstream behavior, and cleanup details: not applicable. - Generated metadata: none; no build outputs committed. Expected effects: documentation or usability only; no target interaction. - [x] Documentation or usability only; no target interaction. ## Evidence and regression coverage - Tests added or updated: `tests/boundary/cli/helpDefaultAnnotation.test.ts` runs `--help` for the six affected commands and asserts that no help line restates the automatic `(default: …)` annotation's value in its description (matching `(default X)`, `default X`, or `defaults to X` prose before the automatic annotation). - Base reproduction or other evidence: on base revision `077de9259` the new test fails with exactly the reported lines, e.g. `--block-size <number> Power-of-two block size from 256 to 65536 bytes (default 4096) (default: 4096)` and `--offset <number> Window start as a decimal file byte offset (default 0) (default: 0)`; after the fix it passes. - User-visible CLI/MCP output: `inspect-byte-entropy --help` now shows `--block-size <number> Power-of-two block size from 256 to 65536 bytes (default: 4096)`; the same single-annotation presentation applies to the other ten entries. - Remaining proof gaps: the test enumerates the six commands from the issue, not a complete catalog audit; other commands could carry similar wording but none were reported. Boundary regressions: not applicable (no boundary or lifecycle behavior changed). ## Validation performed - `npx vitest run tests/boundary/cli/helpDefaultAnnotation.test.ts` — red on base (failed with the two byte-entropy duplicate lines and the equivalent duplicates in the other five commands), green after the fix. - `npx vitest run tests/boundary/cli/` — 1198 passed; 33 failures in 11 files are pre-existing environment issues on this machine (local Node is 24.21.0 while `supported_runtime` requires `^24.22.1`, and IDA/Hopper/provider probes are absent); none touch the six affected commands or help rendering. - `node scripts/rea.mjs <command> --help` for the six commands against a local build — all exit 0 with each default shown once. ## Compatibility, safety, and release - Breaking changes or migration steps: none; help text only. - Real Hopper/Ghidra, browser, or OS coverage: not applicable. - Package or release metadata impact: none. - Security, privacy, process, or containment review: not applicable; no target interaction. ## Author readiness Human owner: @akushonkamen - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi added the

pull-request

label 2026-11-05 01:47:54 +00:00

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

codex/procedure-reference-stacked

release-please--branches--main--components--rea-agents

release-please--branches--main--components--rea-agents--release-notes

codex/kuna-independent-retry

codex/byte-search-overlay-coverage

codex/open-failure-target-receipt

codex/kuna-xref-evidence

codex/ghidra-ambiguous-procedure-recovery

codex/function-source-bundle

codex/trace-function-integration-prototype

codex/snapshot-source-closure

codex/recorded-evidence-array-pages

codex/evidence-recovery-redesign

codex/trace-feature-address-scope

codex/call-discovery-scope

codex/ghidra-literal-candidate-evidence

codex/decompile-directory-independent-retry

codex/retry-provenance-base

codex/value-flow-capability-experiment

codex/ghidra-containing-instruction

cursor/readme-discord-button-ef9f

dependabot/github_actions/actions/setup-node-7.1.0

dependabot/github_actions/actions/upload-artifact-7.0.2

dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df

codex/kuna-1989

fix/8559-native-ui-fixture-ownership

fix/8555-go-verifier-mcp-ownership

codex/provider-capability-recovery

fix/8642-rizin-target-stdin

codex/ghidra-memory-effect-scope

codex/ghidra-annotation-entry-selector

codex/ghidra-readonly-recovery

codex/ghidra-regex-verifier-recovery

codex/evidence-discovery-view-guidance

fix/8545-bulk-append-overflow

fix/8428-navigation-refusal-alternatives

codex/address-context-recovery

codex/matching-member-limitations

codex/unknown-scope-contract

codex/evidence-view-guidance

feat/8373-native-trace-views

codex/ghidra-snapshot-verifier-binding

codex/elf-export-visibility

codex/evidence-view-recovery

codex/native-reference-cli-help

codex/provider-candidate-observation-scope

codex/kuna-session-verification

codex/ghidra-switch-lifetime-guidance

codex/pseudocode-paging-discovery

codex/clarify-evidence-view-support

codex/kuna-xrefs-selector-recovery

codex/context-capacity-recovery

codex/evidence-closure-large-links

codex/same-function-evidence-identity

codex/ghidra-verifier-inspected-jdk

codex/audit-guided-workflows

codex/crash-prompt-retained-dossiers

codex/analysis-view-error-recovery

codex/kuna-verifier-target-selection

codex/ghidra-selected-project-call-coverage

codex/docs-native-analysis-scope

codex/ghidra-java-socket-boundary

codex/ghidra-retained-snapshot-verifier

codex/ghidra-search-inventory-facts

fix/8284-zero-argument-parameter-bindings

fix/8198-ui-action-handler-offset

fix/8257-elf-entry-label-identity

fix/8304-deferred-output-schema-projection

fix/8277-call-path-computed-target-uncertainty

fix/pr-8089-conflicts

fix/ci-static-duplicate-export

dependabot/npm_and_yarn/lint-staged-17.6.0

dependabot/github_actions/actions/download-artifact-8.0.2

dependabot/npm_and_yarn/write-file-atomic-8.0.0

dependabot/npm_and_yarn/canonicalize-5.1.0

dependabot/github_actions/actions/cache/restore-6.1.0

dependabot/npm_and_yarn/toon-format/toon-4.4.0

dependabot/github_actions/actions/deploy-pages-5.0.1

codex/review-fixes-pr-2403

codex/review-fixes-pr-2400

codex/process-terminal-width

codex/test-brittleness-cleanup

verify/7167-browser-connect-macos

fix/7167-browser-connect

feat/native-matching-allowance-setting

feat/browser-scenario-dry-run

test/managed-caller-parameters-20261024

codex/parser-fortythird-boundaries

fix/6926-pinvoke-platform-decorations-20261023

fix/6889-har-body-encoding-20261023

fix/6888-sqlite-schema-budget-20261023

fix/dependency-security-gates-6708

cursor/evidence-overwrite-rebase-b4ac

feat/4057-verify-native-exports

fix/windows-acl-observer-overhead-20261022

cursor/erlang-beam-restack-4476

cursor/pe-certificate-review-bf32

fix/6116-javascript-application-fs-errors

fix/6061-unmapped-runtime-script-unknown

feat/browser-scenario-summary

fix/pe-certificates

codex/verify-3407

cursor/rebase-5699

cursor/rebase-5352

cursor/rebase-5600

cursor/fix-cli-schema-omission-10a8

codex/audit-hopper-shutdown-reasons-20261021

fix/demangle-swift-omitted-record

fix/nib-boolean-value-types

cursor/cancellation-partial-observation-a5ac

fix/ib-object-limit-reasons

fix/electron-fuse-limit-advice

fix/kuna-doctor-dangling-cache

fix/fixed-budget-refusal-advice

fix/js-ipc-listener-dedup

fix/js-return-member-provenance

fix/dmg-integrity-retry-advice

fix/ida-doctor-readiness

fix/kuna-version-probe-output-drain

fix/legacy-swift-runtime-name-matching

fix/dylib-lazy-load-commands

fix/browser-scenario-startup-cancel

fix/swift-nested-punycode-classification

fix/compare-unselected-scopes

fix/objc-method-budget-coverage

fix/dmg-mounted-root-observations

audit/ci-tests-20261019-round2

release/6.7.0

fix/wabt-cleanup-retry-resolution

fix/electron-fuse-elf-pe-architecture

fix/native-plist-descriptor-ownership

fix/kuna-caller-cleanup-ownership

experiment/atomic-codemode-20261016

review/first-contributor-3776

fix/call-resolution-full-read-cycles

fix/member-mutation-selection-repeat

experiment/atomic-re-tools-20261015

perf/member-mutation-lazy-origins

perf/static-network-mutation-index

fix/hopper-startup-lifecycle

audit/3050-windows-proof-20261015

feat/windows-window-capture-2183

audit/3049-windows-proof-20261015

audit/3735-macos-fixtures-20261015

fix/batch-decompile-null-pseudocode

fix/kuna-inventory-honors-jobs

experiment/browser-codemode-tool-design-20261015

fix/hopper-clean-runtime-argv

codex/review-2049-27f1b367

review-fixes/pr-2787-routing

fix/3360-scoped-this-emitters

fix/3367-replaced-global-effects

fix/3838-compact-any-value-items

test/hopper-download-probe-20261015

codex/windows-runtime-creation-red-green-20261015

codex/windows-readonly-root-red-green-20261015

codex/windows-root-share-red-green-20261015

codex/exp-1685-win-mcp-startup

codex/bug-sweep-20261015

investigate/2190-windows-package-phases

investigate/3543-macos-cli-deadline

perf/3281-reverse-tools-feedback-quality

fix/3406-hopper-doctor-fixture

fix/3341-wrapper-require-test-context

fix/3301-owned-uninstall-fixtures

fix/3164-compiler-input-ownership

fix/pcap-cleanup-stdout-newline-20261014

perf/interface-builder-summary

codex/review-fixes-pr-1977

fix/ghidra-effective-jvm-platform

fix/docs-turkish-rust-link-20261013

fix/main-maintenance-ci-20261010

fix/recover-binary-session-process-effects

codex/review-fixes-pr-2457

codex/ci-required-cancellation-gate

fix/main-format-baseline-20261013

fix/setup-preserve-entry-fields

cursor/restore-main-checks-1ffc

fix/ghidra-bridge-hashmap-import

codex/shared-ci-jadx-json-default-20261013

codex/shared-ci-ghidra-test-groups-20261013

codex/shared-ci-java-fixture-format-20261013

codex/fix-intrinsic-invocation-boundaries

test/release-preflight-reusable-jobs

test/js-parameter-provenance-expectation

fix/linux-hopper-verification-current

test/2419-ghidra-elf-probe-size

followup/pr-1544-native-ida

codex/fold-pr-2230-contribution

docs/readme-responsible-use

fix/issue-2064

fix/issue-2050

fix/issue-2053

fix/issue-1968

fix/issue-1945

experiment/codemode-bridge-20261011

fix/tool-effects-negative-wording-1904-20261012

fix/1842-electron-interop-provenance

feat/recover-javascript-multi-input

refactor/website-i18n-prep

fix/nativeaot-pe-virtual-extent

fix/browser-verifier-ci-hang

fix/pe-resources-input-selection

docs/beginner-friendly-guides

docs/beginner-setup-guide

fix/javascript-analysis-worker-1563

fix/1649-ghidra-duplicate-names

fix/javascript-export-keys-integration-1369

test/maintenance-boundary-contracts-20261011

review/javascript-export-keys-1369

review/process-live-progress-1483

test/javascript-1495-growth-ratio

fix/ci-escape-timing

docs/normalized-terminal-geometry-1450

release/6.3.0

archive/release-6.3.0-pr1381

release/6.2.0

fix/electron-preload-dynamic-override

fix/javascript-self-referential-bundler-edges

release/6.1.0

cursor/grok-client-cherry-pick-0b56

feat/signature-posture

feat/dyld-shared-cache

feat/artifact-integrity-policy

feat/pkg-inventory

release/6.0.0

chore/sync-release-5.0.0

release/5.0.0

cursor/cloud-agent-node-787e

fix/javascript-xhr-open-endpoints

review/pr-711-realpath-fallback-wording

cleanup/replay-confinement

codex/test-suite-performance

codex/issue-foundations

codex/address-open-issues-2026-07-20

agent/javascript-vite-rollup-esbuild-adapters

agent/process-cleanup

agent/triage-integration

agent/unknown-commands-registry

feat/mcp-identity-metadata

morlvps/issue_cleanup

codex/installer-redesign

morl/roadmap-investigation-core

morl/roadmap-investigation-docs

release-please--branches--main--components--rea

rea-agents-6.8.0

rea-agents-6.7.0

rea-agents-6.6.0

experiment/atomic-codemode-wait-runtime-20261016

rea-agents-6.5.0

rea-agents-6.4.0

rea-agents-6.3.0

rea-agents-6.2.0

rea-agents-6.1.0

rea-agents-6.0.0

rea-agents-5.0.0

rea-agents-4.1.0

rea-agents-4.0.1

rea-agents-4.0.0

rea-agents-3.2.1

rea-agents-3.2.0

rea-agents-3.1.0

rea-agents-3.0.0

rea-agents-2.7.0

rea-agents-2.6.0

rea-agents-2.5.1

rea-agents-2.5.0

rea-agents-2.4.0

rea-agents-2.3.0

rea-agents-2.2.0

rea-agents-2.1.0

rea-agents-2.0.0

rea-agents-1.7.0

rea-agents-1.6.0

rea-agents-1.5.0

rea-agents-1.4.0

rea-agents-1.3.0

rea-agents-1.2.0

rea-agents-1.1.0

rea-agents-1.0.0

rea-agents-0.5.0

rea-agents-0.4.0

rea-agents-0.3.0

rea-0.2.1

rea-0.2.0

Labels

Clear labels   

area: bridge

  

area: bridge

  

area: build

  

area: build

  

area: build

  

area: cli

  

area: domain

  

area: evidence

  

area: mcp

  

area: native

  

area: providers

  

area: runtime

  

area: server

  

area: setup

  

area: tests

  

bug

  

design

  

documentation

  

enhancement

  

enhancement

  

enhancement

  

experiment

  

help wanted

  

i18n

  

invalid

  

P0: critical

  

P1: high

  

P2: medium

  

P2: medium

  

P2: medium

  

P3: low

  

performance

  

provider-request

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

roadmap

  

triage

No labels

area: bridge

area: bridge

area: build

area: build

area: build

area: cli

area: domain

area: evidence

area: mcp

area: native

area: providers

area: runtime

area: server

area: setup

area: tests

bug

design

documentation

enhancement

enhancement

enhancement

experiment

help wanted

i18n

invalid

P0: critical

P1: high

P2: medium

P2: medium

P2: medium

P3: low

performance

provider-request

pull-request

question

roadmap

triage

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

morluto/rea#7819

No description provided.