Skip to content

Resolve Cycle 11 Stage 5 review findings - #2089

Open
realmarcin wants to merge 1 commit into
mainfrom
codex/c11s5-review-findings-20261114
Open

realmarcin wants to merge 1 commit into
mainfrom
codex/c11s5-review-findings-20261114

Conversation

@realmarcin

@realmarcin realmarcin commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Cycle 11 Stage 5 consumed the accepted Stage 4 review findings and resolves the actionable G-C11S4-RECORD-LEVEL-DEFINITION-SOURCE-SNIPPETS group tracked in #2002.

  • added verified Stage 4 Europe PMC abstract snippets to record-level evidence[0] for 12 genomics records:
    • codon_usage_bias.yaml
    • crispr_cas_system.yaml
    • gc_skew.yaml
    • genome_size.yaml
    • mobile_genetic_element.yaml
    • pangenome_openness.yaml
    • plasmid_carriage.yaml
    • ploidy.yaml
    • prophage.yaml
    • restriction_modification_system.yaml
    • rrna_operon_copy_number.yaml
    • transposable_element.yaml
  • extended scripts/curate_stage5_review_findings.py from 115 to 127 guarded specs and pruned only the 12 exact evidence[0] MISSING_SNIPPET rows from conf/evidence_snippet_baseline.tsv
  • added a regression test proving the Cycle 11 baseline pruning is narrow and idempotent
  • regenerated rendered pages and pages/data/traits.json
  • added one append-only repository history record for the coherent bulk writer change
  • saved the fresh structured post-remediation review and Stage 5 workflow evidence, including the issue map and validation summary
  • linked the independent review-lineage finding in Preserve Stage 4 issue_key lineage in Cycle 11 Stage 5 review output #2097; this PR head already preserves the Stage 4 stable issue keys in the Stage 5 structured review, workflow copy, and coverage JSON

The five non-actionable Stage 4 cohort groups are preserved as deferred under their existing open issues: #1982, #1983, #1984, #1985, and #364.

Validation

  • uv run ruff check scripts/curate_stage5_review_findings.py tests/test_curate_stage5_review_findings.py
  • uv run ruff check .
  • uv run pytest tests/test_curate_stage5_review_findings.py -v
  • uv run pytest
  • just curate-stage5-review-findings
  • just curate-stage5-review-findings --apply
  • just gen-pages
  • just validate-all
  • just audit-snippets
  • just validate-history
  • just validate-products
  • just qc
  • uv run python scripts/record_review.py validate .temp/codex-mech-continue-20261114/traitmech/c11s5_review.yaml
  • .venv/bin/python scripts/record_review.py validate .temp/codex-mech-continue-20261114/traitmech/c11s5_review.yaml reviews/structured/20261115T041700Z-cycle11-stage5-remediated-records-review/review.yaml reviews/workflow/mech-goal-sequence-20261019/cycle-000011/stage-05/revision-0001/remediated_records_review.yaml
  • PYTHONPATH=../../KG-Hub/KG-Microbe/culturebotai-claw/src ../../KG-Hub/KG-Microbe/culturebotai-claw/.venv/bin/python -m kg_microbe_workflows validate-evidence --root . --previous reviews/workflow/mech-goal-sequence-20261019/cycle-000011/stage-04/revision-0001/evidence.yaml --required-output issue_map --required-output validation reviews/workflow/mech-goal-sequence-20261019/cycle-000011/stage-05/revision-0001/evidence.yaml
  • focused Stage 4 to Stage 5 review-lineage aggregation: 0 diagnostics for the Stage 5 review, codon-usage-bias-definition-source-snippet resolved
  • #2097 lineage finding: initial source head c3f7861ec47519ec0230b9c24f035544a141a98e used finding IDs as successor issue_key values; final head 0f609e3df0ed0488d7b612367e236ca3e55060c9 maps those findings to stable Stage 4 keys in the structured review, workflow copy, and coverage JSON
  • git diff --check
  • independent codex review --commit HEAD: no actionable regressions found; live Europe PMC quote verification was unavailable in that review sandbox because DNS resolution failed

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant