v0.3.0

N-1 compatibility for 0.3.0 is against 0.2.1, the latest published patch of the 0.2 minor line. The installed-package bun scripts/n1-check.ts check passed on the prepared 0.3.0 candidate; the existing networked n1 CI job repeats it and remains required by ci-ok.

• N-1 CLI: all 60 published 0.2.1 commands remain, with every prior usage word retained in order; 30 commands are additive (90 total). Additions cover retention, skill checks, harness rounds/streams/transitions, experiences, reviewed lessons, lineage, executor input hashes, literature queries/flow/card exchange, review checklist and paper plans. Optional input/GPU, reuse, named-stage log, query-intent and screening-code controls are additive. New source checks and default v2 skill evidence can require a compatible source reader or revised input; this is not a promise that every earlier write payload or readiness judgment behaves identically.
• N-1 MCP tools: all 55 published tools keep their manifest readOnly values; 30 tools are additive (85 total): ares_retention_inspect, ares_retention_prune, ares_lesson_propose, ares_lesson_list, ares_lesson_check, ares_lesson_decide, ares_skill_check, ares_harness_close, ares_harness_contrast, ares_harness_compose, ares_harness_adopt, ares_harness_stream_set, ares_harness_stream_show, ares_experience_select, ares_experience_freeze, ares_experience_check, ares_harness_set, ares_harness_show, ares_harness_import, ares_lineage_show, ares_lineage_compare, ares_executor_inputs_hash, ares_lit_queries, ares_lit_flow, ares_lit_card_export, ares_lit_card_import, ares_lit_card_list, ares_review_checklist, ares_paper_plan_set, ares_paper_plan_show. Existing schemas gain optional inputs or wider versioned definitions. Skill propose/decide also advertise openWorldHint: true while retaining readOnly: false. The N-1 gate checks names and manifest readOnly values, not complete schema or annotation equivalence.
• N-1 study/ledger formats: 0.3.0 reads 0.2.1 survey/experiment studies (study v1/v2), ledger-event v1 and the existing native formats without a read-time migration. The installed-package check confirms unchanged study/ledger bytes and the no-input protocol hash, design binding and approved gate; 0.2.1 also reads a newly written study v2 unchanged. When encountered by their respective readers, 0.2.1 refuses stage protocol v2, attempt v2/v3, skill-proposal v2 and paper-evidence v2; it also refuses the new fields in closed protocol, executor, scope and plan-step schemas. Paper-plan v1/v2 and the other new namespaces/settings below have no 0.2.1 reader, so those files are ignored rather than version-refused. Use 0.3.0 for the new semantics; no automatic downgrade or blanket older-reader enforcement is promised.

Newer data encountered by 0.2.1	Compatibility boundary
Protocol v2 stages, attempt v2/v3, skill-proposal v2, paper-evidence v2	Their old readers refuse the unsupported version without rewriting the record. Paper evidence v2 is refused by old build/current-build and study-export paths.
Protocol v1 inputs; executor v1 gpu or retentionCapBytes; scope exclusionCodes; plan-step intent, reuse or force-fresh	Old closed-field validators refuse them. Formats retaining v1 does not make these fields usable by 0.2.1.
Paper-plan v1/v2, harness round/transition/stream/experience/fixture-projection v1, lesson proposals v1, executor-local retained artifacts/reuse metadata	0.2.1 has no reader for these namespaces. It ignores their files and unrelated new ledger-event kinds; it does not enforce routing, writing points, harness gates, disposal or reuse semantics. Planned/staged studies require the newer reader.
study.toml paper/review settings	Published 0.2.1 ignores the file, including [review]; refusal by an intermediate unpublished settings reader is not a published N-1 guarantee.
Candidate/search/screen optional metadata; v1 attempt verifiedInputs, gpuDevices or freshRequest	Old readers can ignore optional metadata; acceptance is not equivalent interpretation. Protocol/executor configuration checks remain separate barriers.
Review repair/section/checklist.survey; card extension/reuse fields	Old strict authoring commands refuse the new inputs; stored review replay and direct card readers ignore extra fields. They do not implement current review/card semantics or the new physical-card refusal.

The networked N-1 check covers the manifest and representative study/protocol reads above, not every new format or operation. Feature-specific refusal/ignore distinctions are grounded in the published 0.2.1 source and the offline compatibility tests. New checks may add findings or make an earlier build stale while its stored format remains readable.

