Skip to content

Refresh PR935 maps for the exact newer-main corpus required by docs-current #936

Description

@realmarcin

PR #935 passes the complete maintained local QC on its captured source snapshot, but the required docs-current check now fails against GitHub's actual merge result with a newer main.

The failing run is https://github.com/CultureBotAI/CommunityMech/actions/runs/34967259588/job/104374570440. Checkout explicitly reports merge de8ff348b3b6c40579fe058fc1274f09efc01b10, combining PR head e3ba0195d0116ccf8dd07efc04f8120540c7ef7e with main f7c8fae387add00eff6686716fcf06e29455bf2a. just check-docs-current stops in prepare_text_map() with ContractError: map is stale relative to current adapter input before publishing anything. This is the intended freshness guard, not a reason to weaken it.

The accepted map snapshot uses captured main dac73a613cecba786d0f7b115d4762f0b1e38e0b and contains 376 common records (372 communities and four isolates). The exact newer-main comparison adds two community records:

  • kb/communities/Bacillales_Lignin_Degrading_LDSynCom.yaml
  • kb/communities/Dairy_Wastewater_Algal_Cyanobacterial_Cultivation_Panel.yaml

The complete comparison contains only 13 files: those records, their two record pages and histories, three reference caches, two existing tests, and the browser/index pages. It changes no adapter, runtime, graph producer, alias input or dependency lock. Both graph receipts also need the exact new raw-corpus binding; the common semantic gate cannot substitute for graph freshness.

Acceptance:

  • Integrate exactly main f7c8fae387add00eff6686716fcf06e29455bf2a into the existing draft while preserving reviewed implementation, released pin and previous map generations.
  • Export and independently verify the resulting full common inputs; reuse the prior verified cache, encoding only the two genuinely new semantic rows if the expected comparison is confirmed.
  • Refresh both existing specialty layouts against the resulting 374-community raw corpus with truthful partial matching/omission ledgers; preserve the shared source and reviewed producer semantics.
  • Regenerate maintained pages, independently verify all common/specialty routes and current receipts, run required local gates, then normally update draft Add shared BGE text map and verified graph provenance #935 and require green CI. No stale-map waiver, disabled freshness check, remote merge or force push.

Evidence is retained in the remediation workspace under runtime440-transition-graph-pair/communitymech/ci-*. All 54 currently open repository issues were checked for overlap; #900/#905/#911 cover implementation defects, not this newly observed source-currentness integration blocker.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions