R21: Repeat complete validation on the internal release head

[100yenadmin]

Run unit, integration, build, typecheck, cross-platform, security, plugin, and two disposable OpenClaw canaries on the final internal release candidate head. Compare with the pristine RC19 evidence and investigate every regression.

Upstream stable v1.6.10 does not exist. R20 records the product-owner-approved internal RC19 provenance disposition; this issue must not claim a stable rebase occurred. A future stable tag is later reconciliation input and is not a blocker for this internal fork release.

Acceptance: required current-head checks are green, canaries pass twice, no unresolved P0-P2 review finding remains, and operational confidence is at least 95%.

Depends on: R20 disposition and all retained capability issues.

Parent epic: #39

Tracking ID: R21

[100yenadmin]

Dependency validation split into #84 / PR #85 from current PR #83 head. Focused proof: root/core/web npm audits are 0; Pygments is 2.20.0; fresh installs, shared/core/web builds, core typecheck, 384 web tests, governance, and CI-equivalent formatting pass. Remote current-head CI and R19 canaries remain release gates.

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #60 - R21: Repeat complete validation on the internal release head
State: open; milestone: GitNexus v1.6.10 Reconciliation - Sprint 4 - Internal RC19 Promotion and Governance

Related issues/PRs: #39.
Existing labels: reconciliation, P0, evidence-gate, release-blocker.
Suggested labels: bug, security.
Suggested owners: none.

Related context

• EPIC: Reconcile evaOS GitNexus on the v1.6.10 RC lineage #39 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.

Agent-start packet

Problem shape: R21: Repeat complete validation on the internal release head - Run unit, integration, build, typecheck, cross-platform, security, plugin, and two disposable OpenClaw canaries on the final internal release candidate head. Compare with the pristine RC19 evidence and investigate every
Product fit: Product/market issue; check vision fit, customer value, and whether external precedent can reduce time-to-market.
Implementation wedge: Start with a bounded adapter/contract or dry-run packet before changing live runtime behavior.

Build / borrow / buy scan:

• Build: identify the smallest implementation wedge that proves the issue without broad rollout.
• Borrow: inspect same-repo prior art, repo memory, GitNexus context, and allowlisted cross-repo examples first.
• Buy/use: run capped external OSS/library/API/current-market research with citations, observed dates, and why each source matters.

Candidate sources:

• VISION.md / repo policy / repo-memory.md / GitNexus packet.
• Same-repo issues and PRs referenced by issue metadata.
• Allowlisted cross-repo GitHub examples with direct issue/PR/repo URLs.
• External OSS repositories or library/API docs with freshness dates.
• Current market/product examples, capped and cited, only when they change implementation direction.

Acceptance criteria:

• Preserve and execute the issue's stated acceptance criteria.
• Include source citations for any external OSS/library/current-market claims.
• Keep issue-enrichment comments sticky and idempotent.
• Keep labels, owners, reviewers, and roadmap fields suggestion-only.

Proof plan:

• Focused unit/fixture test for the changed planner behavior.
• Dry-run issue-enrichment evidence packet before live comment posting.
• Redaction check for issue body, citations, and generated markdown.
• Contract or degraded-mode proof before runtime promotion.

Known traps:

• Do not treat related links as proof by themselves; each source needs a reason why it matters.
• Do not scan old issue backlogs or exceed repo-level enrichment throttles.
• External research must stay capped, cited, fresh-dated, and redacted.
• Technical severity alone can miss product/UX regressions; include product-manager review framing.

Non-goals:

• Do not auto-apply labels, owners, reviewers, roadmap fields, or milestones.
• Do not bulk-enrich old backlog issues from this planner output.
• Do not claim external market or OSS research was performed unless cited sources are present.

Context-source taxonomy:

• [enabled] vision_repo_policy_memory_gitnexus: Use repo vision, policy, memory, and GitNexus first before external research.
• [enabled] same_repo_issues_prs: Issue metadata contains same-repo references.
• [enabled] allowlisted_cross_repo_github: Triggered by issue class; keep to configured allowlist and source caps.
• [enabled] external_oss_examples: Use for build/borrow/buy precedent with citations and observed dates.
• [enabled] library_api_docs: Use when implementation may depend on a module, SDK, API, or framework choice.
• [enabled] current_market_examples: Use for product/UX/market positioning issues with freshness dates.
• [enabled] internal_mcp_docs: Use internal docs/MCP context when available; missing context is degraded, not blocking.

Validation suggestions

• Confirm owner, acceptance criteria, and validation evidence before implementation.

Triage gaps

• No obvious issue triage gap detected from issue metadata.

No labels, owners, reviewers, or roadmap fields were changed by this bot.

[100yenadmin]

R21 validation is active on draft PR #97 at exact head 69a1ef53076a4b5708be59081a475c725088b56e.

Local focused gate: 13 files and 182 tests passed, including the large incremental subprocess case, canary environment isolation, scan/import resolution, scope lookup, community/cohesion, graph golden, and C-family PDG snapshots. git diff --check is clean.

Remote CI is running. Final disposable OpenClaw canary 1 is concurrently in initial analysis against public source SHA c0465b863c798e35cc7fac882e1a2c5583b4b21b, with a dedicated clone, isolated home/index, deterministic local embeddings, and no live-index access.

The latest #91 coverage runner stopped before tests because npm omitted optional @huggingface/transformers; prior matrices installed it successfully. This is retained as a runner artifact and will receive a clean rerun, not a source workaround.

Exact next action: complete #97 current-head CI/review while canary 1 runs, then execute canary 2 sequentially.

[100yenadmin]

R21 head moved to 7f081ffec3844594c996c17506bee52ad3a6e339 after CI caught and localized a real Rust resolver regression in the initial global scan sort.

The corrected implementation preserves scan/parse order and canonicalizes only the first-wins suffix index. Local proof is 360/360 in the full focused matrix, 160/160 additional suffix-index call-site tests, 302/302 on the fork capability branch, and a successful production build.

The invalid canary was stopped during initial analysis. Corrected canary 1 is now running in a new disposable clone/evidence path; it has no live-index access. Exact-head CI has restarted on PR #97.

[100yenadmin]

Adversarial review hardening landed on the canary capability branch at 74e003ab and on the integration branch at 67370753.

Confirmed findings addressed:

• fail-closed evidence/worktree symlink containment with exclusive 0600 artifacts;
• append-only retry logs, snapshots, and comparison evidence;
• owned child process groups with SIGINT/SIGTERM tree termination;
• named durable recovery boundaries before deletion, after the first wipe member is removed, after the first node COPY commits, and immediately before final metadata save;
• subprocess recovery coverage now SIGTERMs and recovers at all four boundaries before comparing with a forced rebuild.

Focused local proof: TypeScript no-emit check, production build, Prettier check, ESLint with zero errors, and 26 safety/environment/determinism tests. The expanded native four-boundary recovery matrix is intentionally running in GitHub Actions so it does not compete with the disposable OpenClaw analysis already running on the Mac.

The active pre-hardening OpenClaw run remains safe for its concrete inputs (no tracked TypeScript symlinks and no evidence symlinks), but it is diagnostic only. Final counted canaries will use the reviewed exact head. No live index, package publication, or runtime surface was touched.