• Harness guidance mapper (#66): read-only decoding of the agent-hub GuidanceReadResult public metadata contract at 50100a8 alongside the existing ares fixture format. Keeps native variant/experiment/task/layer/section/digest identity, bounded lifecycle and evidence metadata, and explicit unavailable results. Rationale shape/bounds are checked but its text is omitted pending agent-hub task #822; synthetic PII-shaped canaries cover outputs and errors. Strict ahub execution-reference decoding never enables local-source fallback, skill evidence, hub resolution or live probe import (#1226 remains pending).

  • N-1 CLI: command names, usage and existing fixture operations stay unchanged; no new command is exposed.
  • N-1 MCP: tool names, schemas and annotations stay unchanged; no external resolver is added.
  • N-1 study/ledger formats: no format/version or stored-record rewrite; existing ares reference/projection bytes, round bindings and denominators remain unchanged. New producer metadata is decoded read-only and carries no probe/handoff assurance.

• Supervision treatment record integration (#63 T2b): integration-check now retains all 36 frozen cases and reports the agent-hub#1221 T1 record consumer pinned to bc6f46b077dd3a255debaee8152fa17f1f13b79c. All 12 frozen Supervision task-state payloads remain unsupported rule facts, with per-case reason/hash coverage and helpful/false/missed left unknown (null), not zero or fabricated success. Separate synthetic record vectors exercise the closed reader/scorer without importing or executing hub rules. Helpful/false scoring requires a present matching observation; absence is no-evaluation-coverage, and missed/correct-non-trigger metrics remain null pending source-owned evaluation coverage. Batch counters or caller-asserted evaluated lists cannot establish that coverage. No treatment trial, record receipt or effect path is launched; person decisions remain literal 0. Corpus amendment/sealing and T3 launch remain separate work under their own authorization.

  • N-1 CLI: no command/default switch change; the existing check-only integration output adds Supervision coverage and producer binding.
  • N-1 MCP: no tool, schema or annotation change.
  • N-1 study/ledger/receipt formats: unchanged; prior receipts stay readable and are not rewritten. The T1 seal and frozen corpus/expected files and T2a baseline bytes remain unchanged; new source is bound per run. Tagging and publication follow the separate release workflow.

• Extraction cards are read as physical files: every reader, including lit card list, lit card export, lit card import, paper check's cited-card pass and point evidence, refuses a card path that is a link or special file with the cause and the next step instead of following it out of literature/cards, and a dangling link no longer reads as a missing card. A regular card reads as before and an absent card is still missing.

  • N-1 CLI: no command or usage change; a linked card path refuses where an N-1 reader followed it.
  • N-1 MCP: no tool, annotation or schema change; ares_lit_card_list and ares_paper_check inherit the same refusal.
  • N-1 study/ledger formats: no change; an N-1 reader still follows a linked card path, so a study relying on the refusal needs the newer line.

• Card reuse through vault-mem (#101): lit card export <dir> <id>... --vault ID [--confirm FINGERPRINT] previews, then writes own, identifier-verified cards with hashed-study provenance to the single matching vault-mem reference note (doi/arxiv_id), guarded by the note hash. lit card import copies a card back only for an included candidate verified in this study, stored with a reused record. lit card list and paper check's reusedCards show the provenance; unreadableCards lists cited cards that cannot be read. ArXiv-only papers resolve their note through the arXiv DOI, citekey, id or title (vault-mem does not index arxiv_id) with an exact frontmatter match. The study lock is held only for planning and the commit, not across vmem calls. Both commands need the scope gate and carry any automatic approval into their commit; export preflights its receipt before writing to the vault, and provenance names the actor of the recording lit.card event. Reused cards never touch verification, screening, gates or the bibliography. Cards gain optional datasets, results and motivation. MCP adds ares_lit_card_export, ares_lit_card_import and ares_lit_card_list. Tests use a fake vmem only.

  • N-1 CLI: existing commands and usage remain; the three lit card subcommands are additive.
  • N-1 MCP: existing tools remain; the three card tools are additive and the ares_lit_card card schema gains optional fields only.
  • N-1 study/ledger formats: study and ledger versions stay unchanged; lit.card.exported and lit.card.imported events are additive. Cards without the new fields keep their bytes. Older readers that read card files directly ignore reused and the optional fields; an older lit card refuses input with the new fields.

• Selection flow report (#104): new read-only lit flow [--markdown] (MCP ares_lit_flow) derives the search window, records per source, duplicates, unique, screened, excluded by code, unscreened, included, verified and carded counts from the ledger and candidate file. scope.json may declare up to 30 exclusionCodes; lit screen --exclude --code (MCP code) records a declared code and refuses others. {{n:lit.flow.*}} placeholders resolve in both study modes only while the screen gate is approved; --markdown emits a table whose numbers are placeholders. lit.search now records yearFrom when given and absorbed when a bridging record folds an earlier candidate away, so duplicates reconciles with records and unique (older events without it count as 0; watch run searches go through the same path); the export allowlists both and the screen code.

  • N-1 CLI: existing commands and usage remain; lit flow and lit screen --code are additive.
  • N-1 MCP: existing tools remain; ares_lit_flow is additive and ares_lit_screen gains optional code.
  • N-1 study/ledger formats: study and ledger versions stay unchanged; events without the new optional fields keep their shape. Older readers ignore candidate exclusionCode, but an older scope reader refuses a scope.json with exclusionCodes. Studies from the previous minor line report a flow with one uncoded exclusion group.

• Follow-ups from the merged #61/#63/#102 reviews. A retention refusal now appends "inspect retained evidence and restore integrity before retrying" only when the native reason names no next step, so "cap full", "missing output port", "busy" and selection-bound refusals keep their own advice instead of gaining a contradicting one. With [review] surveyChecklist = "off", review show omits survey fields from checklists and returns an empty surveyAnswers list; an unreadable study.toml adds one review-survey-settings info note instead of defaulting silently. The separate non-frozen producer fixture also covers a changed code tree, where every sealed source stage misses and reruns fresh while the original record stays unchanged. Gates, exit codes and stored bytes are unchanged.

  • N-1 CLI: no command or usage change; review show suppresses per-report survey answers and keeps the aggregate list empty when off.
  • N-1 MCP: no tool, annotation or schema change; ares_review_show output follows the CLI projection.
  • N-1 study/ledger formats: no change; review report v1 and the ledger versions stay as they are, and existing refusals only gain or keep trailing advice.

• Query intent and per-query yield (#103): lit search --intent lexical|semantic|background (MCP intent, plan step args.intent) records the intent on lit.search only when given. New candidates store firstQuery (search-<n>), set only at creation. New read-only lit queries (MCP ares_lit_queries) reports per-search and per-intent included/excluded/new yield and zero-included queries. study export --bundle adds intent to lit.search rows and counts.litQueries, never query text. No query generation, ranking or embeddings.

  • N-1 CLI: existing commands and usage remain; --intent and lit queries are additive.
  • N-1 MCP: existing tools remain; ares_lit_search gains optional intent and ares_lit_queries is additive.
  • N-1 study/ledger formats: study and ledger versions stay unchanged. Searches without intent keep the earlier event shape. Older readers ignore the optional intent and candidate firstQuery; studies written by the previous minor line report as unspecified with unattributed candidates. Older plan set refuses a step with args.intent.

• Optional survey checklist in review reports (#102): checklist.survey takes six booleans (taxonomyPrinciple, noEnumeration, specificGaps, citationRelations, selectionReported, scopeControl); unknown keys refuse. New read-only review checklist (MCP ares_review_checklist) prints the questions. study.toml [review] surveyChecklist = "off" | "show" | "require" (default show for survey studies, off for experiments); require refuses a report without the block. review show adds surveyChecklist and surveyAnswers; answers never gate. The MCP review schema now also accepts the #100 repair/section finding fields.

  • N-1 CLI: existing commands and usage are unchanged; review checklist is additive.
  • N-1 MCP: existing tools stay; ares_review_checklist is additive and the ares_review_add input schema gains optional fields only.
  • N-1 study/ledger formats: review report v1 and ledger versions stay unchanged; reports without the block keep identical bytes. Older readers fold stored reports non-strictly and ignore survey; an older review add refuses a report that carries it. Published 0.2.1 has no study.toml reader and ignores [review]; some intermediate unpublished readers refuse that table.

• Scoped repair and per-section review rounds (#100): review findings accept optional repair (edit/paragraph/section, default edit) and section; unknown repair values refuse. review show adds roundBudget, sections, openBySection, overBudget and info; a section past study.toml [paper] reviewRounds (default 3) gets "replan the section or ask a person" as information only. The review gate conditions are unchanged. study export --bundle adds content-free counts.reviewSections and per-report repairs.

  • N-1 CLI: no command or usage changes; review show output is additive.
  • N-1 MCP: no tool or schema changes; ares_review_show output is additive.
  • N-1 study/ledger formats: review report v1 and ledger versions stay unchanged. Reports without the new fields keep identical bytes. Older readers fold stored reports non-strictly and ignore the optional fields, an older review add refuses a new report that uses them. Format support alone does not guarantee identical readiness under newer checks. The bundle manifest stays bundle: 1 with an additive count.

• Eligible stage-artifact reuse (#64): default fresh behavior is preserved; optional attempt run --reuse eligible and --force-fresh (MCP reuse/forceFresh) add current-policy, source-verified investigation reuse with atomic local source receipts, bounded study-local lookup/pins, reasoned misses and a fresh evaluator. Original and current costs and executed/reused/sample counts remain distinct; unmeasured costs remain unknown. GPU ABI reuse stays unsupported/fresh. The measured pilot is not included.

  • N-1 CLI: required commands/usage are retained; the reuse controls are optional and existing retry/final identity rules remain. V1 execution/identity is retained; v2 stages remain fresh by default and reuse requires an explicit eligible mode and contract.
  • N-1 MCP: existing tools/annotations remain; reuse mode and forceFresh are additive optional inputs on attempt run.
  • N-1 study/ledger formats: readers retain existing v1/v2 attempts, study and ledger versions. Opted-in controlled attempts use v3, with explicit reused source semantics; older readers refuse before mutation. New ledger progress/receipt kinds are additive. Successful retention.pruned events add optional exact manifest-reference tuples [attemptId, stage, sha256] alongside the existing fingerprint/hash/count; 500 maximum-width references remain within the existing 64 KiB ledger event bound. Read-only disposal projections preserve older hash-only receipts as unknown, without rewriting attempts. 0.3.0 supplies the compatible minor reader; tagging/publication remain separate release actions.

• #61 follow-up: a stage that exits 0 without a declared output now fails with a seal refusal naming the missing output port and the next step, instead of a generic retained filesystem error. V2 wall-clock failures keep best-effort stage log evidence like v1; terminal status, reservation release and the unobserved-stop hold are unchanged. No format change.

• Citation hygiene in paper check (#99): deterministic adjacent-duplicate-citation, citation-stack, repeated-bundle, bare-identifier and duplicate-heading findings with section heading paths. Findings now carry severity; the new codes are warnings unless an optional study.toml [paper] table lists them in blocking (thresholds maxGroup, maxBundleRepeats; unknown keys or codes refuse). Existing codes stay blocking and studies without study.toml keep their blocking set. CLI and MCP share one report. No study/ledger format change.

• Protocol v2 stage execution and retained artifacts (#61): opt-in serial fresh candidate stages consume verified read-only task/parent snapshots; a separate fresh evaluator produces metrics. Output payload/file/metadata and wall/compute budgets remain cumulative across the attempt. Executor-local retention uses bounded atomic publication, a default 1 GiB cap with in-flight reservations, and explicit fingerprinted prune with active-consumer refusal and provenance tombstones. Python3 is required for v2. retention inspect and retention prune share CLI/MCP implementations. Permanent stopped-stage verification failures retain their terminal cause and release capacity; transient seal errors preserve the stopped computation for retry; pre-start transient executor failures remain retryable. Released history is preserved in immutable shards with paged inspection, keeping the active index bounded. The prior T1 evaluator double-counting bug and stage/port refusal labels are corrected.

• Release boundary: 0.3.0 supplies the compatible minor reader for opt-in staged protocols and their v2/v3 attempts. Tagging/publication follow the release workflow. scripts/n1-check.ts resolves the latest published previous-minor patch (0.2.1 for this release).

  • N-1 CLI: existing commands and required usage remain; retention commands and optional executor set --retention-cap-bytes are additive. V1 protocol execution, attempt identity and raw-byte design seals remain unchanged.
  • N-1 MCP tools: existing tools and annotations remain; retention inspect/prune are additive and protocol-set accepts a closed v1/v2 union. Optional executor retention cap settings require the compatible reader.
  • N-1 study/ledger formats: study and ledger versions stay unchanged. Current readers keep v1 protocols/attempts; older readers refuse opt-in protocol/attempt v2 without rewriting them. New retention/progress events are additive. Retained bytes remain executor-local; no migration or downgrade is performed. The installed-package/network N-1 CI job remains separate from offline fixture checks.

• Filter prospective experience for temporal and model/runtime/toolset eligibility before any exact-id counterevidence or note reads; incompatible handoffs refuse locally. Share the 256-byte model identity bound across fixture, lesson, experience and MCP validation, preserving valid long model identities.

• Complete #62 T2/T3: new skill proposals default to source-inspected v2, with shared aggregate 25 s/256 KiB response budgets, one local provenance snapshot, owned-lock generation fencing and atomic evidence fingerprints on acceptance. Evidence and counterevidence must both stay available/unchanged; negative/no-winner/unfinished outcomes never imply successful support. Add read-only CLI/MCP skill check and stored-strength console details; no body retention, fallback, export or installation. Historical v1 files and final decisions are unchanged. New v2 writes need a compatible minor release; older readers refuse them rather than silently downgrade. Synthetic executable tests cover process-group cleanup/spawn/output bounds; no live amem or account proof is claimed.

• Complete the local #66 fixture workflow with fingerprint-bound contrast, per-section composition and preview/confirmed experimental adoption/closure and separate baseline-kept/inconclusive/withdrawn close, plus a read-only producer console comparison/edit-to-evidence panel. Immutable closures retain binding/fingerprint/outcome/actor/reason and stale history. Independent deterministic check state/source is separate from deterministic-check/blinded-judgment/actor-claim contrast provenance; current fixtures never claim passed/failed correctness. Changed evidence reopens readiness without rewriting prior decisions; successor bytes need their own fixture execution and identical preserved guidance reuses its receipt. No matched/live assurance, scientific metrics, final qualification, transfer or automatic activation is created. Harness transition format/events are v1; legacy round definitions, native counters and protocols are unchanged.

• Add immutable harness streams, body-free frozen baseline/no-library contexts, optional round context hashes, shared CLI/MCP select/freeze/check and screened exact-id source/version rechecks (#67 T1/T2). Legacy context-free round hashes stay unchanged. T3 adds bounded contrast-backed lesson proposals/checks and hash-bound reviewed dispositions over current harness-closure refs, with required counterevidence checks and explicit synthetic-fixture strength acknowledgement. Accepted unchanged observation/fail/limitation notes export with the literal synthetic-fixture; not evidence of real agent behavior label; no-lesson never exports. Earlier same-study accepted lesson/archive chains can prepare nonempty prior-experience/retrieval-only snapshots after exact screened amem and model/runtime/toolset matches. Bodies stay transient, fixture/prepare-only/no-transfer flags persist, and controlled/live use refuses. Archive recovery is receipt-only: interrupted unreceipted writes require operator reconciliation and may duplicate, without an exactly-once guarantee. No real producer behavior, improvement or transfer is established.

• Harness round T1 (#66): bounded experiment-only round declarations, an independent harness gate using default autonomy, atomic index/events and idempotent synthetic fixture imports. Strict ares-owned variant/probe projection parsers preserve identity drift, unknown usage/sampling and declared source strength; compatible fixtures are never matched or host-observed, and real producer import/end-to-end evaluation remain unavailable. Shared CLI/MCP set/show/import perform no probe/model/hub mutation and touch no native attempt/final counters. Contrast/composition/adoption and console producer views are included by the T2/T3 completion above. Existing studies/gate bindings are unchanged; harness namespace/projections are new v1 formats.

• Skill evidence core (#62 T1): v2 read/validation with applicability, limitations, typed counterevidence and body-free inspection receipts; v1 bytes/terminal decisions are preserved and projected legacy-unresolved. New proposals default to source-inspected v2 and decisions use the T2 evidence-bound preflight described above. Current-study typed provenance refs and screened exact-id amem_show inspection (agent-mem >=0.22.1) expose availability/integrity/recorded outcome separately from reviewer support. Missing capabilities are unsupported, private/absent/capture reads share unavailable, exact returned ids are enforced, and child lifetime/output/environment are bounded. No new export, installation or promotion path. The T2/T3 CLI/MCP/console and atomic acceptance completion is included in this release. The latest readable skillProposal format is 2; older readers refuse v2, while legacy v1 proposals remain unchanged.

• GPU admission (#94): optional executor device allow list, minimum free memory and maximum host-load ratio enable one bounded read-only probe before new GPU attempts. Admission defers with CLI exit 75 and the same structured MCP result for devices/load/probe failures, creating no attempt, approval or budget use. Chosen UUIDs pin every executed candidate stage and the separate evaluator; exports retain device count only. No queue, automatic retry or preemption is added. Executors without GPU settings preserve count-based argv and CPU-only attempts skip probes. This extends executor v1 with a strict optional field; earlier readers refuse that field, and existing no-settings studies remain unchanged.

• Executor-local inputs (#93): optional protocol inputs bind named manifest hashes and read-only stage mounts while keeping network none and existing output limits. The executor hash CLI/MCP command streams regular files through Python3 without downloading or copying input data. Attempts keep path-free input identities and verified hashes; export keeps names/hashes only. Locator changes preserve approval, identity changes stale it; restart requires matching current input identities. Legacy no-input v1 protocol hashes/design bindings and old studies remain unchanged; older readers refuse the optional inputs field. Python3 is required and reported by executor check only for input protocols.

• Section citation plans (#97): optional version-1 paper/plan.json declares exact heading scopes over current included, identifier-verified bibliography keys. CLI/MCP plan set/show share bounded validation (64 KiB, 64 sections, 300 keys/section) and routing coverage. paper check adds positioned blocking out-of-scope citations and fixed warnings for unplanned H2 headings/unrouted included references. No automatic routing or relevance judgment. Exact plan bytes bind planned build/review currency, including addition/removal and whitespace edits; source changes during build refuse before publication.

  • N-1 CLI: existing commands/required usage retained; paper plan set|show are additive. Plan-free builds continue to emit evidence v1; newer check reports may add hygiene/settings fields.
  • N-1 MCP: existing tools/annotations retained; ares_paper_plan_set and read-only ares_paper_plan_show are additive and use the shared handlers. Input/frame budgets are unchanged.
  • N-1 study/ledger formats: study and ledger envelope versions stay unchanged; paperPlan: 1 is new, with additive paper.plan.set receipts. Plan-free builds keep paperEvidence: 1; planned builds use paperEvidence: 2 with a raw plan hash and an optional plan hash on paper.built. Current readers keep v1; older evidence readers refuse v2 before rewriting it. 0.3.0 supplies the compatible minor reader; tagging/publication remain separate release actions. Installed-package/network N-1 remains a separate CI check.

• Writing points (#98): optional section points declare shape-only claims, required scoped citations and local card/attempt existence links. Every anchor occurrence in its own section checks its own window up to any next well-formed anchor or planned-section boundary; satisfied copies cannot mask incomplete ones. Plans with any point store paperPlan: 2, with globally unique point ids, 40 points/section, 500 Unicode characters/claim and the existing formatted 64 KiB total. Point-free plans retain v1 bytes/check behavior. No prose generation, claim-to-prose match or support/entailment judgment is added. Planned evidence remains v2 because its raw plan hash already binds point edits.

  • N-1 CLI: existing commands and required usage remain; writing points use the existing paper plan set|show and paper check surfaces. Point-free operations keep their prior behavior.
  • N-1 MCP tools: existing names and annotations remain; the plan schema adds optional points and version 2 with the same shared validation as CLI. No new tool or caller approval flag is added.
  • N-1 study/ledger formats: study and ledger envelope versions are unchanged. Section-only plans remain v1; 0.3.0 supports both plan versions. Published 0.2.1 has no plan reader and ignores both; intermediate v1-only plan readers refuse v2 without rewriting it. Existing plan-bound paperEvidence: 2 is retained, with no evidence-format bump. 0.3.0 supplies that compatible minor reader; tagging/publication remain separate release actions.

Install

bun add -g @staix/agent-research@0.3.0

Published with npm OIDC trusted publishing and provenance. The validated tarball and its tag/commit/SHA-256 manifest are attached. SHA-256: 608adfe513e662c311e7596a2a9937ad7e3539907200697eee69e5fd61cc9cfc.