jacobh2
50a0d6792a
Build Kvitt images / build (push) Failing after 1m20s
Part A (D-132): KVITT_WEB_DIR (default /app) served under /app/ by a small handler: /app redirects to /app/, app routes fall back to index.html, a missing assets/* file is 404, assets cached immutable, index.html no-store, the app's own CSP plus nosniff, DENY and no-referrer. Unsafe paths never reach the file system. /app paths count against the unauthenticated per-IP limit. Without the directory every /app path stays 404 not_found. server/Dockerfile gains a Node 24 LTS stage (pinned by digest) building web/, passed through the Rust stage so npm and rustc never run at once on the Pi 3; the build context is the repository root with an allowlist .dockerignore (server/.dockerignore removed); workflow, build-images.sh and infra/dev/build.sh follow. Part B (D-133): GET /analytics/trends (E-34) and GET /analytics/forecast (E-35), authenticated, read-only, SQL month buckets; rules (half-up average, trailing 3-month moving average, percent against the rounded average, template occurrence per month) in kvitt-domain::analytics. OpenAPI, examples, contracts-check and tests updated (35 operations). Cargo.lock: rustls-webpki 0.103.16 and webpki-root-certs 1.0.10 (RUSTSEC-2026-0382, -0383) so that cargo audit passes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TQd3pEP9UeN2uifbHknQ7B
46 lines
1.9 KiB
Rust
46 lines
1.9 KiB
Rust
//! Kvitt domain rules as pure functions (SPEC §9.1, §9.3, §9.4, §9.5 `next_occurrence_date`, §14.5, and the
|
|
//! server-side analytics rules of §14.5.7).
|
|
//!
|
|
//! No I/O, no clock, no randomness, no locale. Ids are plain strings (the test vectors use short ids like `"a"`);
|
|
//! money is `i64` öre and basis points are `u32`. The Kotlin `:domain` module implements the same functions and both
|
|
//! must pass every vector in `contracts/test-vectors/` (`tests/vectors.rs`).
|
|
|
|
// No unwrap/expect outside tests (CLAUDE.md server rule); integration tests are separate crates and may use them.
|
|
#![cfg_attr(not(test), deny(clippy::unwrap_used, clippy::expect_used))]
|
|
|
|
mod allocation;
|
|
mod analytics;
|
|
mod balance;
|
|
mod recurring;
|
|
mod settlement;
|
|
mod split;
|
|
|
|
pub use allocation::{
|
|
AccountPosition, Allocation, AllocationError, AllocationProposal, over_settled_accounts,
|
|
propose_allocation,
|
|
};
|
|
pub use analytics::{
|
|
MOVING_AVERAGE_WINDOW, average, div_half_up, moving_average, occurs_in_period,
|
|
percent_vs_average,
|
|
};
|
|
pub use balance::{BalanceExpense, BalanceSettlement, Balances, compute_balances};
|
|
pub use recurring::{
|
|
Period, RecurrenceError, RecurrenceSchedule, next_candidate_period, next_occurrence_date,
|
|
};
|
|
pub use settlement::{SettlementError, validate_settlement};
|
|
pub use split::{SplitError, SplitSpec, compute_split};
|
|
|
|
/// Smallest valid amount of an expense, settlement or template, in öre (SPEC §9.6).
|
|
pub const AMOUNT_MIN_ORE: i64 = 1;
|
|
/// Largest valid amount of an expense, settlement or template, in öre: 10 000 000,00 kr (SPEC §9.6).
|
|
pub const AMOUNT_MAX_ORE: i64 = 1_000_000_000;
|
|
/// 100 % in basis points.
|
|
pub const BP_TOTAL: u32 = 10_000;
|
|
/// Most allocations one settlement may have (SPEC §9.6).
|
|
pub const MAX_ALLOCATIONS: usize = 50;
|
|
|
|
/// Whether `amount_ore` is within SPEC §9.6 (1 to 1 000 000 000).
|
|
pub fn amount_in_range(amount_ore: i64) -> bool {
|
|
(AMOUNT_MIN_ORE..=AMOUNT_MAX_ORE).contains(&amount_ore)
|
|
}
|