US 26-zone power system w/ servers

[SutubraResearch]

Summary by CodeRabbit

• Chores
  • Added two new SQLite database artifacts (usp_26z_base and usp_26z_serverdemand) to the manifest with version tracking and metadata.

[coderabbitai]

📝 Walkthrough

Walkthrough

Two new SQLite database artifacts (usp_26z_base.sqlite and usp_26z_serverdemand.sqlite) were added to the manifest with version v1, including storage keys, checksums, and metadata entries marked as pending merge.

Changes

Cohort / File(s)	Summary
Manifest Updates manifest.json	Added two new SQLite artifact entries with version v1, including history records with R2 object keys, staging keys, SHA256 checksums, and pending-merge status.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Two databases hopping into place,
Registered with version's grace,
Base and demand, now side by side,
In manifest they softly glide,
Pending merge with whispered care,
New artifacts beyond compare! 📦✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'US 26-zone power system w/ servers' directly relates to the changeset, which adds SQLite artifacts (usp_26z_base.sqlite and usp_26z_serverdemand.sqlite) for a US 26-zone power system with servers.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch us-26z-powersys-servers

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

manifest.json (1)

39-53: Add manifest schema validation for new artifact fields

These new objects are structurally good, but the current loader only validates JSON syntax, not required keys/value formats. Consider validating required fields (version, sha256, r2_object_key, staging_key, etc.) at read/update boundaries to catch malformed entries early (src/datamanager/manifest.py:31-50, 123-156).

Also applies to: 56-70

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@manifest.json` around lines 39 - 53, Add explicit manifest-schema validation
in the manifest loader/updater: implement a validation function (e.g.,
validate_manifest_entry or a Pydantic model/JSON Schema) and call it from the
manifest read and update paths (the functions around src/datamanager/manifest.py
lines referenced, e.g., load_manifest and update_manifest). The validator should
enforce presence and types/formats for required fields (version, timestamp,
sha256, r2_object_key, staging_key, commit, description and history entries),
validate sha256 hex length, ISO8601 timestamp format, and non-empty strings for
object keys; return or raise a clear error on failure so malformed entries are
rejected before persisting or further processing. Ensure both read and update
code paths use this single validation routine so all boundaries are covered.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@manifest.json`:
- Around line 49-51: Replace the placeholder provenance fields in manifest.json
so they don't ship as "pending-merge": set the "commit" value to the real git
commit hash (or populate it during your build/release step), replace
"description" with the final human-readable description, and ensure
"temoaRepoHash" is set or null intentionally; update both occurrences (the one
at lines around the shown diff and the second occurrence noted at 66-68). Locate
the fields "commit", "description", and "temoaRepoHash" in manifest.json and
either hardcode the final values before merge or wire them to whatever
build-time generator you use (so src/datamanager/__main__.py:142-182 will
display correct provenance).

---

Nitpick comments:
In `@manifest.json`:
- Around line 39-53: Add explicit manifest-schema validation in the manifest
loader/updater: implement a validation function (e.g., validate_manifest_entry
or a Pydantic model/JSON Schema) and call it from the manifest read and update
paths (the functions around src/datamanager/manifest.py lines referenced, e.g.,
load_manifest and update_manifest). The validator should enforce presence and
types/formats for required fields (version, timestamp, sha256, r2_object_key,
staging_key, commit, description and history entries), validate sha256 hex
length, ISO8601 timestamp format, and non-empty strings for object keys; return
or raise a clear error on failure so malformed entries are rejected before
persisting or further processing. Ensure both read and update code paths use
this single validation routine so all boundaries are covered.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2e2b5a86-9212-4e2c-84a4-b44d9f4081f7

📥 Commits

Reviewing files that changed from the base of the PR and between b655e63 and 739f4f9.

📒 Files selected for processing (1)

• manifest.json