8000 docs: field report for the ES-YAML debug node run by xerj-org · Pull Request #2127 · xerj-org/xerj · GitHub
[go: up one dir, main page]

Skip to content

docs: field report for the ES-YAML debug node run - #2127

Merged
xerj-org merged 1 commit into
mainfrom
cursor/yaml-conformance-field-report-da05
Oct 22, 2026
Merged

xerj-org merged 1 commit into
mainfrom
cursor/yaml-conformance-field-report-da05

Conversation

@xerj-org
Copy link
Copy Markdown
Owner

What this changes, and why

Field report from the agent that ran the local debug node as the ES-YAML target while working on #2114. One new file. No code, no docs.

Evidence

The numbers in the file are the runner's summary line and xerj --version from that session. The delete-guard change itself is #2126.

Checks

  • cargo fmt --all (CI runs rustfmt --check and clippy -D warnings)
  • Scoped release build of the crates touched: cargo build --release -j 32 -p <crate>
  • cargo test -p <crate> passes (cargo check is not sufficient — test code is interleaved with production code)
  • ES-YAML conformance suite at 0 failed (cargo run --release -p es-yaml-runner -- --dir tests/es-compat-yaml/yaml), or: not applicable because this change is docs/landing-only
  • New ES-compatible behaviour has a matching YAML case under engine/tests/es-compat-yaml/yaml/
  • Docs updated if user-visible behaviour changed
  • For non-trivial changes: the applicable audit in docs/CONTRIBUTION_REVIEW.md
  • For non-trivial changes: if this PR changes an operational document or runnable recipe, complete the operational audit in docs/CONTRIBUTION_REVIEW.md. Record a negative control that exits non-zero with no artifact extracted, installed, published, or served. Keep verification and its action in one block; rerun the control with the failing exit discarded and with the next documented block appended, and require that neither reaches an artifact or unsafe/privileged path. List tested variants and unsupported variants separately, and verify every publication copy. Otherwise mark this item N/A with a reason.

Not run: fmt, clippy, tests, release build, ES-YAML. This PR adds one markdown file and does not change the engine. The operational-recipe audit is N/A: the file is a report, not a runnable recipe.

Provenance

  • Written by: AI agent (Cursor Grok 4.7)
  • Verified: xerj v1.0.0-rc.97; YAML runner summary 1438 passed · 0 failed · 10 skipped · 1448 total in 47.7s against ./target/debug/xerj --insecure --data-dir /tmp/xerj-yaml-data --port 9200.
  • Assumed: nothing about product behaviour beyond that run.
Open in Web Open in Cursor 

The suite was the check for the delete-guard work. One file, nothing else.

Co-authored-by: xerj-org <xerj-org@users.noreply.github.com>
@cla-bot cla-bot Bot added the cla-signed label Oct 22, 2026
@xerj-org
xerj-org marked this pull request as ready for review October 22, 2026 03:06
@xerj-org
Copy link
Copy Markdown
Owner Author

Xerj Merger made the fix: none needed. This is a one-file field report with no credentials or paths beyond the repo. The tokio stack overflow it mentions is debug-profile only: xerj-console-api tests pass with the default stack under the ci-test profile, both on main and with #2126.

@xerj-org
xerj-org merged commit 688bfff into main Oct 22, 2026
21 checks passed
xerj-org added a commit that referenced this pull request Oct 22, 2026
…r sweep (#2136)

* release(rc.98): version stamp, CHANGELOG, ROADMAP roll, landing footer sweep

Window since v1.0.0-rc.97 (about 120 PR merges on main's first-parent line,
every one cited in [1.0.0-rc.98]; the release-notes gate passes locally).

Stamp: workspace 1.0.0-rc.97 -> 1.0.0-rc.98 (Cargo.toml + Cargo.lock).
CHANGELOG: [Unreleased] moves into [1.0.0-rc.98], plus the window's uncited
merges grouped by area; the rc.97 heading gets its tag date (2026-10-19).
ROADMAP review line + roll: open defects stay at five. Landing footer sweep
RC.97 -> RC.98, the data-latest-tag fallback, and the regenerated sitemap.

* release(rc.98): cite #2124, #2126 and #2127

* Merge main into release/rc98

* release(rc.98): one #2124 entry

* release(rc.98): intro names #2128 and #2126

* release(rc.98): regenerate sitemap after the merges

---------

Co-authored-by: Xerj Merger <merger@xerj.org>
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.

2 participants

0