Artifact Description [5247259be2]

Artifact 5247259be2586237e47070fb9f0e0ed923f0f7451c290bcdea27a4f82b00c874:

• File docs/site/content/docs/concepts/horizons.md
  • 2026-10-24 05:21:29 — part of check-in [5b43d4fe38] on branch feat/horizon-dfloor-receive — Merge feat/471-seed-refusal into feat/seed-receive-drop

    Takes feat/471's no-delete model: a refused seed stays stored, refused by its hash, and is never linked or served. Its effect on the receive side:

    - A seed a pull or clone can read on arrival is still never stored. - One completed in a later round is refused by the link step and kept, inert, rather than swept. The clone's sweep is gone. - Refusing a seed at the link step takes it out of unclustered, as a push-side refusal does. - A dropped seed's phantom row stays inert, since deleting it would free its rid under a receive pass. loadDBPhantoms skips refused hashes, so it is never asked for again. - The client's addPhantom filter is gone: a refused hash always has a row by then. - The handler keeps feat/471's recordStored, which refuses a re-push whose row is already held.

    A test now pins the client's verified-delta refusal (a seed sent as a delta on a held basis), and seeds dropped on receipt are asserted not stored (assertDropped). (user: [email protected], size: 15762) [annotate] [blame] [check-ins using]

  • 2026-10-24 05:21:29 — part of check-in [5b43d4fe38] on branch feat/horizon-dfloor-receive — Merge feat/471-seed-refusal into feat/seed-receive-drop

    Takes feat/471's no-delete model: a refused seed stays stored, refused by its hash, and is never linked or served. Its effect on the receive side:

    - A seed a pull or clone can read on arrival is still never stored. - One completed in a later round is refused by the link step and kept, inert, rather than swept. The clone's sweep is gone. - Refusing a seed at the link step takes it out of unclustered, as a push-side refusal does. - A dropped seed's phantom row stays inert, since deleting it would free its rid under a receive pass. loadDBPhantoms skips refused hashes, so it is never asked for again. - The client's addPhantom filter is gone: a refused hash always has a row by then. - The handler keeps feat/471's recordStored, which refuses a re-push whose row is already held.

    A test now pins the client's verified-delta refusal (a seed sent as a delta on a held basis), and seeds dropped on receipt are asserted not stored (assertDropped). (user: [email protected], size: 15762) [annotate] [blame] [check-ins using]