Skip to content

0.0.8

Choose a tag to compare

@samzhu samzhu released this 30 Jul 16:15
· 48 commits to main since this release

0.0.8 makes every enabled Independent Safeguard leave an honest result from the same formal run. It is compatible with the 0.0.7 public authoring surface: there is no new annotation, DSL, command-line option, or verifyAll API.

See every enabled safeguard's result

After CONTRACT_INTEGRITY=PASS, toppleCatVerify runs public acceptance, Hidden Tests, Property-Based Testing, and Mutation Testing in that fixed order. A completed gate that finds a problem records FAIL and does not stop later enabled gates. Expected Consumption, evidence, reviewer/public reports, safe feedback, and reviewer-source rehide complete before Gradle returns the aggregate result.

INCOMPLETE remains distinct from FAIL: it means a producer was interrupted or current-run evidence is missing or malformed. Verify clears the configured mutation report before its producer runs, so stale evidence cannot become current evidence.

Reuse the existing Mechanical Seal

Verify checks the existing Mechanical Seal and reviewer custody without updating approval. If the seal is absent, it safely reports CONTRACT_INTEGRITY=INCOMPLETE and directs the reviewer to run toppleCatSeal; only toppleCatSeal and toppleCatReseal create or replace approval.

Write expected-value checks that can all run

Prefer one c.verify("receipt", receipt) for a full receipt projection. When separate expected keys are necessary, put their verify calls in JUnit assertAll. A failed verify is still ASSERTED; a later value not reached remains UNTOUCHED.

Upgrade

Update the plugin and JUnit dependency to 0.0.8. Existing seals use the 0.0.8 policy/version format; after upgrading, restore reviewer custody, Check, Review, and Reseal before Verify.

Requirements

Java 25 and the existing compatible Gradle requirement are unchanged.

0.0.8 讓每一個已啟用的獨立防線都留下同一次正式執行的誠實結果。它與 0.0.7 的公開
撰寫介面相容:沒有新增 annotation、DSL、命令列選項或 verifyAll API。

看見每道已啟用防線的結果

當 CONTRACT_INTEGRITY=PASS 後,toppleCatVerify 依固定順序執行公開驗收、隱藏測試、
性質導向測試與突變測試。已完整執行且發現問題的 Gate 會記錄為 FAIL,不會阻擋後續
已啟用 Gate。Expected Consumption、evidence、審閱者/公開報告、安全回饋與重新隱藏
審閱者原始碼都完成後,Gradle 才回傳唯一的整體 FAIL 或 INCOMPLETE。

INCOMPLETE 與 FAIL 的意義仍不同:它表示 producer 被中斷,或本次執行證據缺失、
損壞。Verify 會在 mutation producer 開始前清除設定的報告,所以舊報告不能變成本次證據;
即使 consumer-owned producer 被 Gradle 跳過也是如此。Verify 也會在 Integrity 比較既有 seal 前
重建已檢查的 definition,並在開始前捨棄未封存的 run workspace。Property 回饋會區分反例與 task/證據中斷;Mutation 回饋會區分存活 mutant 與 producer
證據缺失或損壞。

沿用既有 Mechanical Seal

Verify 現在會在內部檢查既有的 Mechanical Seal 與 reviewer custody,並記錄沿用 seal、
沒有更新 approval。沒有 seal 時,Verify 會安全記錄
CONTRACT_INTEGRITY=INCOMPLETE,並提示 reviewer 先執行 toppleCatSeal;只有
toppleCatSeal 與 toppleCatReseal 能建立或取代 approval。

撰寫能全部執行的預期值驗證

完整收據投影優先使用一次 c.verify("receipt", receipt)。必須驗證多個獨立 expected key
時,請把各個 verify 放在 JUnit assertAll。失敗的 verify 仍是 ASSERTED;若前一個
assertion 擲出例外,後面未呼叫的值仍是 UNTOUCHED。因此 JUnit 與 Expected Consumption
同時失敗可能各自提供有用證據,不是重複回報。

升級

將 plugin 與 JUnit dependency 更新為 0.0.8。既有 seal 使用目前限定的 0.0.8
policy/version 格式;更新 ToppleCat 座標後,先 Restore reviewer custody,再 Check、Review、
Reseal,最後才 Verify。

環境需求

Java 25 與既有相容 Gradle 的需求沒有改變。