Owner review 6 asks Chronos to recognise the same time-lapse held under different ids on the server and on this PC, compare the copies, and keep them apart or integrate and sync them. This lays the shared foundation the later parcels build on, without any UI or detection yet. - Migration 0012 adds found_copies (local-server and local-local pairs with evidence, scores, answer, policy and the 404 record) and copy_probes; every existing link with a local sequence becomes a Linked pair, so a server deletion and the per-link policy have a place. - FoundCopyStore keeps the pairs: upserts that never touch the answer, a compare-and-set of the state with an Integrating backstop (a failed or cancelled job reads as the previous state), link promotion and demotion, the once-per-refresh 404 count, the merge's links stage (session keys, links reset, pairs moved, refused when both are linked on one server), the local overlap queries and the probes. SyncLinkStore.RekeyAsync moves pairs and probes with the links in the same transaction. - Contracts for detection, review, plans, the Integrate and MergeSequences jobs (kinds 25/26, High level, new detail steps) and the Upload all rule that keeps suspected, kept-apart, deleted, busy and server-born sequences here. - Wire: POST photos/lookup, uploads into a target (IntoTarget/Copied, trailing and optional), frames/delete on the client, capabilities photo-lookup and upload-into, cached per remote. - The trash plans and deletes accept the job that holds the sequence (its own hold is not Busy) and a frames version checked under the lease; a Background job never interrupts a running one. - Settings for linking, the photo policy and projects; the en and it keys of design section 9. Refs #73 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
37 lines
2.0 KiB
C#
37 lines
2.0 KiB
C#
namespace Chronos.Protocol;
|
|
|
|
/// <summary>
|
|
/// One local sequence's sample for <c>POST /api/v1/photos/lookup</c> (owner review 6, #73): up to 64 SHA-256 (lower-case
|
|
/// hex), up to 64 unhashed photos, and its back-reference key.
|
|
/// </summary>
|
|
public sealed record PhotoProbe(string Key, IReadOnlyList<string> Sha256, IReadOnlyList<PhotoKeyDto>? Unhashed = null, string? SessionKey = null);
|
|
|
|
/// <summary>An unhashed photo, told apart by size and capture time to the millisecond.</summary>
|
|
public sealed record PhotoKeyDto(long Size, DateTime CapturedAt);
|
|
|
|
/// <summary>At most 200 probes and 20,000 items (hashes + unhashed keys + session keys) in all; 413 <c>too_many</c> beyond.</summary>
|
|
public sealed record PhotoLookupRequest(IReadOnlyList<PhotoProbe> Probes)
|
|
{
|
|
/// <summary>The most probes one request may carry.</summary>
|
|
public const int MaxProbes = 200;
|
|
|
|
/// <summary>The most items (hashes, unhashed keys and session keys) one request may carry.</summary>
|
|
public const int MaxItems = 20_000;
|
|
|
|
/// <summary>The items the request carries, as the limit counts them.</summary>
|
|
public int CountItems() => Probes.Sum(p => (p.Sha256?.Count ?? 0) + (p.Unhashed?.Count ?? 0) + (p.SessionKey is null ? 0 : 1));
|
|
}
|
|
|
|
/// <summary>The answer of a lookup: one result per probe, in the request's order.</summary>
|
|
public sealed record PhotoLookupResponse(IReadOnlyList<ProbeResult> Results);
|
|
|
|
/// <summary>The server sequences a probe hit.</summary>
|
|
public sealed record ProbeResult(string Key, IReadOnlyList<PhotoLookupHit> Hits);
|
|
|
|
/// <summary>
|
|
/// Hashes: distinct probe hashes the sequence holds in a frame; Removed: distinct probe hashes it tombstoned (deleted, or
|
|
/// replaced by a conversion); Unhashed: probe keys a frame of it matches by size and capture time to the millisecond;
|
|
/// SessionKey: the sequence is filed under the probe's session key.
|
|
/// </summary>
|
|
public sealed record PhotoLookupHit(Guid SequenceId, int Hashes, int Removed, int Unhashed, bool SessionKey);
|