Tags

Tags give the ability to mark specific points in history as being important
  • v0.2.4

    v0.2.4 - drift --anonymize masks array cardinality
    
    Adds an --anonymize flag to bairn drift that replaces "<n=N>"
    markers with "<n=*>" in shape signatures, so household-side
    cardinality (number of relations, roles) does not leak into
    committed baselines. Default stays unchanged; bairn's drift-gate
    opts in via .gitlab-ci.yml.
    
    Posture and conditions of use unchanged: NOTICE.md.
  • v0.2.3

    v0.2.3 - upsert release behavior via dunn.dev/pipeline@v1.5.2
    
    Bumps the catalog includes to v1.5.2 so release-create upserts
    the release record and asset links on every fire instead of
    skipping when present. Re-tags and duplicate-pipeline-fires now
    converge cleanly.
    
    No binary behavior change beyond version reporting.
    
    Posture and conditions of use unchanged: NOTICE.md.
  • v0.2.2

    v0.2.2 - drift validation hardening
    
    Folds in the validation fix that surfaced while wiring v0.2.1's
    drift-gate end-to-end:
    
    - Validate("drift") now accepts FAMLY_EMAIL+FAMLY_PASSWORD
      (recommended for CI; refreshing token) in addition to the
      static FAMLY_ACCESS_TOKEN. Matches Validate("fetch")'s logic.
    - runDrift now calls Validate("drift") and fails fast when the
      resolved token is empty, with an error message that names the
      protected-variable / protected-ref mismatch as a likely cause.
    
    No behaviour change for the binary's hot path; this lands the
    clearer error messages and the corrected validation gate.
    
    Posture and conditions of use unchanged: NOTICE.md.
  • v0.2.1

    v0.2.1 - drift gate as pre-release verification
    
    Adds a tag-triggered drift gate to bairn's CI: each tag pipeline
    builds bairn, hits Famly's parent-side surface using the operator's
    own refreshing credentials, and diffs response shapes against the
    committed baseline at discovery/baselines/main/. The gate fails
    the tag pipeline (and blocks the binary from shipping) when drift
    is detected.
    
    Companion docs (NOTICE.md, discovery/PROTOCOL.md, ADR 0007) name
    the trigger model explicitly: tag push is a human action; this is
    not a recurring schedule against Famly's surface.
    
    No behaviour change in the binary itself beyond version reporting.
    
    Posture and conditions of use unchanged: NOTICE.md.
  • v0.2.0

    v0.2.0 - native drift detection
    
    bairn drift is now a native Go subcommand. Loads a TOML manifest,
    hits each endpoint with auth + paced delay, computes JSON-key-only
    shape signatures, optionally diffs against a prior baseline.
    Surfaces vendor schema changes before they break a fetch.
    
    Exit codes: 0 = no drift, 1 = drift found, 2 = config or transport
    error. Wires cleanly into the claude-drift-triage component in
    dunn.dev/pipeline so the LLM triage fires only on real changes.
    
    The Python prototype (discovery/probe/shape.py) stays in the repo
    as documentation of the methodology. Signature format is
    byte-compatible.
    
    Posture and conditions of use unchanged: NOTICE.md.
  • v0.1.0

    v0.1.0 - initial release
    
    Personal photo archive for Famly-using households. Pull images and
    videos to disk with full EXIF and XMP metadata embedded. Optional
    Immich upload (alpha; matures in v0.2.0).
    
    Each binary ships with a sha256 checksum, a keyless cosign
    signature, a CycloneDX SBOM, and a SLSA v1.0 provenance
    attestation. Verification recipes in SECURITY.md.
    
    Posture and conditions of use: NOTICE.md.