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

[GH-ISSUE #649] [Docs] README, AGENTS.md, and docs/testing.md still describe the removed TypeDoc API docs pipeline #308

New issue
Closed
opened 2026-10-15 18:23:43 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-15 18:23:43 +00:00
Owner
Copy link

Originally created by @coygeek on GitHub (Oct 6, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/649

Summary

The commit "chore(deps): remove incompatible TypeDoc generator" removed the docs:api and docs:api:cached scripts, the docs:api Turbo task, typedoc.json, and the CI step that uploaded the api-docs artifact, and it updated CONTRIBUTING.md and removed the docs:api:cached row from the docs/testing.md command table. The follow-up pull request #644 added a conformance test that asserts the removal. Four statements on main still describe the removed pipeline: two in README.md, one in AGENTS.md, and one in docs/testing.md. A contributor or coding agent who follows AGENTS.md and runs npm run docs:api:cached gets a missing-script error, and readers of README.md are told that PR CI renders TypeDoc and publishes an api-docs artifact, which it no longer does.

Affected area

  • README.md:385: "PR CI verifies this catalog, narrative documentation, generated schemas, and a clean TypeDoc render."
  • README.md:654: "PR CI publishes generated API documentation as the api-docs artifact."
  • AGENTS.md:38: "npm run docs:check: check committed generated documents; npm run docs:api:cached separately renders API HTML when needed."
  • docs/testing.md:232-233: "TypeDoc rendering is a separate command and CI step."
  • Related qualifier, docs/testing.md:185: the npm run docs:check row says "Committed generated-document freshness, without API HTML rendering". At 4.0.1 this contrasted with the next row, npm run docs:api:cached ("Explicit cached API HTML rendering"), which the removal deleted. The qualifier is not false by itself, but it now points at a rendering path that no longer exists.

Runtime or environment

  • Repository: main at 19f8cddfd6, fresh clone.
  • Removal commit: 965d0b35f9.
  • Latest published release: rea-agents 4.0.1 (tag rea-agents-4.0.1, feeb19b8b3), which predates the removal.
  • Local tools: Node.js v22.23.2 and npm 12.0.2 on macOS. These differ from the Node.js 24.18.x and npm 11.16.x that CONTRIBUTING.md asks contributors to use; the result below comes from npm's script lookup in package.json and needs no installed dependencies.

Steps to reproduce

  1. Clone the repository and check out the main baseline above.
  2. Read the locations listed under Affected area.
  3. Without installing dependencies, run npm run docs:api:cached and npm run docs:api in the clone root.
  4. Search the tree: grep -rn -i 'typedoc\|api-docs\|docs:api\|api html' --exclude-dir=node_modules --exclude-dir=.git . | grep -v package-lock.
  5. Optional CI check: list the artifacts of any PR CI run after the removal commit, for example run 37412309539 (pull request #647, head commit e4bf5048): gh api repos/morluto/rea/actions/runs/37412309539/artifacts --jq '.artifacts[].name'. Then list the steps of its "Docs Generation" job.

Expected behavior

After the removal commit, the documentation should describe only the documentation checks that exist. CONTRIBUTING.md on main already does this: "docs:check checks committed generated metadata. docs:generate regenerates those files, and the docs CI lane checks them." The conformance test tests/conformance/releaseConfiguration.test.ts ("keeps generated API HTML out of the tracked tree") asserts that typedoc.json is absent and that package.json has no docs:api script, so the removal is intentional. README.md, AGENTS.md, and docs/testing.md should therefore not claim that PR CI performs a TypeDoc render, that it publishes an api-docs artifact, or that npm run docs:api:cached renders API HTML.

Actual behavior

All four statements and the qualifier are present verbatim on main. Running the script named in AGENTS.md fails. Each command also printed a final line pointing at npm's local debug log; that line is omitted below.

$ npm run docs:api:cached
npm error Missing script: "docs:api:cached"
npm error
npm error To see a list of scripts, run:
npm error   npm run
exit=1

$ npm run docs:api
npm error Missing script: "docs:api"
npm error
npm error To see a list of scripts, run:
npm error   npm run
exit=1

On main, npm run lists docs:generate, docs:generate:unlocked, docs:check, docs:check:built, and docs:error-schema, but no docs:api* script. turbo.json has no docs:api task, and .github/workflows/ci.yml has no docs:api:cached step and no api-docs upload. The PR CI run 37412309539 uploaded eight artifacts: vitest-report-0 through vitest-report-3, rea-dist, reconstruction-readiness, windows-capabilities, and test-results. None of them is api-docs. Its "Docs Generation" job ran only npm ci and npm run docs:check between setup and teardown. The grep in step 4 finds no other matches besides the four stale statements, the docs/testing.md:185 qualifier, the conformance test above, and historical CHANGELOG.md entries.

Evidence

  • Expected source: CONTRIBUTING.md:55-56 and tests/conformance/releaseConfiguration.test.ts:104-112 on main, plus the removal commit's diff of package.json, turbo.json, typedoc.json, and .github/workflows/ci.yml.
  • Failure source: README.md:385, README.md:654, AGENTS.md:38, and docs/testing.md:232-233 (with the related qualifier at docs/testing.md:185) on main, with the npm run docs:api:cached output and the CI run 37412309539 artifact list shown under Actual behavior.
  • Evidence provenance: observed
  • Local verification: reproduced
  • Reproduction completeness: complete

The evidence above comes from a fresh clone, local npm run, and read-only GitHub API queries for the CI run. The removal commit deleted exactly the scripts, Turbo task, config file, and CI upload step that these four statements describe. At the 4.0.1 tag the scripts docs:api (typedoc) and docs:api:cached (turbo run docs:api), the docs:api Turbo task, typedoc.json, and the CI upload of build/api-docs as api-docs all exist, so the same four statements were accurate for the 4.0.1 release. This report concerns main only. README.md is in the package files list, and the open release pull request #635 for 4.0.2 does not change these lines, so the next npm release would carry the stale README.md statements unless they are corrected first.

Restoration check

On main, README.md, AGENTS.md, and docs/testing.md no longer state or imply that PR CI performs a TypeDoc render, publishes an api-docs artifact, or that npm run docs:api:cached (or docs:api) renders API HTML. Any documentation command a reader is told to run exists in package.json. Repeating the grep in step 4 returns no matches in README.md, AGENTS.md, or docs/testing.md that describe TypeDoc, an api-docs artifact, or a docs:api* command; the remaining matches are historical CHANGELOG.md entries, the conformance test that asserts the removal, and at most a reworded docs/testing.md:185 row that no longer implies a separate API HTML rendering command. As a control, the existing conformance test that asserts the absence of typedoc.json and the docs:api script still passes. A wording change that only renames the missing command, or one that reintroduces a TypeDoc step without a working script and CI step, does not restore the contract.

Additional context

Issue #643 ("docs:api broken under TypeScript 7 (typedoc incompatible)") led to the removal and was closed with a comment that "related docs were removed." The removal commit updated CONTRIBUTING.md and the docs/testing.md command table but not the four statements above. The translated READMEs (README_ar.md, README_ja.md, README_ko.md, README_zh.md) contain no TypeDoc, api-docs, or docs:api string.

Triage assessment

  • Impact level: P3
  • Assessment status: supported
  • Impact basis: Following the stale text causes no data loss or broken product behavior. npm run docs:api:cached fails immediately with a clear missing-script error, and the README claims about PR CI only misdescribe contributor tooling. The effect is limited to contributors and coding agents who read AGENTS.md, README.md, or docs/testing.md.
  • Workaround status: available
  • Workaround basis: CONTRIBUTING.md on main correctly describes docs:check and docs:generate as the documentation checks, and npm run lists the scripts that exist. No API HTML rendering exists to preserve.
Originally created by @coygeek on GitHub (Oct 6, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/649 ## Summary The commit "chore(deps): remove incompatible TypeDoc generator" removed the `docs:api` and `docs:api:cached` scripts, the `docs:api` Turbo task, `typedoc.json`, and the CI step that uploaded the `api-docs` artifact, and it updated `CONTRIBUTING.md` and removed the `docs:api:cached` row from the `docs/testing.md` command table. The follow-up pull request #644 added a conformance test that asserts the removal. Four statements on `main` still describe the removed pipeline: two in `README.md`, one in `AGENTS.md`, and one in `docs/testing.md`. A contributor or coding agent who follows `AGENTS.md` and runs `npm run docs:api:cached` gets a missing-script error, and readers of `README.md` are told that PR CI renders TypeDoc and publishes an `api-docs` artifact, which it no longer does. ## Affected area - `README.md:385`: "PR CI verifies this catalog, narrative documentation, generated schemas, and a clean TypeDoc render." - `README.md:654`: "PR CI publishes generated API documentation as the `api-docs` artifact." - `AGENTS.md:38`: "`npm run docs:check`: check committed generated documents; `npm run docs:api:cached` separately renders API HTML when needed." - `docs/testing.md:232-233`: "TypeDoc rendering is a separate command and CI step." - Related qualifier, `docs/testing.md:185`: the `npm run docs:check` row says "Committed generated-document freshness, without API HTML rendering". At 4.0.1 this contrasted with the next row, `npm run docs:api:cached` ("Explicit cached API HTML rendering"), which the removal deleted. The qualifier is not false by itself, but it now points at a rendering path that no longer exists. ## Runtime or environment - Repository: `main` at 19f8cddfd6f283188567b8ff1e49b810d79952ee, fresh clone. - Removal commit: 965d0b35f9907d1a4a3ce16553c01f20368b576c. - Latest published release: `rea-agents` 4.0.1 (tag `rea-agents-4.0.1`, feeb19b8b3172b2827b80fde8f09570ce5aeed88), which predates the removal. - Local tools: Node.js v22.23.2 and npm 12.0.2 on macOS. These differ from the Node.js 24.18.x and npm 11.16.x that `CONTRIBUTING.md` asks contributors to use; the result below comes from npm's script lookup in `package.json` and needs no installed dependencies. ## Steps to reproduce 1. Clone the repository and check out the `main` baseline above. 2. Read the locations listed under Affected area. 3. Without installing dependencies, run `npm run docs:api:cached` and `npm run docs:api` in the clone root. 4. Search the tree: `grep -rn -i 'typedoc\|api-docs\|docs:api\|api html' --exclude-dir=node_modules --exclude-dir=.git . | grep -v package-lock`. 5. Optional CI check: list the artifacts of any PR CI run after the removal commit, for example run 37412309539 (pull request #647, head commit `e4bf5048`): `gh api repos/morluto/rea/actions/runs/37412309539/artifacts --jq '.artifacts[].name'`. Then list the steps of its "Docs Generation" job. ## Expected behavior After the removal commit, the documentation should describe only the documentation checks that exist. `CONTRIBUTING.md` on `main` already does this: "`docs:check` checks committed generated metadata. `docs:generate` regenerates those files, and the docs CI lane checks them." The conformance test `tests/conformance/releaseConfiguration.test.ts` ("keeps generated API HTML out of the tracked tree") asserts that `typedoc.json` is absent and that `package.json` has no `docs:api` script, so the removal is intentional. `README.md`, `AGENTS.md`, and `docs/testing.md` should therefore not claim that PR CI performs a TypeDoc render, that it publishes an `api-docs` artifact, or that `npm run docs:api:cached` renders API HTML. ## Actual behavior All four statements and the qualifier are present verbatim on `main`. Running the script named in `AGENTS.md` fails. Each command also printed a final line pointing at npm's local debug log; that line is omitted below. ```text $ npm run docs:api:cached npm error Missing script: "docs:api:cached" npm error npm error To see a list of scripts, run: npm error npm run exit=1 $ npm run docs:api npm error Missing script: "docs:api" npm error npm error To see a list of scripts, run: npm error npm run exit=1 ``` On `main`, `npm run` lists `docs:generate`, `docs:generate:unlocked`, `docs:check`, `docs:check:built`, and `docs:error-schema`, but no `docs:api*` script. `turbo.json` has no `docs:api` task, and `.github/workflows/ci.yml` has no `docs:api:cached` step and no `api-docs` upload. The PR CI run 37412309539 uploaded eight artifacts: `vitest-report-0` through `vitest-report-3`, `rea-dist`, `reconstruction-readiness`, `windows-capabilities`, and `test-results`. None of them is `api-docs`. Its "Docs Generation" job ran only `npm ci` and `npm run docs:check` between setup and teardown. The grep in step 4 finds no other matches besides the four stale statements, the `docs/testing.md:185` qualifier, the conformance test above, and historical `CHANGELOG.md` entries. ## Evidence - Expected source: `CONTRIBUTING.md:55-56` and `tests/conformance/releaseConfiguration.test.ts:104-112` on `main`, plus the removal commit's diff of `package.json`, `turbo.json`, `typedoc.json`, and `.github/workflows/ci.yml`. - Failure source: `README.md:385`, `README.md:654`, `AGENTS.md:38`, and `docs/testing.md:232-233` (with the related qualifier at `docs/testing.md:185`) on `main`, with the `npm run docs:api:cached` output and the CI run 37412309539 artifact list shown under Actual behavior. - Evidence provenance: observed - Local verification: reproduced - Reproduction completeness: complete The evidence above comes from a fresh clone, local `npm run`, and read-only GitHub API queries for the CI run. The removal commit deleted exactly the scripts, Turbo task, config file, and CI upload step that these four statements describe. At the 4.0.1 tag the scripts `docs:api` (`typedoc`) and `docs:api:cached` (`turbo run docs:api`), the `docs:api` Turbo task, `typedoc.json`, and the CI upload of `build/api-docs` as `api-docs` all exist, so the same four statements were accurate for the 4.0.1 release. This report concerns `main` only. `README.md` is in the package `files` list, and the open release pull request #635 for 4.0.2 does not change these lines, so the next npm release would carry the stale `README.md` statements unless they are corrected first. ## Restoration check On `main`, `README.md`, `AGENTS.md`, and `docs/testing.md` no longer state or imply that PR CI performs a TypeDoc render, publishes an `api-docs` artifact, or that `npm run docs:api:cached` (or `docs:api`) renders API HTML. Any documentation command a reader is told to run exists in `package.json`. Repeating the grep in step 4 returns no matches in `README.md`, `AGENTS.md`, or `docs/testing.md` that describe TypeDoc, an `api-docs` artifact, or a `docs:api*` command; the remaining matches are historical `CHANGELOG.md` entries, the conformance test that asserts the removal, and at most a reworded `docs/testing.md:185` row that no longer implies a separate API HTML rendering command. As a control, the existing conformance test that asserts the absence of `typedoc.json` and the `docs:api` script still passes. A wording change that only renames the missing command, or one that reintroduces a TypeDoc step without a working script and CI step, does not restore the contract. ## Additional context Issue #643 ("docs:api broken under TypeScript 7 (typedoc incompatible)") led to the removal and was closed with a comment that "related docs were removed." The removal commit updated `CONTRIBUTING.md` and the `docs/testing.md` command table but not the four statements above. The translated READMEs (`README_ar.md`, `README_ja.md`, `README_ko.md`, `README_zh.md`) contain no `TypeDoc`, `api-docs`, or `docs:api` string. ## Triage assessment - Impact level: P3 - Assessment status: supported - Impact basis: Following the stale text causes no data loss or broken product behavior. `npm run docs:api:cached` fails immediately with a clear missing-script error, and the README claims about PR CI only misdescribe contributor tooling. The effect is limited to contributors and coding agents who read `AGENTS.md`, `README.md`, or `docs/testing.md`. - Workaround status: available - Workaround basis: `CONTRIBUTING.md` on `main` correctly describes `docs:check` and `docs:generate` as the documentation checks, and `npm run` lists the scripts that exist. No API HTML rendering exists to preserve.
bsakaguchi 2026-10-15 18:23:43 +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#308
No description provided.