Repository navigation
Conversation
This was referenced Nov 19, 2026
Closed
Collaborator
Author
|
Superseded by #1033:18 张 OPS-PTC 卡的实现已随统一 PR 合入 main(本 PR 的提交已在 main 中),保留为评审记录。 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #992
What was wrong
The two-tier OPS-PTC publication rule (disclosurePolicy on-demand vs full, plus the legacy off variants) was verified by per-case suites, so a name that exists in a catalogue but is not callable in the current step could slip through if only one view (a name list, a description, or a binding) was checked. Issue #992 asked for one data-driven acceptance matrix covering both publication paths with the same comparison logic.
The change
Validation
Red first (honest sequence): the initial run failed 5 rows on boot mechanics (the unset sandbox mode suppressed every publication) and, after that fix, 3 rows on wrong expectations — each correction either matched shipped behaviour (loaded sets must include result; the directory text disappears when the pool is exhausted; the custom integration admits its own ops_status diagnostics reader) or fixed the suite's own probe (a raw-name tools.glob vs ops_glob binding typo, a sentinel that broke lossless JSON, run_code not being part of the registry views).
Green after (npm run build first; worker DSH_OPS_WORKER_BIN=runtime/linux-x64/dsh-ops-worker, sha256 2b5f988d…):
撤回即红 demonstrated live: corrupting the global-off row's expected set (as if the dynamic admission condition had been removed) fails with
and restoring the row returns the suite to 16/16 green. The in-suite drift-property checks reproduce this mechanically on real collected views.
CI: not run per card instruction (定向验证 only; the full gate is deliberately out of scope for this slice).