btctax_cli/lib.rs
1//! btctax-cli: the CLI + reconciliation library that wires the encrypted vault (btctax-store),
2//! ingest (btctax-adapters), and the pure projection (btctax-core) into the Phase-1 command surface
3//! (spec §11). The library is I/O-explicit and deterministic; the binary (`main.rs`) is a thin clap
4//! dispatch. PRIVACY: tests use only temp vaults + synthetic fixtures; no real user file is ever read.
5pub mod bulk_estimated;
6pub mod cli;
7pub mod cmd;
8pub mod config;
9pub mod donation_details;
10pub mod eventref;
11pub mod input_form_store;
12pub mod optimize_attest;
13pub mod price_cache;
14pub mod render;
15pub mod resolve;
16pub mod return_inputs;
17pub mod session;
18pub mod tax_profile;
19pub mod testonly;
20
21pub use cli::Cli;
22// Re-exported at the crate root so the TUI editor (`btctax-tui-edit`) can call it WITHOUT the `cmd::`
23// token its KAT-G1 source gate forbids in non-test code. That gate exists to keep session-lifecycle /
24// lock-holding `cmd::` fns out of the held-session editor; `guard_allocation_vs_tranche` is a PURE
25// `&[LedgerEvent] -> Result` predicate — no `Session`, no lock, no I/O — so the gate's intent is honored,
26// not evaded. Any FUTURE addition here must be equally pure (do NOT re-export a session-opening fn).
27pub use cmd::tranche::guard_allocation_vs_tranche;
28pub use config::CliConfig;
29pub use session::{
30 BulkFilter, BulkIncomeFilter, BulkIncomePlan, BulkIncomeRow, BulkLinkPlan, BulkLinkRow,
31 BulkReclassifyOutflowPlan, BulkReclassifyOutflowRow, BulkResolvePlan, BulkResolveRow,
32 BulkStiFilter, BulkStiPlan, BulkStiRow, BulkVoidPlan, BulkVoidRow, Frame, MatchAction,
33 MatchProposal, Session,
34};
35
36#[derive(Debug, thiserror::Error)]
37pub enum CliError {
38 #[error(transparent)]
39 Store(#[from] btctax_store::StoreError),
40 #[error(transparent)]
41 Core(#[from] btctax_core::CoreError),
42 #[error(transparent)]
43 Adapter(#[from] btctax_adapters::AdapterError),
44 #[error("sqlite: {0}")]
45 Sqlite(#[from] rusqlite::Error),
46 /// C1: `write_csv_exports` (Task 15) uses `?` on `csv::Writer` ops (→ `csv::Error`); `csv::Error`
47 /// is its own type (NOT covered by `Io(#[from] io::Error)`, whose `From` goes the other way), so it
48 /// needs its own variant or Task 15 will not compile.
49 #[error("csv: {0}")]
50 Csv(#[from] csv::Error),
51 #[error("io: {0}")]
52 Io(#[from] std::io::Error),
53 /// `export-irs-pdf`: an official IRS PDF fill failed — most importantly the geometric read-back
54 /// FAILING CLOSED on a mis-mapped cell, so no wrong tax form is ever written.
55 #[error("IRS form fill: {0}")]
56 FormFill(#[from] btctax_forms::FormsError),
57 /// A user-supplied event reference did not parse as a canonical `EventId` (eventref.rs).
58 #[error("not a valid event reference: {0:?}")]
59 BadEventRef(String),
60 /// A CLI argument was malformed (bad USD/date/enum/wallet spec, or a contradictory flag set).
61 #[error("usage: {0}")]
62 Usage(String),
63 /// M1: a `cli_config` row held an unrecognized value (corrupt DB, future-written value, or manual
64 /// edit gone wrong). Returning an error is safer than silently misreading the stored intent.
65 #[error("unrecognized stored config value: key={key:?} value={value:?}")]
66 BadConfigValue { key: String, value: String },
67 /// P9 §2.6: a stored `return_inputs` row predates the form-question registry (or was written by a newer
68 /// build) and this build does not migrate it. There is no user data yet, so the policy is refuse-and-
69 /// reimport rather than a per-key migration (a version check cannot forget a key). The remedy names all
70 /// THREE commands, in order — `clear` DISCARDS any computed carryover this row's prior reports wrote onto
71 /// it, so the rebuild step is not optional. (Retire this the moment real data exists — FOLLOWUPS, release
72 /// gate.)
73 #[error(
74 "the stored inputs for {year} predate the form-question registry (schema v{found}; this build reads \
75 v{expected}). Run `btctax income clear {year}` — which DISCARDS any carryover this row's prior \
76 reports computed onto it — then `btctax income import` for {year}; then, if this row carried a \
77 computed carryover, `btctax report --tax-year {prior} --write-carryover` to rebuild it.",
78 prior = year - 1
79 )]
80 StaleReturnInputs {
81 year: i32,
82 found: i64,
83 expected: i64,
84 },
85 /// §6.3 / C-1: a PARKED input-form draft is at a schema version this build does not read, and this
86 /// build does not migrate it. Unlike a stale WIP draft (regenerable → discarded), a parked draft may
87 /// hold irreplaceable carryover that exists ONLY in the draft — there is no committed row to re-import
88 /// from — so we REFUSE (fail closed) rather than discard. The remedy therefore is NOT `income import`
89 /// (that recovers a WIP row from committed state, which a parked draft has none of): the message must
90 /// tell the filer the data lives in the draft, must not be discarded, and to re-run on / export from the
91 /// app version that wrote it. (Retire alongside `StaleReturnInputs` the moment migrations exist.)
92 #[error(
93 "year {year}'s parked full return is schema v{found} but this build expects v{expected}; \
94 an upgrade changed the input format. Its data lives only in the draft — do not discard it. \
95 Re-run on the app version that wrote it, or export it there first."
96 )]
97 StaleParkedDraft {
98 year: i32,
99 found: i64,
100 expected: i64,
101 },
102 /// §6.2 draft-coherence: an authoritative committed-row write (`income import` / `income answer` /
103 /// carryover write-back / `income clear`) was attempted for a year whose input-form draft is PARKED.
104 /// A parked draft is the SOLE copy of a screened return (C-1) — clobbering it via the committed row
105 /// would silently destroy irreplaceable data — so the write is REFUSED (fail closed). The message
106 /// names BOTH in-form exits (M-d): re-commit it (`use full return`) or drop it (`discard parked
107 /// draft`, a confirmed delete); a WIP draft, by contrast, is regenerable and is cleared silently.
108 #[error(
109 "year {year} holds a parked full return — in the form, 'use full return' to re-commit it, or \
110 'discard parked draft' (a confirmed delete) to drop it; then re-run this command."
111 )]
112 ParkedDraftBlocksWrite { year: i32 },
113 /// Sub-project 3 attestation gate: an export was attempted while the ledger is pseudo-reconciled
114 /// (a synthetic, non-persisted default contributes to the projection) and NO attestation phrase was
115 /// supplied. Producing a form/data file from a fictional draft requires typing the exact phrase.
116 /// (Supersedes sub-2's interim [I3] blanket refusal.)
117 #[error(
118 "export refused: the ledger is pseudo-reconciled (a synthetic default contributes to the \
119 projection). To export this draft ON PURPOSE, attest the exact phrase {:?} (pass --attest, or \
120 type it at the prompt). Otherwise run `reconcile pseudo off` (or approve + attest the defaults).",
121 ATTEST_PHRASE
122 )]
123 AttestationRequired,
124 /// Sub-project 3 attestation gate: an export was attempted while the ledger is pseudo-reconciled and
125 /// the supplied attestation phrase did NOT match (trimmed, case-sensitive, exact). A wrong phrase is
126 /// FAILED regardless of environment [R0-I1] — no fictional form leaves the machine.
127 #[error(
128 "export refused: the attestation phrase did not match. The ledger is pseudo-reconciled; type the \
129 phrase EXACTLY (trimmed, case-sensitive): {:?}.",
130 ATTEST_PHRASE
131 )]
132 AttestationFailed,
133 /// UX-P4-8: an I/O failure at a user-named path — a `--vault` that is missing/unreadable, or an
134 /// `--out` that collides / cannot be created. Carries the offending PATH and a one-clause remedy
135 /// hint that the bare `io::Error` (surfaced pathlessly through `Store::Io` / `Io`) lacks. Mirrors
136 /// the adapters' `AdapterError::Io { path, source }` so every path-bearing io error reads alike.
137 #[error("io {path}: {source} ({hint})")]
138 PathIo {
139 path: String,
140 hint: String,
141 #[source]
142 source: std::io::Error,
143 },
144}
145
146/// UX-P4-8 hint: shown when a `--vault` cannot be opened (missing/unreadable path).
147pub const VAULT_OPEN_HINT: &str =
148 "check the --vault path, or run `btctax init` to create a new vault";
149
150/// UX-P4-8 hint: shown when an export `--out` directory cannot be created (a colliding file, a
151/// missing parent, or a permission problem).
152pub const EXPORT_OUT_HINT: &str =
153 "choose an --out path that does not already exist as a file and whose parent is writable";
154
155/// Re-wrap a `StoreError` I/O failure with the offending PATH + a one-clause hint (UX-P4-8). ONLY the
156/// pathless `StoreError::Io` is enriched; every other variant (`WrongPassphrase`, `Locked`,
157/// `HalfCreatedVault`, …) passes through unchanged — each already carries its own precise meaning and
158/// must NOT be masked behind a generic path/hint.
159pub fn store_io_with_path(
160 e: btctax_store::StoreError,
161 path: &std::path::Path,
162 hint: &str,
163) -> CliError {
164 match e {
165 btctax_store::StoreError::Io(source) => CliError::PathIo {
166 path: path.display().to_string(),
167 hint: hint.to_string(),
168 source,
169 },
170 other => CliError::Store(other),
171 }
172}
173
174/// Re-wrap a pathless I/O failure with the offending PATH + a one-clause hint (UX-P4-8). Enriches
175/// BOTH shapes an export write can produce: a raw `CliError::Io` (a `write`/`flush` mid-write) AND a
176/// `CliError::Store(StoreError::Io)` (a `mkdir_owner_only`/`open_owner_only` under `out_dir` — e.g. a
177/// SUBPATH collision like `out_dir/lots.csv` already existing as a directory, which `?`-converts
178/// through `From<StoreError>`). A `CliError::Csv` (a serialization error, not a path problem) and
179/// every other variant pass through unchanged.
180pub fn cli_io_with_path(e: CliError, path: &std::path::Path, hint: &str) -> CliError {
181 match e {
182 CliError::Io(source) | CliError::Store(btctax_store::StoreError::Io(source)) => {
183 CliError::PathIo {
184 path: path.display().to_string(),
185 hint: hint.to_string(),
186 source,
187 }
188 }
189 other => other,
190 }
191}
192
193/// The exact phrase a user must affirm to export a form/data file while the ledger is pseudo-reconciled
194/// (sub-project 3). Compared TRIMMED, case-SENSITIVE, exact. The prompt + both error strings are BUILT
195/// from this constant [R0-M1] so there is no drift (a KAT asserts they contain it). `pub` so btctax-tui
196/// shares it [R0-r2-N2].
197pub const ATTEST_PHRASE: &str = "I attest this is true";
198
199/// PURE exact-compare attestation gate — NO I/O, NO TTY read [R0-I2]. The interactive prompt lives in
200/// the caller (the `export-snapshot` main.rs arm / the btctax-tui export modal); this helper only
201/// compares, keeping the library I/O-explicit and the KATs deterministic (no env-dependent branch).
202///
203/// - `attest.map(str::trim) == Some(ATTEST_PHRASE)` → `Ok(())`.
204/// - `Some(_)` non-matching → `Err(AttestationFailed)` (a wrong phrase FAILS regardless of env) [R0-I1].
205/// - `None` → `Err(AttestationRequired)`.
206///
207/// `pub` so btctax-tui shares the exact-compare [R0-r2-N2].
208pub fn require_attestation(attest: Option<&str>) -> Result<(), CliError> {
209 match attest.map(str::trim) {
210 Some(p) if p == ATTEST_PHRASE => Ok(()),
211 Some(_) => Err(CliError::AttestationFailed),
212 None => Err(CliError::AttestationRequired),
213 }
214}