npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-grasp-mirror/docs, branch v1.0.2Unnamed repository; edit this file 'description' to name the repository.
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-grasp-mirror/atom?h=v1.0.22026-03-25T07:19:26+00:00chore: remove arbitrary default max connections limit2026-03-25T07:19:26+00:00DanConwayDevDanConwayDev@protonmail.com2026-03-25T07:19:26+00:00urn:sha1:28168a7701c897a5b6af13bc472d6f5902e0a96d
When NGIT_MAX_CONNECTIONS is unset the relay imposes no connection cap,
deferring to OS fd limits and infrastructure controls. The option remains
available for operators who want an explicit ceiling.
docs: remove comparison doc and update architecture to reflect announcement purgatory2026-02-25T15:14:46+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-25T15:14:46+00:00urn:sha1:8cd232727ae31613abba7a3d0485a1cb94fda2f3drop nostr-db backend support, keep only lmdb and memory2026-02-25T15:07:40+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-25T15:07:40+00:00urn:sha1:5ad9d9093fcbe7037e5474a9d8fa20a0b64fb79afix migration scripts for non-interactive SSH and bash 5.32026-02-24T08:58:23+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-24T08:58:23+00:00urn:sha1:f62846b2966e0a3ffc93e718bbe44137d01c66b3
01-fetch-events.sh: nak buffers output when stdout is not a TTY, causing
it to hang silently in non-interactive SSH sessions. Wrap with 'script'
to provide a pseudo-TTY, then strip the injected carriage returns and
connection banner line from the output.
40-classify-actions.sh: bash 5.3 treats ${#assoc[@]} and array iteration
as unbound variable errors under set -u when arrays are empty. Replace
${#assoc[@]} with explicit counters and guard array iterations with
set +u/set -u.
Merge master into 3ca0-announcements-purgatory2026-02-23T15:20:59+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-23T15:20:59+00:00urn:sha1:113928aa84894ea8f65c247d9987527e792b32a9persist and restore announcement events across graceful restarts2026-02-23T15:08:37+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-23T15:08:37+00:00urn:sha1:26f608e5011b9d1ad6036da75b89272835e69695
Extends purgatory persistence to include announcement purgatory entries.
On graceful shutdown, non-soft-expired announcements are serialised to
purgatory-state.json alongside state/PR/expired events; on startup they
are restored, skipping any entry whose bare repo path no longer exists.
Updates purgatory-design.md to reflect that purgatory persists through
graceful shutdown and documents the new PurgatoryState disk format.
Adds create_announcement_event helper to purgatory_helpers and three new
integration tests in purgatory_persistence covering the full save/restore
cycle, missing-repo skip, and the combined roundtrip with all entry types.
docs: update purgatory docs to reflect announcements purgatory implementation2026-02-23T14:49:30+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-23T14:49:30+00:00urn:sha1:4848c4029fc58f6f310a2babeae1ee82a7e41656
Remove the pre-implementation planning docs (announcements-purgatory-design.md
and announcements-purgatory-implementation.md) now that the feature is built.
Update the three living docs to reflect what was actually implemented:
- purgatory-design.md: expanded to cover all three purgatory stores
(announcement, state, PR), including AnnouncementPurgatoryEntry structure,
two-phase soft expiry lifecycle, expiry extension triggers, promotion flow,
and updated integration points and file structure
- grasp-02-proactive-sync.md: added SyncLevel enum (Full/StateOnly) to
RepoSyncNeeds, documented the purgatory announcement sync timer as the
registration path for purgatory announcements, updated filter building
to describe build_sync_level_aware_filters() and StateOnly behaviour
- grasp-02-proactive-sync-purgatory-git-data.md: expanded to cover
announcement purgatory as a third entry type, added Timeline E showing
soft-expiry and revival, replaced the single expiry section with separate
hard-expiry (state/PR) and two-phase soft-expiry (announcements) sections
with full justification for the 24-hour extended retention window
docs: annocunment purgatory clarify soft expiry rationale2026-02-12T09:11:38+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-12T09:11:38+00:00urn:sha1:0a1908bd6ee19f7079bb2914c0009bea1fc1db37
now we have added announcement purgatory to the protocol spec
docs: complete high-level announcements purgatory design2026-02-05T17:03:37+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-05T17:03:37+00:00urn:sha1:603c87fabda70145b967579b9338051ea9f00704
- Integrate sync-only-state-events decision (SyncLevel concept)
- Add authorization must check purgatory decision
- Add soft expiry design (delete repo, retain event for 24h)
- Add purgatory lifecycle diagram
- Create separate implementation details document
- Remove inline questions (now resolved)
add notes to announcment purgatory design2026-02-05T15:25:14+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-05T15:25:14+00:00urn:sha1:854484813dfe45f882fe66ff866621f9a21186fe