Scorecard alert #2 reports no fuzzing integration. Four FsCheck properties (500 cases each) are implemented locally but not on main.
Acceptance criteria
Publish the properties and private test dependency; keep all unit/coverage gates passing; rerun Scorecard and verify the actual Fuzzing result before closing the alert; document shrunk counterexample replay.
Scope
AppKit core and updates.
This issue is part of the user-requested AppKit readiness remediation. Local work is not completion until the applicable published/runtime state and checks are verified. Substantial AI assistance: Codex.
## Problem
Scorecard alert #2 reports no fuzzing integration. Four FsCheck properties (500 cases each) are implemented locally but not on main.
## Acceptance criteria
Publish the properties and private test dependency; keep all unit/coverage gates passing; rerun Scorecard and verify the actual Fuzzing result before closing the alert; document shrunk counterexample replay.
## Scope
AppKit core and updates.
This issue is part of the user-requested AppKit readiness remediation. Local work is not completion until the applicable published/runtime state and checks are verified. Substantial AI assistance: Codex.
Generated-input coverage is committed locally in AppKit 4cea46bb1dbb3a0d38011fafef0b2443c6d0e53d.
Four FsCheck properties run 500 cases each in the normal unit suite, covering settings repair, malformed bytes, JSON persistence and log tails. All 119 unit tests pass and core/updates remain at 100% line coverage. The UI helper foreground fix also passed all 12 sample UI tests.
Remaining: publish through CI, rerun Scorecard and inspect detection. These bounded properties do not prove large-file resilience; that remains #18. Signed and signed-off commit; AI assistance: Codex (GPT-6).
Generated-input coverage is committed locally in AppKit `4cea46bb1dbb3a0d38011fafef0b2443c6d0e53d`.
Four FsCheck properties run 500 cases each in the normal unit suite, covering settings repair, malformed bytes, JSON persistence and log tails. All 119 unit tests pass and core/updates remain at 100% line coverage. The UI helper foreground fix also passed all 12 sample UI tests.
Remaining: publish through CI, rerun Scorecard and inspect detection. These bounded properties do not prove large-file resilience; that remains #18. Signed and signed-off commit; AI assistance: Codex (GPT-6).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
Scorecard alert #2 reports no fuzzing integration. Four FsCheck properties (500 cases each) are implemented locally but not on main.
Acceptance criteria
Publish the properties and private test dependency; keep all unit/coverage gates passing; rerun Scorecard and verify the actual Fuzzing result before closing the alert; document shrunk counterexample replay.
Scope
AppKit core and updates.
This issue is part of the user-requested AppKit readiness remediation. Local work is not completion until the applicable published/runtime state and checks are verified. Substantial AI assistance: Codex.
Generated-input coverage is committed locally in AppKit
4cea46bb1dbb3a0d38011fafef0b2443c6d0e53d.Four FsCheck properties run 500 cases each in the normal unit suite, covering settings repair, malformed bytes, JSON persistence and log tails. All 119 unit tests pass and core/updates remain at 100% line coverage. The UI helper foreground fix also passed all 12 sample UI tests.
Remaining: publish through CI, rerun Scorecard and inspect detection. These bounded properties do not prove large-file resilience; that remains #18. Signed and signed-off commit; AI assistance: Codex (GPT-6).