Skip to content

ci: converge exact-head coverage foundation on current main - #337

Draft
seonghobae wants to merge 39 commits into
fix/test-path-filter-contract-v1from
ci/exact-head-coverage-foundation-v5
Draft

ci: converge exact-head coverage foundation on current main#337
seonghobae wants to merge 39 commits into
fix/test-path-filter-contract-v1from
ci/exact-head-coverage-foundation-v5

Conversation

@seonghobae

@seonghobae seonghobae commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Purpose

Converge reusable exact-head coverage evidence from heavily diverged #156 onto the current dependency-root stack without importing superseded product history. #156 remains open until every useful unique test, fixture, contract, and evidence delta is merged through its current owner or explicitly rejected with exact technical evidence.

Current stack authority — 2026-09-05 KST

Coverage contract and measured RED

Frontend scope is all source-controlled production TypeScript under src/lib/**/*.ts and src/routes/**/*.ts, excluding tests/generated declarations. Rust measurement remains cargo llvm-cov --locked --no-cfg-coverage --no-cfg-coverage-nightly --all-features --manifest-path src-tauri/Cargo.toml --branch --json --output-path coverage.json. coverage-evidence.json is impossible unless region, branch, function, and line totals are each exactly 100%.

The last usable repository-wide predecessor measurement remains regions 64391/80218 = 80.270014%, branches 5292/8991 = 58.858859%, functions 3357/4924 = 68.176280%, lines 42867/53111 = 80.712094%. It is diagnostic only and does not describe the current head. Current owner has restored still-valid command/environment, cloud, minimally adapted iCloud-health, and real-filesystem Git-worktree coverage. Provider-OAuth coverage remains #339-owned; synthetic broad Podman success-path evidence is not accepted as destructive/recovery proof.

#156 inheritance ledger

Command public/environment, cloud, adapted iCloud health, the real Git-worktree public fixture, dirty-secondary preservation, and stale/prunable registration evidence remain adopted pending unchanged-head hosted compile/runtime and fresh measurement.

git_worktree_dirty_secondary_coverage.rs creates a real temporary Git repository and linked worktree, writes untracked content, audits through the current API, and requires zero removal candidates plus preservation of local bytes and branch. git_worktree_prunable_coverage.rs creates and removes a real linked worktree directory while retaining stale registration; prunable remains diagnostic evidence only and never deletion authority.

Provider-OAuth domain evidence belongs to #339; release retry/artifact identity belongs to #264. Remaining historical #156 deltas stay open for item-by-item owner classification. These adoptions do not mean #156 is fully superseded.

Merge boundary

#264 Release 33937972244 is terminal success, but its Test/Security/SAST/CodeQL gates remain queued. Keep Draft until #264 and #338 are integrated in order or equivalently present on protected lineage and one unchanged #337 exact head proves applicable Test/Release/Security/SAST/CodeQL/OSV/Scorecard plus repository-wide exact 100% coverage. No coverage exclusions, threshold weakening, force-push, destructive rebase, self-approval, administrative bypass, or predecessor-evidence transfer.

@coderabbitai

coderabbitai Bot commented Sep 3, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@seonghobae
seonghobae changed the base branch from main to fix/release-artifact-windows-namespace-v1 September 3, 2026 11:05
@seonghobae
seonghobae changed the base branch from fix/release-artifact-windows-namespace-v1 to fix/test-path-filter-contract-v1 September 3, 2026 12:21

Copy link
Copy Markdown
Contributor Author

#156 inheritance ledger (fresh verification)

  • src/lib/api.clean-dev-artifacts.coverage.test.ts is intentionally not copied. Its only contract is argument forwarding for cleanDevArtifacts; current src/lib/api.test.ts already exercises cleanDevArtifacts("/repo", 30, []) and asserts the exact clean_dev_artifacts payload. Copying the old file would duplicate evidence rather than preserve a unique delta.
  • src-tauri/tests/package_metadata_contract.rs is already present on this stack and continues to enforce the package-metadata/publish contract, so that ci: require exact-head production coverage evidence #156 evidence is inherited rather than reintroduced from the diverged product tree.
  • src/lib/coverageCommandDiagnosticBound.test.ts is already present on exact head 7330fd8f6fdb4a3a9f582376f0529d8434606ea2; no duplicate port is needed.

This is only a partial ledger. #156 remains open until every unique coverage/evidence test, fixture, workflow contract, and supporting script has either been inherited into the current owner stack or rejected with current-code evidence. No product implementation from the diverged #156 branch is being overlaid mechanically.

Copy link
Copy Markdown
Contributor Author

#156 inheritance ledger update: the old providerOauthWindowsWorkflowContract.test.ts / provider_oauth_cli_process.rs evidence is valid, but it does not belong in this coverage-only stack. The current CLI-process owner is #212. It now carries a test-first reconstruction: RED ab6812449e60583baf2402fb06e1f5fdc8629140, real shipped-binary Windows USERPROFILE regression 20a5fb375dc28eb564f413d05a4aeb16e37ab394, dedicated exact-head windows-2022 workflow GREEN b85e16042c2f8ec5bee6c0dbfde6049f087c549e, and non-force current-main restack 92c65229a89cf2f7d334d9c6575a9126012a3505. Exact-head Provider OAuth Windows/Test/Release/Security/SAST/OSV/Scorecard runs are newly queued, so this is inherited source/test/workflow delta but not yet terminal merge evidence. #156 remains open for the remaining unique ledger.

Copy link
Copy Markdown
Contributor Author

Fresh #156 inheritance verification (2026-09-04): its latest RED 0e705002765c21777c59f72ce4bf9ebe7feb243a and fix a3803fced0bdbb4f8eb9d19d07a623b1422e5204 do not require another code copy here. Exact #337 head af39bce9bb6ac3186e3940e2c94dd8381080f619 already contains the same executable contract: coverageEvidenceWorkflow.test.ts requires the bounded fallback coverage diagnostic rendering failed; raw diagnostic withheld, and .github/workflows/test.yml writes that fallback before returning the authoritative coverage exit status when diagnostic rendering/redaction fails. #337 additionally keeps its current always() && hashFiles('coverage.json') != '' evidence-build semantics. Treat these two latest #156 deltas as verified inherited by the coverage owner, not as a reason to duplicate or cherry-pick stale branch history. #156 remains open for other unclassified unique evidence.

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

Labels

maintenance priority: medium Normal-priority or P2 work type: maintenance Maintenance, build, dependency, or operational upkeep

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant