Skip to content

Event chain E0–E5: warranted finding → identity → verified repair → qualified learning #984

Open

Description

@hyperpolymath

Objective: prove a complete event chain before upgrading the context engine

This is an integration programme, not a new graph/database proposal. Begin with one real event chain from a GitHub finding through gitbot-fleet/Hypatia observations and ultimately a verified learning outcome. Keep VeriSimDB, VCL-UT, Odraz/JEG, residual-evidence and invariant-path independently useful. Do not force any of them to become Hypatia-only. No automation should increase repair confidence or authorise a merge from unverified external reports.

Observed as-built state (2026-10-30)

  • Hypatia lib/vcl/client.ex routes primarily to a flat-file FileExecutor, with remote executor for multi-URL sources; it does not currently demonstrate a fully integrated VeriSimDB/VCL-UT/JEG analysis path.
  • VeriSimDB elixir-orchestration/lib/verisim/query/vclt_gate.ex supports an optional VERISIM_VCLT_GATE binary. Unconfigured returns :skip; proof discharge and mutations use other paths. This gate is a static admissibility check, not a factual attestation that a code change is good.
  • vcl-ut owns the proof-backed VCL admissibility semantics; the exact reachable L7–L10 source surface and residual obligations must be treated as observed/version-specific, never asserted from README badges alone.
  • Odraz JEG is a pre-alpha independently useful claim/evidence mechanism. It is not deployed as Hypatia's generic graph service.
  • #919 wants support-named gate verdicts. #971 wants a single KYAML-parsed workflow model. These are adjacent but do not block the initial outcome chain.
  • PR #982 attempts replay-safe, postcondition-backed fleet ingestion. At inspected head 579e969c6343c9a4a312eae78bf2033754c61b93 it had nine unresolved inline review threads (six Codex, three CodeRabbit), and red Security Status, Rust Dependency Audit, Rust License & Ban Check, and governance / Allowlist Preflight; it was returned to draft. Do not report it as complete or learning-verified.
  • lib/cross_repo_learning.ex on main still counts outcome: "success" in local and transferred evidence without the stricter verification qualification. Repairing just OutcomeTracker is insufficient to close the overall feedback loop.

