morluto/rea
1
0
Fork 0
mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00
Code Issues 1.3k Projects Packages Wiki Activity

[PR #2461] [MERGED] fix(setup): resolve DeepSeek Harness home overrides #5244

New issue
Closed
opened 2026-10-31 01:05:06 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 01:05:06 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2461
Author: @saya-ch
Created: 10/13/2026
Status: ✅ Merged
Merged: 10/13/2026
Merged by: @morluto

Base: main ← Head: fix/dsh-home-path-resolution

📝 Commits (1)

  • c266ad2 fix(setup): resolve DeepSeek Harness home overrides

📊 Changes

4 files changed (+190 additions, -11 deletions)

View changed files

📝 docs/client-configuration.md (+9 -2)
📝 src/application/SupportedClients.ts (+21 -2)
📝 tests/acceptance/setup/dshClientSetup.test.ts (+106 -1)
📝 tests/boundary/filesystem/dshClientConfiguration.test.ts (+54 -6)

📄 Description

Summary

DeepSeek Harness users who set DSH_HOME="" or DSH_HOME="~/selected harness" can have REA register its MCP server in a directory Harness never reads. The same mismatch affects skill installation through DSH_AGENTS_HOME.

Resolve both roots using Harness's home-paths semantics so setup, doctor and uninstall agree with the client. Related to the integration in #1929. No separate issue is linked: this was reproduced while checking that integration, and searches for open DSH_HOME / DSH_AGENTS_HOME reports and PRs found no matching path fix.

Problem and expected behavior

REA used the environment values directly with ?? and join. An empty override selected cordis.patch.yml or skills under the working directory; whitespace selected a literal whitespace directory; ~/... remained a literal tilde directory. Harness ignores blank overrides, expands the current user's tilde prefix, and resolves relative roots against cwd.

The source contract is Harness's root resolver. trim() determines whether a value is blank; nonblank values retain their original spaces. Both ~/ and ~\ expand, while ~someone stays a literal relative directory. The shared agents root is independent of the Harness home.

Change and scope

  • Give the two DSH roots one resolver in SupportedClients.ts; config paths, detection markers and skill destinations consume its absolute result.
  • Add a boundary input matrix and three public CLI journeys with separate temporary HOME/cwd directories: blank defaults, independent tilde roots and independent relative roots.
  • Document the root selection and same-cwd requirement for relative overrides.

This is an ordinary correction to the existing client configuration integration. The contribution-scope maintainer decision for new providers or target-execution capabilities is not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: DSH root resolution in SupportedClients.ts, before filesystem inspection or setup planning.
  • CLI and MCP/tool-catalog contract: existing commands and flags; corrected absolute configuration/skill destinations in setup plans.
  • Provider, bridge, target-format, or platform compatibility: matches the client-owned path contract on the host's native Node path implementation. Other client resolvers are untouched.
  • Evidence, artifact, provenance, or reconstruction contract: no analysis contract changes.
  • Authority and cleanup: existing approval, backup, atomic replacement and uninstall ownership behavior apply at the correctly resolved locations. No model request or target execution capability is added.
  • Generated metadata, package and installation impact: no package/version/lockfile changes; generated outputs remain ignored. DSH registration and skill paths now follow the selected roots.

Expected effects of the existing configuration workflow touched here:

  • Read existing client configuration.
  • Change client configuration and installed skill files after existing setup approval.

This change does not add target attachment, instrumentation, protection recovery or network access.

Evidence and regression coverage

  • Before the production fix, the focused DSH filesystem suite reported 8 failed / 79 passed: blank, tilde and absolute-path projection regressions failed.
  • After the fix, the DSH filesystem and CLI setup suites report 96 passed.
  • CLI journeys inspect the exact dry-run destinations, confirm no dry-run mutation, apply setup, preserve the caller patch and first backup, check doctor --client dsh --skill, repeat setup without changes, then uninstall from the same roots while retaining the caller entry.
  • Existing DSH CLI/MCP launcher verification remains in the same acceptance suite. These checks do not establish a real Harness chat session, live DeepSeek API or native analysis-provider behavior.

Validation performed

Windows x64, pinned Node 24.18.0 and npm 11.16.0:

  • npm ci — passed.
  • npm run test:focused -- tests/boundary/filesystem/dshClientConfiguration.test.ts tests/acceptance/setup/dshClientSetup.test.ts — 96 passed.
  • npm run check — passed: typecheck, lint, formatting, dependency/metadata checks, module boundaries, knip and architecture guards.
  • npm run docs:check — passed, including 2 README consistency cases.
  • npm run verify:test-discovery — passed; 1,008 files discovered exactly once.
  • npm run jscpd — passed at 2.98%, below the unchanged 3.0% threshold.
  • npm pack --dry-run --json — passed; 1,511 package entries.
  • git diff --check — passed.
  • npm run verify:package — not completed on Windows. Its unchanged repository-skill verifier calls execFile("npm", ...) and fails with spawn npm ENOENT before package verification starts. The runtime build and package dry-run above passed; they do not replace the full package verifier.

Compatibility, safety, and release

  • Breaking changes or migration: no API change. Blank/tilde overrides now point at the same directories Harness uses; a registration previously written to a literal wrong directory is not migrated or removed automatically.
  • Real OS coverage: Windows x64 public REA CLI and SDK MCP transport. POSIX behavior is covered by host-neutral source cases for CI; a local POSIX run was not performed.
  • Real Harness, live DeepSeek API and Hopper/Ghidra coverage: not run for this path-only change.
  • Publication: this PR adds no release or publication action.

Before merge

  • This PR addresses a concrete configuration problem.
  • Scope and authority remain within the existing client integration.
  • The title follows fix(setup): ... and the diff has one focused outcome.
  • Related integration is linked and the absence of a separate issue is explained.
  • Tests cover observable behavior, preserved caller data and repeated setup/uninstall.
  • Owning documentation is updated.
  • CLI behavior and verification limits are recorded.
  • The final diff was checked for secrets, generated outputs, unrelated changes 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/2461 **Author:** [@saya-ch](https://github.com/saya-ch) **Created:** 10/13/2026 **Status:** ✅ Merged **Merged:** 10/13/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/dsh-home-path-resolution` --- ### 📝 Commits (1) - [`c266ad2`](https://github.com/morluto/rea/commit/c266ad2340ec09e4dc3fb212a6b5495229e8a028) fix(setup): resolve DeepSeek Harness home overrides ### 📊 Changes **4 files changed** (+190 additions, -11 deletions) <details> <summary>View changed files</summary> 📝 `docs/client-configuration.md` (+9 -2) 📝 `src/application/SupportedClients.ts` (+21 -2) 📝 `tests/acceptance/setup/dshClientSetup.test.ts` (+106 -1) 📝 `tests/boundary/filesystem/dshClientConfiguration.test.ts` (+54 -6) </details> ### 📄 Description ## Summary DeepSeek Harness users who set `DSH_HOME=""` or `DSH_HOME="~/selected harness"` can have REA register its MCP server in a directory Harness never reads. The same mismatch affects skill installation through `DSH_AGENTS_HOME`. Resolve both roots using Harness's home-paths semantics so setup, doctor and uninstall agree with the client. Related to the integration in #1929. No separate issue is linked: this was reproduced while checking that integration, and searches for open `DSH_HOME` / `DSH_AGENTS_HOME` reports and PRs found no matching path fix. ## Problem and expected behavior REA used the environment values directly with `??` and `join`. An empty override selected `cordis.patch.yml` or `skills` under the working directory; whitespace selected a literal whitespace directory; `~/...` remained a literal tilde directory. Harness ignores blank overrides, expands the current user's tilde prefix, and resolves relative roots against cwd. The source contract is [Harness's root resolver](https://github.com/deepseek-ai/deepseek-harness/blob/d743267388641bc76f17c45ce8b4c231aed1d32c/packages/util/home-paths/src/index.ts#L101). `trim()` determines whether a value is blank; nonblank values retain their original spaces. Both `~/` and `~\` expand, while `~someone` stays a literal relative directory. The shared agents root is independent of the Harness home. ## Change and scope - Give the two DSH roots one resolver in `SupportedClients.ts`; config paths, detection markers and skill destinations consume its absolute result. - Add a boundary input matrix and three public CLI journeys with separate temporary HOME/cwd directories: blank defaults, independent tilde roots and independent relative roots. - Document the root selection and same-cwd requirement for relative overrides. This is an ordinary correction to the existing client configuration integration. The contribution-scope maintainer decision for new providers or target-execution capabilities is not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: DSH root resolution in `SupportedClients.ts`, before filesystem inspection or setup planning. - CLI and MCP/tool-catalog contract: existing commands and flags; corrected absolute configuration/skill destinations in setup plans. - Provider, bridge, target-format, or platform compatibility: matches the client-owned path contract on the host's native Node path implementation. Other client resolvers are untouched. - Evidence, artifact, provenance, or reconstruction contract: no analysis contract changes. - Authority and cleanup: existing approval, backup, atomic replacement and uninstall ownership behavior apply at the correctly resolved locations. No model request or target execution capability is added. - Generated metadata, package and installation impact: no package/version/lockfile changes; generated outputs remain ignored. DSH registration and skill paths now follow the selected roots. Expected effects of the existing configuration workflow touched here: - [x] Read existing client configuration. - [x] Change client configuration and installed skill files after existing setup approval. This change does not add target attachment, instrumentation, protection recovery or network access. ## Evidence and regression coverage - Before the production fix, the focused DSH filesystem suite reported **8 failed / 79 passed**: blank, tilde and absolute-path projection regressions failed. - After the fix, the DSH filesystem and CLI setup suites report **96 passed**. - CLI journeys inspect the exact dry-run destinations, confirm no dry-run mutation, apply setup, preserve the caller patch and first backup, check `doctor --client dsh --skill`, repeat setup without changes, then uninstall from the same roots while retaining the caller entry. - Existing DSH CLI/MCP launcher verification remains in the same acceptance suite. These checks do not establish a real Harness chat session, live DeepSeek API or native analysis-provider behavior. ## Validation performed Windows x64, pinned Node **24.18.0** and npm **11.16.0**: - `npm ci` — passed. - `npm run test:focused -- tests/boundary/filesystem/dshClientConfiguration.test.ts tests/acceptance/setup/dshClientSetup.test.ts` — **96 passed**. - `npm run check` — passed: typecheck, lint, formatting, dependency/metadata checks, module boundaries, knip and architecture guards. - `npm run docs:check` — passed, including 2 README consistency cases. - `npm run verify:test-discovery` — passed; 1,008 files discovered exactly once. - `npm run jscpd` — passed at 2.98%, below the unchanged 3.0% threshold. - `npm pack --dry-run --json` — passed; 1,511 package entries. - `git diff --check` — passed. - `npm run verify:package` — **not completed** on Windows. Its unchanged repository-skill verifier calls `execFile("npm", ...)` and fails with `spawn npm ENOENT` before package verification starts. The runtime build and package dry-run above passed; they do not replace the full package verifier. ## Compatibility, safety, and release - Breaking changes or migration: no API change. Blank/tilde overrides now point at the same directories Harness uses; a registration previously written to a literal wrong directory is not migrated or removed automatically. - Real OS coverage: Windows x64 public REA CLI and SDK MCP transport. POSIX behavior is covered by host-neutral source cases for CI; a local POSIX run was not performed. - Real Harness, live DeepSeek API and Hopper/Ghidra coverage: not run for this path-only change. - Publication: this PR adds no release or publication action. ## Before merge - [x] This PR addresses a concrete configuration problem. - [x] Scope and authority remain within the existing client integration. - [x] The title follows `fix(setup): ...` and the diff has one focused outcome. - [x] Related integration is linked and the absence of a separate issue is explained. - [x] Tests cover observable behavior, preserved caller data and repeated setup/uninstall. - [x] Owning documentation is updated. - [x] CLI behavior and verification limits are recorded. - [x] The final diff was checked for secrets, generated outputs, unrelated changes and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:05:06 +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
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#5244
No description provided.