4 Commits

Include renames

Author	SHA1	Message	Date
jaredandClaude Opus 4.8	e813ffd3aa	feat: accept corpus schema v6 (FIPS geography harmonization); v6 fixture ... Schema v6 (cog_pipeline 2026-07-22) renamed the long table's fips_state_code/fips_county_code to fips_state_asof/fips_county_asof and added cog_legacy_state/cog_legacy_county (26 -> 28 cols). This package references none of those columns and its geography always came from canonical_fips_xwalk (already present-based), so acceptance is a version-set bump: supported = c(4L, 5L) -> c(4L, 5L, 6L) in .validate_schema() and cog_open(). A prominent note in .validate_schema() documents the SILENT semantic change for raw-long readers: long fips_state/fips_county are now PRESENT/harmonized geography (carried back per government), not as-of-year. Fixture regenerated from the published v6 tree (schema_version 6, 28 cols). Test updates: * test-manifest.R: v6 accepted; boundary rejection moves to v7. * test-spending.R: the na_rows_excluded pin (0) predated the Task 18 map extension, which added E/F/G-prefix discontinued_na rulings (E21/F21/G21, Education NEC local, SB184-186). Broward's 2011 partition zero-pads exactly those codes: 3 NA-harmonized rows excluded, all amt=0, so the excluded AMOUNT pin stays 0. Data-verified against the v6 fixture. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-22 13:16:11 -04:00
jared	7818cd2b1a	feat: basis= harmonized/raw with v4/v5 dual-accept ... Adds schema_version 5 support alongside the existing v4 corpus: .validate_schema() now accepts a supported set (4, 5) instead of a single expected version, and cog_spending()/cog_revenue() gain basis = c("harmonized", "raw"). Harmonized basis routes to new spending_annotated_harmonized / revenue_annotated_harmonized views built on spending_long_harmonized / revenue_long_harmonized (REPLACE(harmonized_code AS item_code), excluding aggregate and NA-harmonized rows); raw basis is byte-identical to the pre-Phase-R2 behavior. On a v4 corpus, an unspecified basis silently resolves to "raw" with a provenance note; an explicit basis = "harmonized" aborts with an actionable message. Provenance gains basis, basis_note, and a harmonization block (applied/na_rows_excluded/na_amount_excluded). The five new schema-v5-only SQL views (harmonized long/annotated views, harmonization_map, harmonization_recipes, series_breaks_pq) are registered conditionally on manifest$schema_version >= 5, since DuckDB's read_parquet() errors eagerly at CREATE VIEW time when the backing file doesn't exist on a v4 corpus. Fixture corpus regenerated to schema_version 5 / years 2011, 2012, 2019, 2020 (2011->2012 spans the wide-aggregate -> modern-leaf format boundary needed for the harmonization/recipe work), with the harmonization_map / harmonization_recipes / series_breaks parquet tables bundled alongside the existing metadata registries.	2026-07-18 23:19:17 -04:00
jared	4d61692f05	feat: export cog_manifest() accessor + pin CPI coverage 1967-present	2026-07-18 13:40:54 -04:00
jared	874347242b	fix(manifest): actionable errors when USCOGDATA_URL is unset or returns non-JSON ... `cog_gov_search()` (and every other verb) used to fail with a cryptic `jsonlite` lexical error when the package's placeholder default URL was hit and the server returned an HTML welcome page that got cached as `manifest.json`. Three guards added: 1. `.check_url_configured()` aborts with class `uscogdata_url_not_configured` when the resolved URL is empty or still contains the `REPLACE_WITH_SHARE_TOKEN` sentinel. Message names both `Sys.setenv(USCOGDATA_URL = ...)` and `options(uscogdata.url = ...)` remediations and points at the bundled fixture. 2. `.fetch_or_cache_manifest()` parses the response body before persisting it. Non-JSON payloads raise class `uscogdata_invalid_manifest` (URL, Content-Type, parse error) and never touch the on-disk cache. 3. Cache writes are atomic via a sibling tempfile + `file.rename`, and existing caches with non-JSON content are silently refetched instead of returning a parse error to the caller. Local-path manifests that aren't valid JSON now surface the same `uscogdata_invalid_manifest` class with file context.	2026-05-27 11:57:31 -04:00