Unnamed repository; edit this file 'description' to name the repository. https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-grasp-mirror/atom?h=v1.0.2 2026-02-24T11:39:55+00:00 2026-02-24T11:39:55+00:00 DanConwayDev DanConwayDev@protonmail.com 2026-02-24T11:39:55+00:00 urn:sha1:aa40780d6f1710a386dcaa2e73730ba50634eaed Both were pub functions with no callers. Clippy doesn't flag dead pub items because the compiler treats them as potentially used by external crates - only private items trigger the dead_code lint. 2026-02-24T11:36:39+00:00 DanConwayDev DanConwayDev@protonmail.com 2026-02-24T11:36:39+00:00 urn:sha1:c31a313ccf781e54fa15942bc882c1b113d3f590 The old name was ambiguous - it wasn't clear whether purgatory was included or not. The two variants are now explicitly named: - fetch_repository_data_excluding_purgatory: DB only - fetch_repository_data_with_purgatory: DB + purgatory overlay SyncContext trait method also renamed to fetch_repository_data_with_purgatory to match the free function it delegates to. 2026-02-24T10:20:55+00:00 DanConwayDev DanConwayDev@protonmail.com 2026-02-24T10:20:55+00:00 urn:sha1:5efdf431a1481f6fb7a17190b62588b81c5b1e65 2026-02-23T15:20:59+00:00 DanConwayDev DanConwayDev@protonmail.com 2026-02-23T15:20:59+00:00 urn:sha1:113928aa84894ea8f65c247d9987527e792b32a9 2026-02-23T12:54:57+00:00 DanConwayDev DanConwayDev@protonmail.com 2026-02-23T12:54:57+00:00 urn:sha1:c3dedb7a5b527c3a3deb1e781aba9d562c6eb294 Per design doc decision #4: when git auth finds a matching state event in purgatory that authorizes a push, extend the announcement's expiry. The repo is actively receiving git data so the announcement should not expire prematurely. Also triggers revival of soft-expired announcements. 2026-02-13T17:29:23+00:00 DanConwayDev DanConwayDev@protonmail.com 2026-02-13T13:24:46+00:00 urn:sha1:1d09e4bdea7e328cf2740818df9df660c5532a99 Route new announcements to purgatory instead of accepting immediately. Announcements are promoted to the database when git data arrives, ensuring we only serve announcements for repos with actual content. Implemented: - AnnouncementPurgatoryEntry type and DashMap store - Route new announcements to purgatory (replacement announcements skip) - Promote announcements on git data arrival (process_purgatory_announcements) - Authorization checks purgatory announcements (fetch_repository_data_with_purgatory) - State policy uses purgatory announcements for maintainer validation - Cleanup task handles announcement expiry - Updated count()/cleanup() to 3-tuples Known broken: - test_archive_read_only_creates_bare_repo fails: sync module does not treat purgatory announcements as confirmed repos, so per-repo sync (state events, PRs) is never triggered for purgatory announcements - Announcement persistence (save/restore) not implemented - SyncLevel (StateOnly vs Full) not implemented - Soft expiry two-phase not implemented - Expiry extension on state event / git auth not wired up 2026-02-03T21:41:19+00:00 DanConwayDev DanConwayDev@protonmail.com 2026-02-03T21:21:33+00:00 urn:sha1:d392f0bc14bcd687e918d4653ae016226496b4c4 Improves observability when pushes are rejected due to state events that only partially match the pushed refs. Previously, logs only showed 'No state event found' even when state events existed but didn't match. Changes: - Add diagnose_state_mismatch() to explain why state events don't match - Log specific reasons: missing refs, wrong SHAs, or extra refs - Update rejection message to 'No matching state event found' (more accurate) - Add 4 unit tests for diagnostic function Example diagnostic output: WARN State event abc123 from authorized author doesn't match push: refs/heads/main missing (state declares 9cc3d93b) This addresses the issue where a push with only refs/heads/test was rejected because the state event also declared refs/heads/main, but logs didn't explain why the match failed. 2026-02-03T17:05:16+00:00 DanConwayDev DanConwayDev@protonmail.com 2026-02-03T16:13:59+00:00 urn:sha1:c163d717147b92b16d89da2fbccef775647b5a07 Fixes race condition where user's push becomes no-op after state event is applied between fetch and push. Now accepts these as successful no-ops, matching Git's 'Everything up-to-date' behavior. - Add early detection in get_state_authorization_for_specific_owner_repo - Return success for all-noop pushes without requiring purgatory event - Document behavior in inline-authorization.md 2026-01-08T11:23:28+00:00 DanConwayDev DanConwayDev@protonmail.com 2026-01-08T11:20:35+00:00 urn: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 2026-01-08T00:50:54+00:00 DanConwayDev DanConwayDev@protonmail.com 2026-01-08T00:50:54+00:00 urn:sha1:f75e1c59aacf5ce668fd327e4e3d827511661c2a