Skip to content

MEMBERS-CANCEL-001A — Record approved paid-term cancellation policy and expiry regressions #705

Closed

Description

@daliu

Parent: #114. Officer impact: Records the approved membership cancellation rule; no cancellation control becomes available. Officer documentation: OFFICER_START_HERE.md and docs/officers/EVENTS_SHOP_MEMBERS.md. Deployment evidence: Source and local tests only; no website, Firebase, provider, production data or payment change authorized by this child. Dave approved on October 11, 2026: membership cancellation retains access through the already-paid annual term and does not issue a refund. Atomic outcome: versioned backend policy plus regression checks against the existing authority expiry/ownership/suspension boundary. Dependencies: the pure authority contract from merged #208/#451 exists; this child does not runtime-adopt it or depend on unresolved payment/persistence work. Preserve one-time annual dues, no automatic renewal. Do not shorten or extend a paid term, set it ended early, revive suspended/ended membership, grant claims, or call a payment provider. Cancellation metadata and its durable command/ownership/persistence belong to a later child. Acceptance: policy explicitly versioned; exact term end is not entitled; approved linked term remains current just before end; wrong UID, unlinked, suspended/ended and malformed terms fail closed; tests explicitly do not claim a cancellation command executed. No runtime import, dependency, schema migration, Rules, IAM or deployment change. Keep #114 and staging lifecycle acceptance open. Specialist still needed for future endpoints; the officer documentation review needs no terminal or member data.

Activity

  1. self-assigned this
    on Oct 11, 2026
  2. daliu commented on Oct 11, 2026

    @daliu
    ContributorAuthor

    CLAIMED by Codex at 2026-10-11 22:56:16 UTC; branch codex/membership-cancellation-policy. Allowed files: functions/membershipCancellationPolicy.json and its regression test, relevant root policy/design notes, and officer handoff only. No runtime endpoint, grant, provider, data or deployment action.

  3. daliu commented on Oct 11, 2026

    @daliu
    ContributorAuthor

    Completed policy-only scope via PR #706, merged as 6178c48 at 2026-10-11T23:01:42Z. All six exact-head CI jobs passed in 38182483286, including actual frontend behavior/build, Rules, commerce-emulator and Node22 profile-persistence steps. Local focused149/full7609 pass,64 skipped; lint/diff clean. Sole-maintainer repository review override used under prior Dave authorization, explicitly not a deployment approval. Officer read-through is complete: understandable decision, NOT AVAILABLE YET, no manual data workaround; specialist still required for request persistence/UI/staging. No migration or hosted cancellation behavior. Main CI38182719490 currently pending. Website publication/Firebase/provider configuration/production-data/payment action: none performed. Parent #114 remains open.

  4. daliu commented on Oct 11, 2026

    @daliu
    ContributorAuthor

    Exact-main CI38182719490 is now successful at merged 6178c48: all six jobs pass. Policy-only acceptance is complete. No protected release dispatched; signup/cancellation persistence/UI and hosted staging evidence remain unavailable, #114 open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions