npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-grasp-mirror/grasp-audit/src/specs/grasp01/nip01_smoke.rs, branch masterUnnamed repository; edit this file 'description' to name the repository.
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-grasp-mirror/atom?h=master2026-02-13T12:31:49+00:00fix: use ValidRepoServed for events that tag repo events2026-02-13T12:31:49+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-13T12:07:37+00:00urn:sha1:a2a99d5a4137b57e4141cf2840f2f51b38035cfa
PR events, issues, and comments need a queryable repo announcement
to reference. Changed PREvent and PREventGenerated fixtures and
related tests to depend on ValidRepoServed instead of ValidRepoSent.
This ensures tests will fail correctly when announcement purgatory
is implemented - events tagging a repo should require that repo
to be served (not in purgatory).
refactor(grasp-audit): split ValidRepo into Sent/Served, add tolerant purgatory2026-02-12T12:57:44+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-12T12:57:44+00:00urn:sha1:dcaaa0c44c46f963929ab0baa91f63759ec702dc
- Rename ValidRepo to ValidRepoSent (announcement sent, may be in purgatory)
- Add ValidRepoServed (announcement queryable after git data pushed)
- Add send_event_and_note_purgatory() for tolerant purgatory detection
- Update fixtures to use tolerant method instead of strict assertion
- Update event_acceptance_policy tests to use ValidRepoServed
This enables tests to pass regardless of purgatory implementation status
while still having explicit purgatory tests that verify the behavior.
refactor(grasp-audit): introduce SpecRef enum for type-safe spec references2026-02-12T12:36:23+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-12T12:36:23+00:00urn:sha1:3fd6ce4149d567c67009b0332ca76c0cd6f51055
Replace string-based spec references with typed SpecRef enum for
compile-time validation and better IDE support. TestResult::new() now
accepts SpecRef enum plus a requirement description string for
test-specific context.
refactor: replace hardcoded Kind constants with rust-nostr variants2026-01-08T11:23:28+00:00DanConwayDevDanConwayDev@protonmail.com2026-01-08T11:20:35+00:00urn:sha1:5d02ad6b893f9059044914c115d77cf9d8e589c3
- Replace KIND_REPOSITORY_ANNOUNCEMENT with Kind::GitRepoAnnouncement
- Replace KIND_REPOSITORY_STATE with Kind::RepoState
- Replace KIND_PR with Kind::GitPullRequest
- Replace KIND_PR_UPDATE with Kind::GitPullRequestUpdate
- Replace KIND_USER_GRASP_LIST with Kind::GitUserGraspList
- Replace KIND_PATCH with Kind::GitPatch
- Replace KIND_ISSUE with Kind::GitIssue
- Replace KIND_COMMENT with Kind::Comment
- Replace all Kind::Custom(30617|30618|1617|1618|1619|1621|1111|10317) patterns
- Remove all hardcoded KIND_* constants from events.rs
- Update all match statements to use Kind enum directly
- Update all filter builders to use Kind variants
- Update all test helpers and assertions
Benefits:
- Type safety: compiler prevents wrong kind numbers
- Readability: Kind::GitRepoAnnouncement is self-documenting
- Maintainability: single source of truth (rust-nostr)
- IDE support: full autocompletion and refactoring
- Standards: aligns with rust-nostr best practices
Files modified: 21
Constants removed: 9
Patterns replaced: 100+
Tests passing: 222/222
chore: bump rust-nostr to latest master2025-12-22T21:02:03+00:00DanConwayDevDanConwayDev@protonmail.com2025-12-22T21:02:03+00:00urn:sha1:1df90c609399c675e629b97294aee81a0b1e66dd
so we can more easily support grasp purgatory feature
fix: resolve all fmt and clippy warnings2025-12-11T16:53:03+00:00DanConwayDevDanConwayDev@protonmail.com2025-12-11T16:53:03+00:00urn:sha1:2a9160836bb87fdea3ae891563b0169c68d1c2ab
Main lib (src/):
- Add #[allow(dead_code)] for build_info field (stored to prevent Prometheus unregistration)
- Add #[allow(dead_code)] for first_seen field (reserved for future rate limiting)
- Replace .or_insert_with(RelaySyncNeeds::default) with .or_default()
- Replace manual div_ceil implementations with .div_ceil(100)
Test code (tests/):
- Replace .expect(&format!(...)) with .unwrap_or_else(|_| panic!(...))
- Remove needless borrows in fetch_metrics() calls
- Add #[allow(dead_code)] and #[allow(unused_imports)] to test helpers module
grasp-audit:
- Apply cargo fmt to fix formatting
refactor: rename AuditMode variants and change CLI default to shared2025-12-02T21:20:17+00:00DanConwayDevDanConwayDev@protonmail.com2025-12-02T21:20:17+00:00urn:sha1:72683beea066d066637e747c40dc859fb709babf
Breaking change: Renamed AuditMode enum variants for clarity:
- AuditMode::CI -> AuditMode::Isolated (fresh fixtures per test)
- AuditMode::Production -> AuditMode::Shared (reuse fixtures across tests)
Config constructors renamed (with deprecated aliases):
- AuditConfig::ci() -> AuditConfig::isolated()
- AuditConfig::production() -> AuditConfig::shared()
CLI default changed from 'ci' to 'shared' mode, which enables
fixture caching across tests. This fixes the issue where fixtures
were being re-created for every test in CLI mode.
Fixture caching behavior:
- Shared mode (CLI default): Uses client's cache, fixtures reused
- Isolated mode (for cargo test): Local cache per TestContext
grasp-audit: show tests under GRASP-01 line2025-12-02T21:03:24+00:00DanConwayDevDanConwayDev@protonmail.com2025-12-02T20:54:15+00:00urn:sha1:5c10ca008413744b09136618eaa85275c997704cfix cargo clippy and fmt warnings2025-12-01T15:22:38+00:00DanConwayDevDanConwayDev@protonmail.com2025-12-01T14:31:32+00:00urn:sha1:d2ac69816567f092fe0d4661723bc43778cb481bfix running audit with production flag2025-11-28T02:54:34+00:00DanConwayDevDanConwayDev@protonmail.com2025-11-28T02:30:10+00:00urn:sha1:15892018705b3b4ca42586174518319adc224c0e
no events were allowed to be published which broke most tests