HolyOrders

lightweight tag b261e6d2f9186d8197344a06fb80ed40c310dfd1 v0.29.0
Author:    Klopfer Hello <forkent@icloud.com>
Date:    Sat Jul 25 13:30:18 2026 +0200

commit b261e6d2f9186d8197344a06fb80ed40c310dfd1
Author: Klopfer Hello <forkent@icloud.com>
Date:   Sat Jul 25 13:30:18 2026 +0200

    chore: release v0.29.0

    Co-Authored-By: Claude Fable 5 (1M context) <noreply@anthropic.com>

commit e382bfd669b3f8dbf96cebdffa51291e3f7cccfe
Author: Klopfer Hello <forkent@icloud.com>
Date:   Sat Jul 25 13:30:17 2026 +0200

    docs: add anonymized ui screenshots to the readme

    Co-Authored-By: Claude Fable 5 (1M context) <noreply@anthropic.com>

commit 224e8a7f6b51c545098636cef41ba6bbc0a924c0
Author: Klopfer Hello <forkent@icloud.com>
Date:   Sat Jul 25 12:55:15 2026 +0200

    feat(comm): allow editing rows of paladins without the addon

    Rows of paladins who run no HolyOrders (a legacy blessing addon, or
    nothing) were locked behind lead/assist even though the owner has no
    consent flag to honor and no receiving client of ours to convince —
    which blocked exactly the coordinator scenario the legacy push exists
    for. Such rows are now freely editable: they are a local plan plus, at
    most, a legacy push, and the legacy client enforces its own acceptance
    rule (lead/assist or its free-assignment option) regardless of what we
    gate locally. Rows of HolyOrders peers keep the raid rules: lead/assist
    or the owner's open-edit.

    Co-Authored-By: Claude Fable 5 (1M context) <noreply@anthropic.com>

commit 97b4ad31d9f3c9b9d3134349bf9db3bb6e3d3f4c
Author: Klopfer Hello <forkent@icloud.com>
Date:   Sat Jul 25 12:52:42 2026 +0200

    chore: silence retail-only deprecation warnings in luals

    Co-Authored-By: Claude Fable 5 (1M context) <noreply@anthropic.com>

commit cc6320e6a14607ab6ead5effcb1fe15f706768f6
Author: Klopfer Hello <forkent@icloud.com>
Date:   Sat Jul 25 12:52:42 2026 +0200

    feat: party-scope permissions and an explicit not-a-tank mark

    In a 5-man party (never in raids) every member may now flag tanks and
    edit any paladin's assignments: parties have no assist rank, and
    coordination among five people must not hang on the lead or on consent
    flags. Receivers mirror the same rule, so this fully applies once every
    client runs this version.

    Tank toggling now flips the EFFECTIVE state and stores it explicitly in
    both directions: unmarking someone who is tank-by-role-icon or
    tank-by-spec records a suppression that overrides those derived sources
    — previously such a tank could not be unmarked at all (reported as a
    warrior with Salvation assigned never appearing on the cast bar). The
    suppression syncs live and travels in plan snapshots as a prefixed
    entry; old clients ignore it harmlessly. /ho plan show lists explicit
    non-tanks separately.

    Co-Authored-By: Claude Fable 5 (1M context) <noreply@anthropic.com>

commit e49c52901b9e3315c84096e9fce6ead90814681d
Author: Klopfer Hello <forkent@icloud.com>
Date:   Sat Jul 25 12:52:23 2026 +0200

    feat(plan): keep the cast mode when switching a cell's blessing

    Picking another blessing for a class cell silently reset a deliberately
    chosen always-greater/always-normal mode back to auto. A plain blessing
    switch (no mode given) now inherits the cell's existing mode; explicit
    mode arguments and the mode cycle behave as before.

    Co-Authored-By: Claude Fable 5 (1M context) <noreply@anthropic.com>