S00-002: Propose a pinned React stack with a reproducible rendering spike

Changes: Compare React and Vue in ADR 0001; pin React 19.3.1, TypeScript 7.0.2, Vite 8.3.4 and Node 24.21.0/npm 11.19.0. Add isolated TSX counter, exact lockfile, runtime/TLS guards, reproduction instructions and license inventory/runtime notices. Preserve the reviewed registry probe and leave ADR proposed for security review.
Validation: Clean npm ci with a fresh cache and npm run build passed on the pinned tools; strict typechecking and repeated local build hashes matched. HTTP preview served HTML and matching JS. make check passed all 66 tooling tests; git diff --check passed. Browser interaction was unavailable and is recorded as an external check; no app, crypto/protocol interoperability or release readiness is claimed.

Task: S00-002
Agent: auto-orchestrator-68a05c587e33
Role: orchestrator
Action: claim
Status: review

Task title: Выбрать framework и build runtime
This commit is contained in:
wt committed 2026-10-15 01:18:53 +07:00
1 parent 06f353b214
commit 59b9ff62fe
21 files changed
+1729 -16

No files matched your search

+6 -6
View File
@@ -1,10 +1,10 @@
# S00-002 blocker handoff
# S00-002 handoff for independent security review
Executor: auto-orchestrator-3a4f07103316, orchestrator.
Outcome reached: required instructions, task packet, NFR-007, accepted ADR 0000 and S00-001 evidence/review read. React/Vite and Vue/Vite primary documentation opened for comparison; no selection made. No source changes, stack ADR, package.json or lockfile authored.
Executor: auto-orchestrator-68a05c587e33 (orchestrator), 2026-10-15.
Outcome: proposed ADR 0001 compares React and Vue, selects exact React/TypeScript/Vite pins and Node 24.21.0 LTS / bundled npm 11.19.0. One isolated TSX rendering spike, lockfile, runtime/TLS guards, license inventory and runtime notices created in experiments/0001-stack. Registry-access probe retained unchanged. No blocker; prior registry failure did not recur.
Blocker: local npm metadata lookup fails with `getaddrinfo ENOTFOUND registry.npmjs.org`; cannot verify package versions/licenses or perform required clean install/build. Reproduce with `npm view react version license engines --json --cache /private/tmp/luma-stack-npm-cache --fetch-retries=0 --fetch-timeout=15000` (actual exit 1). Node v26.3.0 and npm 11.16.0 observed; not accepted runtime choices. Evidence: state/evidence/S00-002-auto-orchestrator-3a4f07103316.md.
Actual checks: clean npm ci with fresh empty cache, strict TypeScript/Vite build before/after ci, identical local artifact/lock SHA256, HTTP preview HTML and byte-matching JS, make check (66 tests) all exit 0. Full commands, pins, digests, setup failures and limits: state/evidence/S00-002-auto-orchestrator-68a05c587e33.md.
One external remediation requests an execution environment with working DNS/HTTPS to the public npm registry and package tarballs. Keep TLS validation and project write sandbox. No credentials or secret values requested. Resolver must verify metadata and one integrity-checked tarball retrieval, document the safe runner configuration/action, and obtain independent review. Resolver must not choose stack or implement rendering; those remain S00-002.
Next step belongs only to separate assigned security reviewer. Read ADR/card/evidence and executor commit/message. From experiments/0001-stack with Node 24.21.0 / npm 11.19.0, run the README's clean npm ci and npm run build. Existing verified macOS ARM64 runtime is at /private/tmp/luma-stack-runtime/node-v24.21.0-darwin-arm64, or retrieve the official exact runtime with verified HTTPS/checksum. Inspect exact manifest/lock pins, licenses including build-only MPL-2.0, runtime notices, no production transport/secrets and no source changes outside card scope. Record acceptance and reviewer metadata in ADR only if warranted, then approve/reject through tasks.py.
After reviewed remediation, coordinator launches a fresh S00-002 executor. Continue candidate comparison from primary sources, choose and pin supported runtime/tool versions, create one minimal rendering spike only within experiments/0001-stack, perform actual clean install/build and record license/browser limits in docs/decisions/0001-stack.md. Current reporter exits after escalate and must not resume or resolve remediation.
DOM rendering/counter interaction is an external check: no browser is exposed by this harness. README gives manual steps; do not label them passed. Current compiler floors are not the product browser matrix. Vue was not built or benchmarked. Crypto/XMPP compatibility, full app CI, notices for future libraries, other build-host platforms, provider integration and release readiness remain subsequent cards. Shared contracts/specs/plan definitions unchanged. ADR remains proposed; executor does not set done or perform Git mutations. Coordinator commits this submission and launches the reviewer.