Calendar Maintenance Follows Successful Closure

Context

Future calendar availability is related maintenance, but the current task places it after the completed monthly decision.

Decision

Generate until three open years start after the closed month. A Books validation refusal stops the loop; other failure can settle the job failed while the close remains successful.

Alternatives Considered

Generate the calendar before committing closure. A maintenance failure would then keep an otherwise ready month from completing.

Commit all generated years with one output. The inspected implementation chooses separate Books calls; no cited decision establishes why a single transaction was rejected.

Consequences

The run can report success while its job later fails. Committed generated years can precede a missing maintenance output, and replay recalculates the remaining need. A subsequent close can replenish the calendar again.