Skip to content

chore: sync Smite 2 content - #83

Merged
diese-tech merged 3 commits into
mainfrom
automation/smite-content-sync
Sep 1, 2026
Merged

chore: sync Smite 2 content#83
diese-tech merged 3 commits into
mainfrom
automation/smite-content-sync

Conversation

@diese-tech

@diese-tech diese-tech commented Aug 4, 2026

Copy link
Copy Markdown
Owner

Smite 2 Content Sync Report

Generated: 2026-08-17T13:52:49.417Z

Summary

Metric Gods Items
Discovered 89 263
Canonical before 88 265
Canonical after 89 265
Added 1 0
Updated 0 0
Source URL normalized 0 0
Unchanged 88 263
Missing from source 0 2
Conflicting/unresolved 0 0
Gods: 1 added, 0 content changes, 0 source URL normalized
Items: 0 added, 0 content changes, 0 source URL normalized, 2 missing from source

Gods

Added

  • Ix Chel (ix-chel)

Items

Missing from source

Preserved in canonical data; not discovered on this run. Review before assuming removal.

  • Ruinous Ankh (ruinous-ankh)
  • Spectral Visage (spectral-visage)

Review Notes

  • Role pools (data/smite2/god-pools.json) are preserved from canonical data unless manually updated.
  • Item build pools (data/smite2/item-build-pools.json), including chaos-build eligibility, are preserved from canonical data unless manually updated. Discovery never grants build eligibility on its own.
  • Review missing-from-source entities, conflicts, renames, class changes, and damage-type changes carefully before merging.

Validation Warnings

  • Items: 2 previously canonical entities were not found in this discovery run and need review.

Outcome

REVIEW_REQUIRED

Canonical data was written, but human review is required before this is safe to publish downstream.

GodForge chaos eligibility

  • Chaos-pool additions: 0
  • Chaos-pool removals: 0
  • Unresolved pool entries: 0

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@diese-tech
diese-tech force-pushed the automation/smite-content-sync branch 10 times, most recently from 4972c77 to bab96d4 Compare August 12, 2026 14:33
@diese-tech
diese-tech force-pushed the automation/smite-content-sync branch 4 times, most recently from 254501b to 6526024 Compare August 16, 2026 13:45
@diese-tech
diese-tech force-pushed the automation/smite-content-sync branch from 6526024 to adfc175 Compare August 17, 2026 13:53
diese-tech added a commit that referenced this pull request Sep 1, 2026
Second hard-coded blocker in the same pipeline as #112. 005_item_catalog
test 5 asserted an exact 265 rows and a frozen
source_updated_at = '2026-07-29T15:19:05.553Z' across every row. A
reviewed sync restamps that provenance by design, so the assertion failed
on every content PR -- #83 carries 265 items, an unchanged catalog size,
with provenance at 2026-08-07 and 2026-08-17, and failed purely on the
timestamp.

The failure was invisible until now: database-contract is gated on
repository-state, which had been failing first on the hard-coded god
count, so this suite had never run against a synced catalog.

The assertion now requires the catalog to be whole, active,
source-attributed, and carrying provenance on every row, with a floor
rather than an exact count. The verify-seed-growth step added in #112 is
what stops the catalog shrinking, and it already covers the items seed.
The description had also drifted, claiming 260 while asserting 265.

Verified on PostgreSQL against #83's shape: 265 rows with two distinct
provenance timestamps pass where the frozen assertion fails, growth to
266 passes, and a null source_updated_at or an inactive row still fails.
@diese-tech
diese-tech merged commit 4bf9f34 into main Sep 1, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant