[GH-ISSUE #267] Add approval-gated managed-runtime characterization #156

New issue

Closed

opened 2026-10-15 18:21:45 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-10-15 18:21:45 +00:00

Owner

Copy link

Originally created by @morluto on GitHub (Jul 16, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/267

Problem

Static JavaScript analysis cannot prove runtime module ownership, dynamically selected branches, closure behavior, computed imports, native bridges, or effect ordering. General process capture observes the outside of a process but cannot selectively characterize an internal managed-runtime boundary.

Agents currently compensate by patching formatted bundles to export internal functions, writing temporary harnesses, or attaching ad hoc Node Inspector scripts. Those approaches can lose artifact identity, execute more code than intended, omit cleanup proof, and produce results outside the evidence model.

Outcome

Add an approval-gated, provider-neutral managed-runtime characterization capability. The first provider should support Node.js and JavaScript bundles while keeping the public contract suitable for other managed runtimes.

The capability must bind every observation to an exact artifact digest, an explicit runtime and analysis profile, a finite characterization plan, and an owned contained environment.

Capability model

Support separate operations for:

• inspect managed-runtime/package metadata without executing the target;
• prepare a hash-bound characterization workspace;
• expose selected internal functions or modules through reversible instrumentation;
• invoke explicitly selected pure or bounded-effect callables with serialized fixtures;
• observe module loading and export shape;
• observe declared environment, filesystem, child-process, native-addon, WebAssembly, HTTP, WebSocket, Electron IPC, and timer boundaries;
• attach through Node Inspector to an owned provider-launched process;
• compare static semantic claims with controlled runtime observations;
• export the resulting characterization as Evidence v2 and a reusable fixture.

Preparation and execution must be separate approval and policy decisions.

Exact-artifact instrumentation

When temporary instrumentation is required:

• verify the source artifact digest before modification;
• never modify the authoritative artifact in place;
• copy into an owned temporary root;
• apply a deterministic, reviewable transformation;
• record original and instrumented digests plus exact inserted byte/AST locations;
• preserve a transformation manifest and source map when feasible;
• expose only explicitly named/hash-addressed targets;
• reject ambiguous matches;
• prove the authoritative artifact remained unchanged;
• remove the instrumented workspace on every exit unless separately approved for export.

Instrumented execution is controlled-replay authority, not shipped-artifact authority. Results must cite both the shipped source evidence and transformation evidence.

Invocation contract

A characterization plan declares:

• artifact, runtime, entrypoint, working directory, and isolated HOME;
• selected module/function identity from semantic bundle evidence;
• serialized arguments and expected serialization bounds;
• allowed globals, modules, environment keys, roots, loopback endpoints, timers, and native boundaries;
• maximum calls, processes, files, bytes, handles, duration, and idle time;
• deterministic clock/randomness/ID policy;
• secret aliases and redaction;
• expected effect class: pure, declared bounded effects, or observation-only;
• cancellation and cleanup requirements.

Unknown return values, thrown values, callbacks, promises, iterators, cyclic objects, functions, handles, and native objects require typed bounded projections. They must not be serialized through unsafe generic inspection.

Isolation and safety

• Require explicit approval and a matching scoped policy grant.
• Launch only provider-owned processes.
• Default to no external network and loopback-only replay.
• Never attach to unrelated or pre-existing processes.
• Do not inherit arbitrary environment variables or credentials.
• Block undeclared module, filesystem, child-process, native, and network boundaries.
• Bound stdout, stderr, inspector messages, object graphs, source text, protocol bodies, and evidence.
• Propagate cancellation and prove descendant, socket, timer, inspector, temporary-root, and instrumentation cleanup.
• Clearly state that this is controlled observation, not a security sandbox, unless a real isolation provider supplies that property.

Evidence

Return:

• shipped and instrumented artifact identities;
• runtime/provider/version/profile identities;
• transformation manifest and limitations;
• selected callable identity and resolution proof;
• ordered inputs, outputs, throws, effects, and boundary events;
• process/environment/isolation identity;
• completeness, truncation, cancellation, and cleanup;
• static-to-runtime correlations labeled observation, derivation, or hypothesis;
• residual unknowns and recommended next probes.

A successful call proves only the declared finite characterization claims, never global behavioral equivalence.

Failure model

Distinguish artifact mismatch, target ambiguity, transformation failure, runtime unavailable, policy denial, unsupported value, undeclared effect, boundary escape attempt, inspector disconnect, timeout, cancellation, truncation, target crash, descendant leak, cleanup failure, and incomplete observation.

Acceptance criteria

• Provider-neutral contracts are independent of Node Inspector and any specific transformer.
• A Node provider characterizes selected functions from plain, minified, and bundled fixtures.
• Every run is bound to exact shipped and instrumented digests.
• The authoritative artifact is never modified in place and is rehashed after execution.
• Pure fixtures prove arguments, returns, throws, promises, and deterministic clock/randomness.
• Bounded-effect fixtures prove module loads, files, children, loopback HTTP/WebSocket, native/Wasm boundary declarations, and cleanup.
• Undeclared effects fail closed and remain visible.
• Inspector attach is limited to an owned provider-launched process.
• Cancellation and all resource-cleanup paths are exercised.
• Static semantic evidence can be correlated without being promoted to runtime proof.
• Large records are available through MCP resources.
• CLI and MCP contracts, typed errors, progress, cancellation, and Tasks behavior are equivalent.
• A temporary export-instrumentation fixture produces deterministic evidence twice and leaves the source tree byte-identical with no residual instrumented file.

Relationships

• Parent dynamic-observation policy: #36
• Static JavaScript semantics: #117 and #68
• Managed-runtime provider roadmap: #42
• Provider SDK: #45
• Evidence resources: #99
• Scoped approval grants: #96 and #114
• Long-running work: #97 and #98
• Fixture export: #62

Non-goals

• Executing arbitrary bundles without approval.
• Claiming instrumentation output is unmodified shipped behavior.
• Attaching to unrelated user processes.
• Providing a security boundary without a real sandbox or VM.
• Recovering original names, comments, or source.
• Replacing external process, browser, Electron, or native-binary observation.

Originally created by @morluto on GitHub (Jul 16, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/267 ## Problem Static JavaScript analysis cannot prove runtime module ownership, dynamically selected branches, closure behavior, computed imports, native bridges, or effect ordering. General process capture observes the outside of a process but cannot selectively characterize an internal managed-runtime boundary. Agents currently compensate by patching formatted bundles to export internal functions, writing temporary harnesses, or attaching ad hoc Node Inspector scripts. Those approaches can lose artifact identity, execute more code than intended, omit cleanup proof, and produce results outside the evidence model. ## Outcome Add an approval-gated, provider-neutral managed-runtime characterization capability. The first provider should support Node.js and JavaScript bundles while keeping the public contract suitable for other managed runtimes. The capability must bind every observation to an exact artifact digest, an explicit runtime and analysis profile, a finite characterization plan, and an owned contained environment. ## Capability model Support separate operations for: - inspect managed-runtime/package metadata without executing the target; - prepare a hash-bound characterization workspace; - expose selected internal functions or modules through reversible instrumentation; - invoke explicitly selected pure or bounded-effect callables with serialized fixtures; - observe module loading and export shape; - observe declared environment, filesystem, child-process, native-addon, WebAssembly, HTTP, WebSocket, Electron IPC, and timer boundaries; - attach through Node Inspector to an owned provider-launched process; - compare static semantic claims with controlled runtime observations; - export the resulting characterization as Evidence v2 and a reusable fixture. Preparation and execution must be separate approval and policy decisions. ## Exact-artifact instrumentation When temporary instrumentation is required: - verify the source artifact digest before modification; - never modify the authoritative artifact in place; - copy into an owned temporary root; - apply a deterministic, reviewable transformation; - record original and instrumented digests plus exact inserted byte/AST locations; - preserve a transformation manifest and source map when feasible; - expose only explicitly named/hash-addressed targets; - reject ambiguous matches; - prove the authoritative artifact remained unchanged; - remove the instrumented workspace on every exit unless separately approved for export. Instrumented execution is controlled-replay authority, not shipped-artifact authority. Results must cite both the shipped source evidence and transformation evidence. ## Invocation contract A characterization plan declares: - artifact, runtime, entrypoint, working directory, and isolated HOME; - selected module/function identity from semantic bundle evidence; - serialized arguments and expected serialization bounds; - allowed globals, modules, environment keys, roots, loopback endpoints, timers, and native boundaries; - maximum calls, processes, files, bytes, handles, duration, and idle time; - deterministic clock/randomness/ID policy; - secret aliases and redaction; - expected effect class: pure, declared bounded effects, or observation-only; - cancellation and cleanup requirements. Unknown return values, thrown values, callbacks, promises, iterators, cyclic objects, functions, handles, and native objects require typed bounded projections. They must not be serialized through unsafe generic inspection. ## Isolation and safety - Require explicit approval and a matching scoped policy grant. - Launch only provider-owned processes. - Default to no external network and loopback-only replay. - Never attach to unrelated or pre-existing processes. - Do not inherit arbitrary environment variables or credentials. - Block undeclared module, filesystem, child-process, native, and network boundaries. - Bound stdout, stderr, inspector messages, object graphs, source text, protocol bodies, and evidence. - Propagate cancellation and prove descendant, socket, timer, inspector, temporary-root, and instrumentation cleanup. - Clearly state that this is controlled observation, not a security sandbox, unless a real isolation provider supplies that property. ## Evidence Return: - shipped and instrumented artifact identities; - runtime/provider/version/profile identities; - transformation manifest and limitations; - selected callable identity and resolution proof; - ordered inputs, outputs, throws, effects, and boundary events; - process/environment/isolation identity; - completeness, truncation, cancellation, and cleanup; - static-to-runtime correlations labeled observation, derivation, or hypothesis; - residual unknowns and recommended next probes. A successful call proves only the declared finite characterization claims, never global behavioral equivalence. ## Failure model Distinguish artifact mismatch, target ambiguity, transformation failure, runtime unavailable, policy denial, unsupported value, undeclared effect, boundary escape attempt, inspector disconnect, timeout, cancellation, truncation, target crash, descendant leak, cleanup failure, and incomplete observation. ## Acceptance criteria - [ ] Provider-neutral contracts are independent of Node Inspector and any specific transformer. - [ ] A Node provider characterizes selected functions from plain, minified, and bundled fixtures. - [ ] Every run is bound to exact shipped and instrumented digests. - [ ] The authoritative artifact is never modified in place and is rehashed after execution. - [ ] Pure fixtures prove arguments, returns, throws, promises, and deterministic clock/randomness. - [ ] Bounded-effect fixtures prove module loads, files, children, loopback HTTP/WebSocket, native/Wasm boundary declarations, and cleanup. - [ ] Undeclared effects fail closed and remain visible. - [ ] Inspector attach is limited to an owned provider-launched process. - [ ] Cancellation and all resource-cleanup paths are exercised. - [ ] Static semantic evidence can be correlated without being promoted to runtime proof. - [ ] Large records are available through MCP resources. - [ ] CLI and MCP contracts, typed errors, progress, cancellation, and Tasks behavior are equivalent. - [ ] A temporary export-instrumentation fixture produces deterministic evidence twice and leaves the source tree byte-identical with no residual instrumented file. ## Relationships - Parent dynamic-observation policy: #36 - Static JavaScript semantics: #117 and #68 - Managed-runtime provider roadmap: #42 - Provider SDK: #45 - Evidence resources: #99 - Scoped approval grants: #96 and #114 - Long-running work: #97 and #98 - Fixture export: #62 ## Non-goals - Executing arbitrary bundles without approval. - Claiming instrumentation output is unmodified shipped behavior. - Attaching to unrelated user processes. - Providing a security boundary without a real sandbox or VM. - Recovering original names, comments, or source. - Replacing external process, browser, Electron, or native-binary observation.

bsakaguchi 2026-10-15 18:21:45 +00:00

• closed this issue
• added the
  area: runtime
  enhancement
  labels

bsakaguchi referenced this issue 2026-10-15 18:28:29 +00:00

[GH-ISSUE #2383] [Tracker] Audit analysis and debugging coverage for the TIOBE top 100 languages (October 2026) #794

bsakaguchi referenced this issue 2026-10-16 21:11:48 +00:00

[PR #203] [MERGED] fix: resolve triaged correctness issues #1854

bsakaguchi added

enhancement

and removed

enhancement

labels 2026-10-31 00:28:46 +00:00

bsakaguchi referenced this issue 2026-10-31 00:39:57 +00:00

[GH-ISSUE #5607] [Bug] get_objc_classes counts imported Objective-C classes twice through GOT aliases #3400

bsakaguchi referenced this issue 2026-10-31 00:40:00 +00:00

[GH-ISSUE #5617] [Bug] get_objc_classes omits Hopper class labels from a stripped Objective-C binary #3405

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#156

No description provided.