ziz-drop: Žiz design, JEG spec, tree-sitter skeleton, Chapel bootstrap + triage of AI-generated material - #1048
Merged
Merged
Conversation
… ziz0 bootstrap, and triage of AI-generated material Staging area for metadatastician/ziz (not yet reachable from this session). Contents: README, DESIGN, docs/JEG, TRIAGE (bins A/B/C of the Gemini transcript), tree-sitter grammar + indent-stack external scanner + corpus, bootstrap/ziz0.chpl (unverified: no chpl available), examples, Justfile fragment. ASCII-only surface; no triads, no dialectics in semantics.
arena-ai-coding-agent
Bot
requested a review
from hyperpolymath
as a code owner
September 24, 2026 22:34
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
hyperpolymath
approved these changes
Sep 24, 2026
hyperpolymath
pushed a commit
that referenced
this pull request
Sep 27, 2026
…D29, D43) (#1051) ## What this is The five owner-only rows held back from the 2026-09-23 batch on #787 were answered by the owner on 2026-09-26 (via selection UI). The answering session (an Arena.ai agent, read-only on the issues API) could not post the rulings itself, so this PR carries the execution kit: - **`arena-session-787/owner-rulings-comment-2026-09-26.md`** — the ruling comment, paste-ready (house format: struck rows, verbatim owner quotes, consequence per row) - **`arena-session-787/787-execution-kit.md`** — the three execution steps plus the two owner-only browser steps: 1. Post the ruling comment on #787 2. Strike the five rows in the issue body (exact find/replace blocks, F4a convention: strike, never delete) 3. File the fresh D29 plugin-host issue (title + body included) - Owner-only, browser: the D12 GitHub for Nonprofits application; the D16 Settings → Applications glance at app IDs 1561 / 85455 / 946600 Any write-capable session may execute steps 1–3 on the owner's behalf; the rulings were given by the owner on 2026-09-26. ## Verification state (2026-09-27) - #787 body unchanged since 2026-09-23T17:28Z — all five Find-blocks byte-match the live body - Based on main @ `2479cf7` (2026-09-24); markdown-only addition, no code or workflow changes ## Merge optional The kit is executable from the branch as-is; merging simply persists it in-tree. Kept as **draft** until the rulings land on #787 — then merge or close at owner discretion. Note: this repo's required-check set includes gates already recorded as unsatisfiable or red on every PR (#1040, #955, #935). Any red here is expected to be pre-existing, not introduced by this PR. Rulings given by the owner 2026-09-26 · kit assembled by an Arena.ai agent session. --- ## Addendum 2026-09-27 — merge attempted on owner instruction; refused by the main gate The owner instructed the merge. Both routes were attempted and refused: 1. **Normal squash merge** → `X not mergeable: the base branch policy prohibits the merge`. 2. **Admin squash merge** → `Repository rule violations found — 22 of 22 required status checks are expected. Code scanning is waiting for results from CodeQL for the commits d1d40f9 or 5ae9c59.` **Measured state of ruleset `23787415` ("main gate: append-only + required checks + signatures + scanning"):** `enforcement: active`, `bypass_actors: []` — no actor, including admins, may merge over it. Rules: `deletion`, `non_fast_forward`, `required_status_checks`, `required_signatures`, `code_scanning`. **The 22 required contexts (none reported on this PR):** `CodeQL` · `SPARK Theatre Gate` · `SonarCloud Code Analysis` · `analyze-actions / analyze` · `analyze-js / analyze` · 14× `governance / …` (Actions lockfile verify, Check Workflow Staleness, Code quality + docs, Debt ratchet, Exemption ratchet, Guix packaging policy, Language/package anti-pattern policy, Licence consistency, Security policy checks, Trusted-base reduction policy, Well-Known, Workflow security linter) · `scan / Hypatia Neurosymbolic Analysis` · `scan / gitleaks` · `scan / rust-secrets` · `scan / shell-secrets` · `uses ⊆ actions.lock`. **The five checks that did run all passed** (CodeFactor, CodeRabbit, Codeac analyze results, GitGuardian, semgrep) — none of them are in the required set. **Consequence:** `standards` is currently **merge-locked for every actor** — a markdown-only PR carrying an explicit owner instruction cannot land. This is the live, measured instance of the already-filed #1040 class (a required context no PR can produce), compounded by #955 / #935 (permanently-red ratchets) and #1050 (Hypatia scan produces no SARIF at current main). Last merge on the repo: #1048, 2026-09-24. **Options on the table:** - **A (doctrinal):** cure the gate first — re-scope `required_status_checks` to contexts that actually report on PRs (D84/D86a precedent), then merge normally. - **B (expedient):** owner edits/disables the ruleset, merges, restores. The "disable-to-merge" shape this estate records as a defect. - **C (interim):** leave this PR open — the branch is on the remote and the kit is executable from it by any write-capable session without merging. Merge attempts and evidence recorded by the Arena.ai agent session, 2026-09-27. Co-authored-by: arena-agent <[email protected]> Co-authored-by: arena-agent <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
ziz-drop/, a self-contained staging set for the Žiz language, intended to be moved verbatim intometadatastician/ziz(that repo is not reachable from this session's GitHub installation, so it is parked here).TRIAGE.adocDESIGN.adocsexpand off-sidelayoutreaders; bootstrap plan; explicit non-goalsdocs/JEG.adocclaimform, A2ML sidecar format, merge/re-anchoring via tree-sitter node idsgrammar/bootstrap/ziz0.chpl--jeg=observemodeexamples/*.ziz,Justfile.ziz-fragmentVerification status (honest)
grammar.jsevaluates under the tree-sitter DSL (23 rules);scanner.ccompiles with-Wall -Wextra -Werror.tree-sitter generate(GitHub release assets unreachable from sandbox) andchpl(not installed).ziz0.chplshould be expected to need small fixes on first compile; this is stated in the file header and README.Open for owner decision (in
TRIAGE.adoc→ "Owner to confirm")Жas a reader-table alias for the evaluator, or drop.claudia / boggs / federici / dunayevskaya / assata.Language policy
Chapel (bootstrap), C (tree-sitter scanner only), JavaScript (tree-sitter grammar DSL only). No Python, no Rust, no Deno. All files carry SPDX headers.