Event-chain trace (MVP; all steps must be inspectable)

  1. Source change: identify repo/ref, immutable commit SHA, relevant path/symbol and scan tool version. A path/line alone is not stable identity; use file/revision identity and reanchoring when available.
  2. Observed finding: structural scanner emits a reproducible observation and its evidence reference. Keep asserted, inferred, observed, tested, contradicted different; do not certify assertions because they were received.
  3. Identity/relationship context: link affected symbol, transitive callers and previous version through existing VeriSimDB graph/temporal/provenance modalities; record modality/profile and missing witnesses explicitly. Vector results can nominate candidates, never establish identity or equivalence alone. Later seam, not a prerequisite for the MVP outcome chain.
  4. Admissibility: where operations need VCL-UT checking, record the actual certified level, input/schema digest, gate version and whether invoked/skipped/failed. A skipped gate is NOT a pass. Preserve verifier limitations. Later seam, not fabricated today.
  5. Judgement: record claimed effect, supporting and contradicting evidence IDs, policy version, qualification status and current-head context. JEG-like evidence model is an interchange concept, not a mandatory dependency on Odraz.
  6. Attempt: append an identifiable attempt_id with stable producer identity and source event provenance before execution. Do not use a hash of the JSON contents as an attempt ID: separate attempts can have identical content. Avoid host-specific absolute paths and credentials.
  7. Test/verification: record before/after predicates, test runner+toolchain, exit status, test/scan digests, verified | incomplete | failed | unverified, independent failure/timeout cases. A zero exit code or neural self-assessment alone does not establish successful remediation.
  8. Durable ingestion: use a stable event identity and idempotent destination write, detect corrupt and unreadable logs, retry transient reads/writes, prevent producer feedback echoes and duplicates after restart. Different attempts with identical payloads must remain distinct. Record causality (parent IDs) and timestamps as metadata, not as trust substitutes.
  9. Qualified learning and review verdict: Bayesian counts, annealing temperatures/stages, cross-repo transfer and dispatch decisions use the SAME verified-evidence qualification. Unsupported records may still count as auditable attempts, not successful fixes. Findings/approvals name exactly which evidence they depend on. If evidence is withdrawn, recompute/revise dependent verdicts (link Gate verdicts that name their support #919 and residual-evidence Revision).
  10. Receipt: emit a compact machine-readable chain with head_sha, subject_id, event_id, parent_event_ids, source, provenance, assertion, observations, proof_or_test_ref, qualification, verdict, missing_evidence, chain_version. Final format must respect KYAML / I-JSON/JCS policy through their actual canonical tools, not introduce ad-hoc parsing or Python.

First implementation slice: close PR #982's epistemic leaks

Do not create a grand new data model before fixing the actual false-learning path.

  • Fix all outstanding review findings in PR fix: stop replay and false success in fleet learning ingestion #982 with fixtures: local failed fixes must count as failures; unqualified results may appear in the audit log but not advance Bayesian confidence, annealing maturity or dispatch tier; unqualified-only attempts must persist as such.
  • Handle missing/unreadable destination log, dropped append, changes during poll, and restart/replay. A failed persistence operation must not advance a source cursor/signature.
  • Deduplicate the same actual event, not different attempts containing byte-identical JSON. Define an exact stable source identifier and prove how producer emits it or an equivalent source-location identity; event-ordering and crash-recovery tests are required.
  • Prevent re-reading imported fleet outcomes as new local outcomes on the following scheduler tick.
  • Audit and fix CrossRepoLearning's unqualified success counts/transfer and anomaly classification, in a separate targeted PR or explicitly linked follow-up, with negative tests. Otherwise higher-level confidence remains vulnerable.
  • Run the pinned Elixir tests and an integration fixture across two polls + scheduler restart, synthetic identical-but-distinct attempts, missing/corrupt logs, retry-after-write-failure, red->green transition, and withdrawn evidence. Treat incomplete tool execution as BLOCKED.
  • Resolve all app review threads substantively and inspect current-head CI, including the four red checks named above. Never bypass a rule to get green. Preserve Verified signature policy.

Acceptance evidence

Only claim E0 outcome chain verified when tests show:

  • 1 verified event credits one outcome and one learning update across poll/restart/replay.
  • 2 distinct attempts with identical outcomes credit twice if both verified, while replay of one event never credits twice.
  • Exit-zero-only / absent verifier / contradictory evidence contributes zero positive learning and zero maturity increase.
  • A true failed attempt lowers confidence appropriately; a failed write does not commit or acknowledge an event.
  • Missing/unreadable/corrupted evidence causes a visible failure/unknown, never a silent success.
  • Cross-repo consumers cannot re-introduce unqualified confidence.
  • A resulting gate/learning receipt names its exact evidence and supports retraction/revision without erasing audit history.

Following E0 (not before): E1 parsed workflow identity with #971 and KYAML; E2 VeriSimDB graph/temporal/provenance identity and optional native-vector retrieval (reusing existing HNSW); E3 VCL-UT validation seam; E4 JEG-style support/contradiction exchange with Odraz-compatible semantics; E5 controlled neuro-symbolic synthesis. Each state must be separately demonstrated as source-existing / tested / integrated / operational. Never claim features are operational because their repos exist.

Boundaries

No new Python. No forced cloud vector DB, blockchain, login or mandatory new sandbox. No breaking changes to unrelated research repos. No unapproved fixes or automatic merges. Keep this scoped to event-source integrity and reproducible evidence before expanding to formal consonance. This is event-chain integration, not an architectural restart.

Activity

  1. coderabbitai commented on Oct 30, 2026

    @coderabbitai
    Contributor
    🔗 Related PRs

    #982 - fix: stop replay and false success in fleet learning ingestion [open]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  2. hyperpolymath commented on Oct 31, 2026

    @hyperpolymath
    OwnerAuthor

    E0 implementation checkpoint (2026-10-30/31 UTC)

    Draft PR #982 (fix/fleet-learning-evidence-20261030, most recently inspected head a25373bd5ea1fada02521b89421f621452436e3b) now changes the actual feedback boundary:

    • Only eligible postcondition-backed observations advance Bayesian confidence and new annealing.
    • Existing saved annealing maturity is compared to qualified log counts on read; legacy veteran states no longer automatically confer dispatch authority when all supporting logs lack verification fields. Added planted historical-veteran regression.
    • Same append-only fleet line replay is identified by line ordinal + bytes; separate identical attempts have distinct provisional IDs. The producer should eventually emit a real stable event_id.
    • Missing/unreadable imported-ID logs fail closed; failed destination appends do not acknowledge the source. Permanent malformed historical fleet lines are quarantined/skipped with warning, while an unterminated final line is retained for retry.
    • Fleet imports are not counted twice on the next local poll.
    • Failed local fixer attempts carry a negative failed status; batch rollback requests carry explicit negative provenance without claiming they executed a revert.
    • Confidence persistence failures are recorded as pending and retried by the scheduler on later cycles (including after reading imported fleet log rows); no Python added.
    • Added explicit mix test test/outcome_tracker_test.exs test/cross_repo_learning_test.exs to the pinned Elixir E2E job. On prior head 31e240477c70b008ef251cd7c3d91ab808e1741f, this job ran 29 ExUnit tests with 0 failures (Actions run 41148628818, job 124379674626). Later commits are not covered by that outcome; current-head CI is still pending.

    Draft stacked PR #986 (fix/e0-cross-repo-qualified-after-982, base = #982 branch) applies the same qualification function to local/transferred cross-repo confidence, transfer source eligibility, cached indexes and verified anomaly evidence, with planted negative tests. PR #985 was closed unmerged because it had incorrectly targeted main, where the new qualification function was unavailable.

    Still owed (not E0-certified): current-head ExUnit, format, reviews and mandatory CI on both branches; replay/restart/incomplete-write end-to-end fixture; historical-data migration parity/performance on large logs; stable producer event IDs; all bot review conversations; verified signatures. Governance / Allowlist Preflight fails for five SHA-pinned metadatastician/standards reusable workflows not covered by the current allowlist, and Rust license/dependency security checks also fail. These must be diagnosed and repaired, not waived. No merge authorised.

    After this closes, proceed E1 KYAML source model (#971), not a newly invented vector database.

  3. hyperpolymath commented on Nov 1, 2026

    @hyperpolymath
    OwnerAuthor

    E0 post-merge audit — 2026-11-01 (BLOCKED, not acceptance)

    Inspected main at f6f8864e772003a2ee66b18b3d8261a5484a6d2a and merged PRs #982/#986. Both ingestion and cross-repo qualification code are present; no new database or Python. The current-head E2E Elixir, Security, CodeQL and CICD Squabbler workflows pass, but this is not full E0 replay/restart acceptance.

    Specific code-level regression candidate: lib/learning_scheduler.ex:517-575, local ingest_new_outcomes/1, snapshots file size and advances last_outcome_positions[file] to size after parsing with String.split("\\n", trim: true); undecodable lines are silently dropped. An incomplete final JSONL record can therefore be acknowledged, and an append containing only its suffix is read from that advanced offset on the next poll. Missing/unreadable local files are not surfaced as a blocking evidence condition. Contrast fleet import at lines 664-714, which explicitly rejects an incomplete final row without acknowledging the source signature. Validate with a two-poll append-in-progress fixture before fixing; then retain the offset of the last complete newline, quarantine complete malformed historical lines with traceable audit metadata, and retry incomplete tails without duplicate outcomes. Also test file truncation/rotation and restart.

    Current-head governance blocker: Governance run 41249464522 has failed governance / Allowlist Preflight, job 124679746203. The log reports exactly two uncovered action refs: google/clusterfuzzlite/actions/build_fuzzers@v1 and google/clusterfuzzlite/actions/run_fuzzers@v1 (45 references inspected). Review legitimate usage, action security and canonical allowed-actions policy; do not turn off the gate or add blanket wildcards. Separate Mirror run 41249464519 has host verification failures for Gitea, Disroot, SourceHut and a Bitbucket push failure; these should be triaged as operational integration issues, not misreported as learning-test failures.

    Outstanding proof obligations: executable pinned two-poll + restart tests for same-event deduplication, distinct identical attempts, partial tails, read/write/recipe-file failures, maturity reconstruction from old veteran states, and cross-repo non-qualification; inspect #982/#986 review thread resolution and actual signed-commit/merge rule status. Current unit tests cover many qualification cases but their test names do not establish the full restart integration contract. Until demonstrated, E0 remains BLOCKED. No merge, branch-rule waiver or dispatch authorisation proposed by this note.

  4. hyperpolymath commented on Nov 1, 2026

    @hyperpolymath
    OwnerAuthor

    E0 critical-path repair issue created: #995 — local JSONL ingestion must not acknowledge incomplete records. Follow that with deterministic replay/restart fixtures, canonical I-JSON/JCS evidence/identity checks, then governance gates and an exact-head E0 receipt. This is an independent repair seam, not a request for a new database or Python.

  5. hyperpolymath commented on Nov 4, 2026

    @hyperpolymath
    OwnerAuthor

    Cross-repository execution evidence from the 2026-11-04 audit is now recorded in hyperpolymath/proven-cicd-and-workflows#77, with companion repairs hyperpolymath/proven-tests-and-benches#103, hyperpolymath/pons-asinorum#68 and hyperpolymath/panic-attack#257.

    Both scanners were run with strict coverage on all four repositories. All eight runs returned exit 2 / partial coverage. These must enter E0–E5 as incomplete observations, never as clean scans or successful repairs. The suite gate now preserves this distinction, bounds execution and runs the second scanner even when the first refuses; 88 controls include the full 49-pair exit matrix and an actual timeout.

    A concrete negative-label failure was reproduced: a Pons fixture assumed two Python property reads were stable. A changing property produces UnboundLocalError. PR #68 retains the original as a positive fixture and makes the negative snapshot once. A learned outcome must bind the source digest, fixture identity, execution result and review; changing a fixture label alone is not evidence of repair.

    Requested integration acceptance: malformed report, unknown/partial coverage, repeated delivery, tool crash and absent checker cannot increase assurance; correlated Pons/panic observations retain their separate provenance and do not count as independent proofs. This audit did not execute Hypatia's neural/symbolic system, so it is feedback for its conformance corpus, not a claim of completed Hypatia verification.

  6. hyperpolymath commented on Nov 14, 2026

    @hyperpolymath
    OwnerAuthor

    Farm recon for hypatia issue 984, step E0

    Scope: read-only recon of hyperpolymath/.git-private-farm (private), 2026-11-14. Nothing in the farm was changed. Claims are marked READ (file and line) or RAN (command and result). Local test success does not show live CI or estate health.

    Summary

    1. The farm's merge actuator (scripts/actuate.sh) is unwired. No workflow, Justfile or script calls it. The farm README and merge-observe.yml say so correctly. The stale statements are hypatia lib/merge_orchestration/loop.ex line 25 and lib/application.ex line 106, which say the farm "independently re-verifies and merges". (Not re-checked here: I did not read those hypatia lines in this recon; they are as quoted in the task brief.)
    2. The actuator and its ledger are real, tested code, not only README text. Its design is worth copying for E0-08, E0-11 and E0-12.
    3. The propagation workflow's idempotence key is weaker than the README says (details below).
    4. The offline test suite passes in a scratch copy once the pinned yq v4.54.1 is installed. That does not establish live CI or estate health.

    Design rules: what the farm does in code

    # Rule Verdict Evidence
    1 Idempotence by key Done in code, with gaps .github/workflows/propagate.yml:136 builds the key; dedupe at lines 150-180
    2 Applied, skipped, failed counted apart; applied=0 fails Done in code propagate.yml:514-540; scripts/actuate.sh:14, 413
    3 Read-only receiver check, fail closed Done in code, with gaps propagate.yml:182-204; scripts/verify-receiver.sh:78-109
    4 One writer per repo Done in code propagate.yml:73; actuate.sh:300, 393
    5 Durable intent ledger and contract Done in code, unwired actuate.sh:95-101, 326; docs/operations/merge-provenance.adoc:63-94
    6 Actuator wired? Unwired no caller anywhere; merge-observe.yml:26-36, 198
    7 Drift detection Done in code scripts/drift-detect.sh:90-122
    8 SHA bump validation and tests Done in code scripts/validate-sha-bump.sh:4-64; tests/sha-bump-test.sh:98-167
    9 Offline suite Passes in scratch copy RAN below

    1. Idempotence key (gaps)

    • Key format, READ propagate.yml:136: event=<id>;repo=<owner/name>;sha=<target>;template=<version>;correlation=<id>. Absent fields are written as none. Correlation is a fifth field the README does not name.
    • The key is not stored. It goes to step outputs, the run summary (line 498) and a per-forge outcome TSV artifact (line 465, 30 day retention).
    • The duplicate check (lines 156-170) runs gh run list --limit 200 and matches the run title Propagate: <repo> [<token>], where the token is the event id, else the correlation, else the sha. So the effective match is repo plus one token, not all four fields.
    • A retry can slip through when:
      • a manual dispatch supplies only target_sha: the run-name (line 19) uses client_payload.sha, not inputs.target_sha, so the titles never match;
      • the repo was sent as a bare name: the run-name carries the raw name but the check searches the normalised hyperpolymath/<name>;
      • the payload has no event id, correlation or sha: dedupe is skipped (line 157);
      • the earlier run is older than the last 200 runs.
    • It over-blocks when the same event id arrives with a different SHA or template version. A prior failed or cancelled run also counts as a duplicate.

    2. Counts

    READ propagate.yml:514-540: applied, skipped (skipped_*) and failed are counted separately, and applied=0 exits 1 (line 537). A duplicate run also exits 1 (line 511). The actuator prints four counters, including refused (actuate.sh:413).

    3. Receiver verification

    • READ verify-receiver.sh:78-109: checks owner/name shape, canonical full_name equals the payload coordinate, repo not archived, head is 40 hex. API errors exit 65, mismatches exit 66.
    • The read token is FARM_READ_TOKEN when set (lines 66-72). Otherwise propagate.yml:191 falls back to MAINTENANCE_PAT, which can write.
    • The workflow comment (lines 10-11) says the sender's SHA is re-verified. The code records the live head but does not compare it to the sender's target_sha, and the later mirror clone (line 338) does not pin to it.

    4. One writer per repo

    propagate.yml:68-74: concurrency group propagate-<raw repo>, no cancel. Keyed on the raw string, so a bare name and the full name do not serialise together. The actuator adds a per-batch guard (actuate.sh:300-303) and a non-blocking flock on the ledger lock (lines 392-396).

    5. Ledger and contract

    • Files: docs/operations/merge-provenance.adoc (contract) and scripts/actuate.sh. Default ledger is state/actuated.jsonl (actuate.sh:13). It is gitignored (.gitignore:92-93) and absent from the checkout, so a write would fail closed.
    • READ actuate.sh:326, 95-101: an intent row is appended and fsynced before the merge request at line 331.
    • States: intent, uncertain (actuate.sh:360), observed_merged (lines 291, 353), applied (line 346). applied requires an HTTP 200 mutation response whose SHA equals the fresh merged PR SHA.
    • Row key (line 79): event;repo;pr;sha;template. Rows are schema_version 2.
    • A missing, malformed or symlinked ledger fails closed (lines 387-391). The code never creates a ledger.
    • Retry is safe: an unresolved intent or uncertain row blocks any repeat request, and a retry may only read the PR. A merge seen on reconciliation is counted as skipped, not applied (merge-provenance.adoc:89-94).
    • There is no undo. The contract states no rollback is performed.

    6. Is the actuator wired?

    Verdict: unwired, but code complete and tested.

    • RAN grep -rn 'actuate\.sh\|merge-decisions': only comments, docs, tests and fixtures. No workflow, Justfile or script calls it.
    • READ merge-observe.yml:15, 26-36, 198: "DELIBERATELY STILL UNWIRED", per an owner ruling of 2026-08-25. The observe workflow is manual dispatch only (line 63).
    • Path from a decision file: actuate.sh:417-423 takes a .jsonl or .json file by hand. It is dry-run unless FARM_ACTUATE_WRITE=true (line 382). It refuses without a veto-free arm_auto decision, an assessed 40-hex head, an event id and green CI (lines 192-240). P3 needs FARM_P3_AUTHORIZED=1. mass_squash needs an active campaign marker.
    • Consequence: hypatia's "independently re-verifies and merges" lines describe a path no automation runs.

    7. Drift detection

    READ drift-detect.sh:90-122. For each manifest repo with auto_propagate true, it compares the GitHub HEAD SHA with the same ref on each non-GitHub forge via anonymous git ls-remote. "Same" means an identical commit SHA on the default branch at that moment. It does not compare name, ownership, archive state, other branches, tags or content. On a difference it prints drift and exits 0 (header lines 14-15). Other statuses: ok, forge-missing, forge-unreachable, ungated, github-private, github-unreachable. Radicle, Azure DevOps and CodeCommit are skipped (line 109). So this is a mirror freshness check, not an identity check.

    8. SHA bump validator and tests

    READ validate-sha-bump.sh:4-64: both SHAs are 40 hex and differ; the reusable source must be metadatastician/standards or hyperpolymath/cicd-suite, and the redirect alias hyperpolymath/standards is refused (lines 32-36); path shape is checked; title, body and branch text may not mention licence, SPDX, secret or CVE words; the branch may not be main or master; the consumers TSV must be well formed, deduplicated and between 1 and 500 rows. tests/sha-bump-test.sh covers: dry-run default with receiver checked first and only the exact pin bytes written (line 98), a dangling coordinate failing before any write (113), a missing reusable at the target SHA (122), a canary with no jobs stopping fan-out (136), a second propagator refusing to start (148), and the allowlist plus legacy alias refusal (167).

    9. bash tests/run.sh

    • It was run only in scratch copies, with credentials unset and a gh stub that exits 99. The first runs failed for environment reasons: the pinned yq v4.54.1 was missing, and incident-regression-test.sh drops to the nobody user, which could not read a 0700 scratch path.
    • After installing the repo's pinned yq (digest checked by scripts/install-label-yq.sh) and running from a world-readable directory, RAN bash tests/run.sh exited 0 and printed PASS: offline farm suite. All 20 checks passed.
    • The scratch copies were deleted afterwards and the real checkout was unchanged.
    • This is an offline, mock-based result only.

    Three farm facts for E0-08, E0-11 and E0-12

    1. Event id in the key, with a validated shape and no invented fields. actuate.sh:50 requires the event id to match ^[A-Za-z0-9][A-Za-z0-9_.:/-]{0,255}$ and the head to be 40 hex. The key format is at line 52. Missing provenance refuses (actuate.sh:213-215). The observer's event id in Actions is github:<repository>:run:<run_id> (merge-provenance.adoc:12-14).
    2. Receipt design. .observation-batch.json is collecting before publication and complete only after every requested repo succeeds. It names each record file with its SHA-256, and the reader re-reads it after loading (merge-provenance.adoc:27-38).
    3. Effect evidence is separate from process exit. applied needs a 200 response SHA equal to the fresh merged PR SHA (actuate.sh:345-349). Anything weaker is observed_merged and counts as skipped (lines 353-358). merge-provenance.adoc:96-99 says learning must use independently qualified effect evidence, never a process exit or an empty finding count. One verified event should credit one outcome.

    Contradictions and estate rule departures

    • Hypatia lines saying the farm merges (above) conflict with the unwired actuator.
    • propagate.yml:10-14 claims the sender's SHA is re-verified and retries of the same key are skipped. The code does neither fully (items 1 and 3).
    • A2ML files (retired): 0-AI-MANIFEST.a2ml; .machine_readable/anchors/ANCHOR.a2ml; .machine_readable/descriptiles/META.a2ml, ECOSYSTEM.a2ml, STATE.a2ml; contractiles/{intend,dust,must,bust,trust}/*.a2ml.
    • Python files (banned): scripts/label-sync-graphql.py, scripts/labelutil.py, scripts/label-migrate-graphql.py. No Makefile.
    • .machine_readable/MUST.contractile:49 says "Deno only", against the Bun-first rule. RSR_COMPLIANCE.adoc:15 says "Bun preferred, Deno banned".
    • .machine_readable/ holds 9 files: 4 .a2ml (ANCHOR, META, ECOSYSTEM, STATE), 4 .contractile (ADJUST, INTENT, MUST, TRUST) and svc/k9/farm-metadata.k9.ncl.
    • TRUST.contractile exists and is not a copy of MUST. INTENT and ADJUST open with generic definition blocks; I did not read their bodies in full, so I cannot say whether they are filled in.
    • Enrolled repo counts disagree: STATE.a2ml:28 says 24 (and line 43 says 25); ECOSYSTEM.a2ml:29, codemeta.json:6, EXPLAINME.adoc:14 and docs/wiki/Home.md:7 say 25. RAN: farm-manifest.json has 25 repos, 23 with auto_propagate true.
    • README line 224 calls hypatia Rust. It is mostly Elixir.

    Suggested follow-ups (not done)

    • Hypatia: correct the "re-verifies and merges" wording in loop.ex and application.ex.
    • Farm: fix the dedupe gaps in item 1 or soften the propagate.yml header and README claim; compare the sender's target_sha to the live head.
    • Farm: reconcile the 24/25/23 counts and the "Deno only" line.

    Generated by Claude Code

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions