Skip to content

fix(ui): correct P-07 default sweep targets - #645

Closed
ndrorchestration wants to merge 6 commits into
mainfrom
fix/tools-default-targets-643
Closed

ndrorchestration wants to merge 6 commits into
mainfrom
fix/tools-default-targets-643

Conversation

@ndrorchestration

@ndrorchestration ndrorchestration commented Sep 11, 2026

Copy link
Copy Markdown
Owner

Purpose

Preserve the bounded P-07 Tools default-target correction: replace stale/nonexistent defaults with repository paths that actually exist while leaving sweep execution and authority semantics unchanged.

Intended effective change

Defaults:

  • pages/api/health.ts
  • pages/api/sweep.ts
  • requirements.txt

Retired/nonexistent defaults remain regression-guarded:

  • api/health.py
  • app/api/health/route.ts

Mutation: NONE · Input: PATHS ONLY · Harmonic score: NOT ASSUMED · Authority effect: NONE.

Current disposition — 2026-09-15

DRAFT / HOLD / STALE-LINEAGE. DO NOT MERGE AS-IS.

Current protected main is 1fb2c665587d5a0e7b213aef1cc5c870097cdc9b. Track A Epoch 002 collection is COMPLETE; operator retained-byte provenance remains PENDING; dataset lock is NOT ESTABLISHED; unblinding/primary analysis remain NOT AUTHORIZED.

This correction is not on the #679 critical path. Because the accepted operator dataset-lock evidence preparer binds to exact executing repository HEAD, do not reconcile or merge this UI lane before the retained-byte checkpoint merely to reduce backlog.

Reconciliation rule

After the retained-byte/evidence-admission frontier reaches a stable accepted boundary:

  1. reconstruct the bounded correction from exact then-current main;
  2. re-confirm all intended default paths exist and remain appropriate under the current runtime architecture;
  3. confirm the effective delta remains limited to default-input correctness;
  4. preserve /api/sweep non-mutating semantics and harmonic_score: null / NOT_COMPUTED behavior;
  5. require fresh exact-head UI/build/governance validation plus applicable external deployment evidence.

No historical validation transfers.

Governance boundary

UI/default-input correctness only. No governance/scientific state, dataset lock, unblinding, analysis authority, efficacy, High-Assurance status, or scientific-N increment changes.

@vercel

vercel Bot commented Sep 11, 2026

Copy link
Copy Markdown

Deployment failed for project dynamicgovernanceagenticformation with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/ndrorchestration?upgradeToPro=build-rate-limit

Copy link
Copy Markdown
Owner Author

Current-lineage reconstruction is now underway in #739 from protected main ca10b9c1e6c73119a66488f15895848538dc6f29. Fresh TDD was reproduced there: RED UI run 35104754121 failed exactly on the intentionally missing shared defaults module (22/23 passed), then GREEN UI run 35104957269 passed semantic/contract tests and the production build on candidate head 5ca0da6fea5917da7288fb98a1c8bdeda7d48479. #645 remains historical/stale lineage and should not be merged; close it only after the replacement lane is accepted or otherwise explicitly disposed.

Copy link
Copy Markdown
Owner Author

Superseded by accepted current-lineage reconstruction #739, merged to protected main as ab1418038fba08d91ce50e453b1a49ef2d795693. #739 reproduced fresh RED→GREEN evidence from then-current main and preserved the bounded three-file correction without transferring historical validation. Keep #645 only as provenance; do not merge this stale branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant