Repository navigation
fix: a write refuses importance outside 1-10 on every type (#1537) - #1570
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013BnEiXVYWrA6aMb1ajpfSw
The range rule sat on EventEntry.validation_errors only, so every other type stored importance 99 and qa validate then warned about what Pyrite had just written. It now sits on Entry.validation_errors, which the one write gate (KBService._validate_write) already calls for every type: create, update and add refuse it; a value already on disk is kept and reported, as for events. EventEntry's rule name, message and on-disk exception are unchanged. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013BnEiXVYWrA6aMb1ajpfSw
verify-red found them passing without the fix, as intended: they guard against over-refusal and pin EventEntry's behaviour. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013BnEiXVYWrA6aMb1ajpfSw
The range row moved to Entry.validation_errors, which runs first; keep the order an event refusal has always had (date, then importance). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013BnEiXVYWrA6aMb1ajpfSw
|
Stopped: my push is refused by the pre-push hook, and the red is caused by this change. Pushed head is still the claim commit 1fe21e2. Three local commits are not pushed: the fix, the controls and the event row-order commit. The full pre-push run:
Both build a journalism-investigation KB, write The brief says to stop and report instead of rewriting Local state: new test file 639 passed, verify-red Generated by Claude Code |
|
Conductor's answer to the stop on #1570 (2026-11-17). You stopped in the right place; thank you. This is a directed answer, not a review round. The property to keep. Each of the two tests pins something about plugin validators, and
Your change makes the model answer first for importance, which is the point of #1537, so neither test reaches a plugin validator any more. Keep what each pins; change only the trigger. Do not make them expect the model's refusal: that would leave both properties untested. What to do.
Then the full pre-push run again; push without 🤖 Written by the maintainer's conductor agent (Claude Code) |
…tance (#1537) The two test_plugin_contract tests pinned plugin-validator behaviour using importance=99; the model now refuses that first. Keep what each pins: a rule-less validator message survives (own registered plugin), and a plugin-only error (payment without amount) is a SchemaViolationError. Each was shown red with its defect planted. Add the journalism-KB case to the parametrised file and say the error_code change in the fragment. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013BnEiXVYWrA6aMb1ajpfSw
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013BnEiXVYWrA6aMb1ajpfSw
|
Report posted at dc213bd Generated by Claude Code |
|
Conductor, Opus cold read of dc213bd, 2026-11-17. Read-only; CI not re-run ( Verdict: one fix round (round 1), sent to the worker's session. Holds (reader, by planting or reading): the rule is on the base class and the one write gate applies it to every type; only Does not hold: a value already in a file never stops a write that does not set it.
Text that is not yet true.
Notes, not in the round (follow-up issues when the round is in): create turning a non-number into 5 without a report; The round asks for the property over every kind of value a file, MCP or |
…ent (#1537) validate_importance caught ValueError and TypeError but not the OverflowError int(float('inf')) raises, so a file holding importance: .inf locked every update of that entry (and pyrite add) with NO_OUTCOME/INTERNAL: the opposite of 'a value already in the file is kept and reported'. It now answers False for anything int() cannot read, and a bool is not a number. A blank or null importance is absent (no row) on every path, instead of a 'kept' warning about None after pyrite add accepted it. Adds one cell per kind of value (23 kinds x note/event x CLI/MCP x file, set, create, add), each with its verdict written from the property. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013BnEiXVYWrA6aMb1ajpfSw
|
Round 1 report posted at 55fb3fe Generated by Claude Code |
|
Conductor, Opus delta read of 55fb3fe (the round-1 commit, d0db45f..55fb3fe), 2026-11-17. Read-only; CI not re-run (it was still running on this head when the read finished). The reader wrote its own probes; the conductor re-ran each line marked "ran" on 55fb3fe and on dev 0d4bcd4. Verdict: round 2, sent to the worker's session. It is the last worker round; what is left after it is stated as a limit for the maintainer. Round 1's property holds: the check never raises, and a value already in a file never stops a write that does not set it. The reader tried 24 kinds beyond the worker's table (1e400, Does not hold: a write that is accepted never leaves in the file an importance outside 1 to 10 (the header of the new test block).
Text: the 30-digit sentence should say that the command answers Round 2 asks for the range edges that are not whole (10.000001, 10.5, 10.9, 0.5, 0.99, -0.5, 1e1, Notes, not in the round (one follow-up issue after it): create turning a non-number into the default without a report; REST's top-level 422; the "kept" row's rule name; Merge: the maintainer's (it changes what every write accepts). Next: a delta read of round 2. |
|
The 30-digit defect named in the delta read is filed as #1584 (a bug in the write path's index step, older than this PR). Round 2 points the four xfail cells and the fragment's sentence at it. |
…er first (#1537) validate_importance passed int(importance) to the range check, so 10.9 and 10.5 passed (accepted range was 1 up to but not including 11) while 0.5 was refused. Numbers are compared as they are; strings stay whole-number text. 5.5 stays accepted (the range is the rule, whole-ness is not checked). Adds the edge values (10.000001, 10.5, 10.9, 0.5, 0.99, -0.5, 1e1, "10.9", "1e1") and the null-set column to the matrix, names every changed answer in the fragment, and makes the 30-digit xfail cells fail as expected only for the index overflow (#1584). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013BnEiXVYWrA6aMb1ajpfSw
|
Round 2 report posted at d508760 Generated by Claude Code |
|
Conductor, Opus delta read of d508760 (the round-2 commit, 55fb3fe..d508760), 2026-11-17. Read-only; CI not re-run ( Verdict: round 2's property holds. No third round. What remains is words (five sentences), sent to the worker as a words-only change. Holds (reader ran on d508760 and on dev 0d4bcd4; the conductor re-ran the create and
Words that are not true on d508760 (conductor ran each on the head and on dev)
Limits, stated, all on the safe side (none leaves an out-of-range number in a file; for the follow-up issue, not this PR)
Not run by the reader or the conductor: the journalism-investigation Next: when the words-only push is green, this goes to the maintainer to merge (it changes what a write accepts on every type), with the limits above. |
…ch event rows are controls (#1537) Fragment: a create still cuts a decimal and stores true as 1; a quoted empty string is not blank. Test header: name the event controls and the event cells that changed. Words only: the test file's code is unchanged. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013BnEiXVYWrA6aMb1ajpfSw
|
The limits listed in the delta read are filed as 1588 (a create coerces what an update refuses, and seven smaller ones). |
|
Words-only change pushed at 0580fac Generated by Claude Code |
|
Conductor, 2026-11-17: ready for the maintainer at 0580fac.
Recommendation: merge. |
Groom 2026-11-16
Automated groom (architect agent, working for the maintainer). Written so someone new to Pyrite can start from this issue alone. "Checked" means I ran the command or read the line on bccf8f7.
The user's model. "Importance is 1 to 10. If I send 99, Pyrite tells me, whatever kind of entry it is."
The implementation model. One range rule, on the base entry, reached by every write through the one write gate. Design principle 8 (
kb/design.md): each rule lives in one place.The difference today. The rule sits on one subclass. The gate that calls it already runs for every type.
Contracts that apply
kb/design.mdprinciple 8: a rule is enforced at the single point everything passes through.kb/design.mdprinciple 2: a hand-edited file is never refused or repaired for what it already holds. An update that leaves a bad value alone must still succeed.docs/json-contracts.md, "canonical error shape": the refusal isVALIDATION_FAILEDwith anerrorsrow (field,rule,message,expected).kb/maps/types-and-schema.md: its first invariant (write path andqa validateagree) covers enums only. No sibling for ranges is written anywhere; 0.26.4 theme T1: a type is one schema per KB #1528 slice T1-4 writes it. Not this issue's job.What the code does today (checked)
pyrite/services/kb_service.py:759KBService._validate_writeis the write gate. Create (:1589) and every update path (:1724,:2321,:2350) call it, and it callsentry.validation_errors()for every type. So the enforcement point exists and every surface passes it.pyrite/models/core_types.py:198EventEntry.validation_errorsis the only place the range is checked on a write (:221-232, callingvalidate_importance,pyrite/schema/validators.py:103).pyrite/models/base.py:724Entry.validation_errorschecks id and title only.importanceis a base field (:287), carried by all of the about 40 entry classes (13 in core).extensions/journalism-investigation/src/pyrite_journalism_investigation/validators.py:142-150has its own range check, which runs only in a KB registered with that plugin's type.tests/test_plugin_contract.py:403-446uses it.pyrite/services/qa_service.py:915_check_importance_rangeand:1179report the same rule after the fact, as a warning.pyrite/server/schemas.py:467,:484,ge=1, le=10). MCP only describes it (pyrite/server/tool_schemas.py:784,:844,:874). The CLI has no bound on--importance(pyrite/cli/entry_commands.py:318,:565) or on-f importance=.importance: 99hand-written into an event file,pyrite update vote -k res -f location=Hallsucceeds and returns a warning:"rule": "model_validation", "message": "Importance must be 1-10, got: 99", "note": "violation already on disk; kept". That is_validate_write'sprior_model_errors(:783-807). Moving the rule to the base class gives every type this behaviour with no new code.Invariant and surfaces
A write never stores an importance outside 1-10, on any type, by any surface. A value already in the file is reported, not refused.
create/update-f importance=create/update--importancekb_create,kb_update99, then77); not re-run hereimportanceimportanceinsidemetadatapyrite add <file>:1589), not runindex syncqa validatereports itShapes (parametrise the test over these):
grep -rnE "^class \w+\(" pyrite/models/*.py extensions/*/src/*/*.py | grep -c Entrykb.yamlalone (GenericEntry)"7";"high"; absentadd_validate_writecallersimportance:in this repo's own files<1-10>)git grep -hE "^importance:" -- '*.md' | sort | uniq -cOptions
EventEntry.validation_errorstoEntry.validation_errors(recommended). About ten lines moved. Every type and surface is covered by the gate that already runs; the on-disk exception comes with it.kb_service.pyis not edited._validate_write. Same effect, but it editskb_service.py, which is the busiest file in the tree this month (0.26.4 themes: order of work #1533, "Files that force a series"), and puts a model rule in the service.type_spec). Right end state, about three weeks out, andimportanceis a base field whose range does not depend on the type.Open questions
qa validatereportimportance_rangeas an error, now that a write refuses it? Today it is a warning. Leave it unless the maintainer says otherwise; note what you find.tests/test_plugin_contract.py::TestValidateWritePrefersMessageneeds another rule-less validator to exercise.pyrite addof a hand-written file withimportance: 99: refused, as an event file is today. Say so in the changelog fragment. If you find that this breaks an import path, report it instead of working around it.Pointers
pyrite/models/core_types.py(EventEntry.validation_errors),pyrite/models/base.py(Entry.validation_errors,unrepresented_frontmatter),pyrite/services/kb_service.py(_validate_write, read only),tests/test_enum_enforcement.py(a write-gate test over surfaces),tests/conftest.py(cli_world),tests/_world.py.Checked versus assumed
pyrite add.validation_errorswithout callingsuper()(grep finds one override,EventEntry, which does call it).pyrite/,extensions/or the shipped templates.pyrite/models/base.py,pyrite/models/core_types.py, one new test file, onechangelog.d/*.changed.mdfragment. About 60 lines with tests. If it grows past four source files, stop and say why.Fixes #1537
Report
Done. The range rule moved from
EventEntry.validation_errorstoEntry.validation_errors(pyrite/models/base.py,pyrite/models/core_types.py). The one write gate already calls it for every type, so create, update andaddrefuse an importance outside 1-10 and write nothing. A value already on disk is kept and reported ("violation already on disk; kept").pyrite/services/kb_service.pyis not edited. Branch isfix/1537-importance-range-every-type(named in the brief), not the session's default branch.Red first. On dev the new file gave
381 failed, 258 passed, and no event row was among the failures.scripts/verify-red.shon the branch:verify-red: 381 red · 0 import-only · 0 unexpected pass · 0 n/a · 258 control. The controls are the event rows, event subclasses, and the in-range and absent values (an over-refusal guard).validation_errorsoverrides. A grep ofpyrite/andextensions/finds two definitions:Entry(base.py) andEventEntry(core_types.py).EventEntrycallssuper(). No class overrides it withoutsuper(), so the groom's assumption holds.One change beyond the groom. The importance row now comes from the base class, so an event's rows would have come out
importance, date.tests/test_write_refusal_names_the_field.pypins["date", "importance"], soEventEntrynow puts its date row before the importance row, as before.Surfaces (the groom's table).
create/update-f importance=VALIDATION_FAILED, exit 1, nothing writtenkb_create/kb_update--importanceimportancepyrite/server/schemas.py) is unchangedimportanceinsidemetadatapyrite add <file>personwithimportance: 99(the test also covers an event file); no file is writtenindex syncqa validatestill reports itTypes covered. Surface tests run over the core registry, one plugin type (zettelkasten) and a type declared only in a
kb.yaml(widget), on both the CLI and MCP. A separate test runstest_every_entry_class_carries_the_ruleover every registered class (core, all plugin, generic), so a new type cannot skip the rule.pyrite add. It refuses a hand-writtenimportance: 99on a non-event, as it already did for an event, and the changelog fragment says so. I searchedpyrite/andextensions/for importance values outside 1-10 and for computed values: none. No import, init-template or example path stores one, so there is no "Decision needed" for this.Caller-visible change on a
journalism-investigationKB (create ... -f importance=99on aperson):SCHEMA_VIOLATIONVALIDATION_FAILEDkb_createSCHEMA_VIOLATIONVALIDATION_FAILEDSchemaViolationErrorValidationErrorerrorsrow{field, message}, no rule{field, rule: "range", message, expected: "1-10"}The fragment says so in one sentence, and
test_a_journalism_kb_refuses_importance_99_with_the_models_answerpins it on both surfaces.The conductor's directed change to
tests/test_plugin_contract.py.TestValidateWritePrefersMessagenow registers its own plugin, with a validator that returns amessageand norule. It asserts the message survives. Plant: make_validate_writeignoremessage(theelif message:branch inkb_service.py). Red:TestValidateWritePrefersMessage::test_a_rule_less_validator_message_is_not_lostandTestValidateWriteKeepsEnumDetail::test_a_ruleless_error_uses_its_message.test_plugin_validator_error_is_non_zero_not_silentnow uses apaymenttransaction with noamount, which only the journalism validator enforces. Plant:run_validatorsreturns[]. Red: that test, plus 6 others in the file that depend on plugin validators.kb_service.pyis not in the diff.rule.Tests.
3 failed, 23510 passed(the three were the two plugin-contract tests plus the row-order one, which is now fixed).1942 passed. This covered the new file,tests/test_enum_enforcement.py,tests/test_plugin_contract.py,tests/test_response_text_is_pyrites.py,tests/test_write_refusal_names_the_field.pyandextensions/*/tests.Pushed SHA.
dc213bd142b7d3be6e40eff8f202bf50af09151a, equal togit ls-remote origin fix/1537-importance-range-every-type.origin/devwas merged in (a merge commit) before the last push.Unsure.
--no-verify.highas a value on create or-fupdate is not in the refused set: events already stored the default for it, so I kept that behaviour. Only a hand-writtenhighis kept and reported.qa validatekeep reportingimportance_rangeas a warning? I saw it still reads the index, so it only reports hand-edited files now.Left.
validators.py) is now unreachable on a write. 0.26.4 theme T2: a plugin passes the same single points as core #1529 owns removing it, so it stays.kb/maps/types-and-schema.mdis not touched (0.26.4 theme T1: a type is one schema per KB #1528 T1-4).tests/), so none was removed.Learned.
super().SchemaViolationErroris a subclass ofValidationError, so callers catching the latter see no break.Captured in.
tests/test_importance_range_on_every_type.py(every item above that is behaviour),tests/test_plugin_contract.pydocstrings, the changelog fragment, and the comment on the date-row insertion inEventEntry.validation_errors.Tokens. Not reported.
Fixes #1537
Report, round 1
Head
55fb3fe698bfb71ae35b8e0cc8eacbbd25aaf185(git ls-remote origin fix/1537-importance-range-every-typereturns the same SHA).origin/devis merged (a merge commit). The pre-push hook's full run passed.The value matrix
I measured every cell with one script on dev (the head with
base.pyandcore_types.pyput back toorigin/dev) and on the new head, through the CLI and through MCP_dispatch_tool. The events give the same answers as the notes on the new head. On dev, the only event differences are the crashes and the refusals the event rule already had.Cells are
dev -> head(note; an event gives the same answers on head).ok= succeeds,+W= with the importance warning,refused= VALIDATION_FAILED,CRASH= NO_OUTCOME/INTERNAL; (x) = what the file then holds.Classification of every changed or crashing cell:
.inf/-.infon disk and onadd(CRASH to kept+warning / refused);.infset over MCP (CRASH to refused);true; null and blank on disk.tests/test_importance_range_on_every_type.py, one per kind × note/event × CLI/MCP × file / set / create / add (test_a_value_already_on_disk_never_stops_an_update_of_another_field,test_a_set_importance_is_refused_or_in_1_to_10,test_a_created_importance_is_refused_or_stored_in_1_to_10,test_add_refuses_a_file_holding_a_bad_value_and_accepts_the_rest,test_the_check_never_raises_and_says_row_or_nothing). TheKINDStable has one row per kind with the verdict written by hand from the property; a new kind cannot be added without a verdict.NO_OUTCOME/INTERNAL, on dev and on this head. The check answers with a row; the crash is in the index upsert (pyrite/storage/crud.pytobase_backend.py,OverflowError: Python int too large to convert to SQLite INTEGER) after the file has been written. It is fourxfail(strict=True)cells so it flips when fixed.int(5.5)is 5, which is within the stated limit.What I decided
importanceare absent: no row, on every path (Entry.validation_errorsinbase.py).pyrite addalready accepted them; the "kept" warning about None on every later update is gone.importance: ""(an explicit empty string) is a non-number and gets a row. Explicitly setting null over MCP writesimportance: nullas on dev; it reads as absent..inf,-.inf,.nanare non-numbers: a row, never an exception. The mechanism:validate_importance(pyrite/schema/validators.py) is the one place a value becomes "in range or not", and it cannot raise. It catches OverflowError besides ValueError and TypeError. A bool is not a number (trueused to pass as 1), sotrueandfalseare rows.qa_servicecalls the same function, so the QA check cannot raise on one either.Final fragment (
changelog.d/1537-importance-range-every-type.changed.md)Tests
tests/test_importance_range_on_every_type.py:1005 passed, 4 xfailed. With the round-1 change removed (the dc213bdvalidators.pyandbase.pyput back):48 failed, 957 passed, 4 xfailed(12 set, 20 on-disk, 6 add, 10 check).24118 passed, 256 skipped, 7 xfailed.tests/test_plugin_contract.py,tests/test_write_refusal_names_the_field.py,tests/test_response_text_is_pyrites.pyandextensions/*/teststogether:2214 passed, 4 xfailed.pyrite/services/kb_service.pyis not edited.Unsure
importance: trueon disk from silent to a "kept" warning, andpyrite addof it from accepted to refused. The fragment says so.pyrite/models/base.py,pyrite/models/core_types.py,pyrite/schema/validators.py), under the four-file limit;kb_service.pyis untouched.update -f importance=highon a non-event is refused on this head (for events it was already refused on dev).Left (one line each, for follow-up issues)
high,.inf,true) into 5 or 1 without a report;update -f importance=5.5writes 5.5 as given;importanceanswers FastAPI's own 422, not Pyrite'sVALIDATION_FAILEDrow;rule: model_validationwhere the refusal row saysrange;qa validatedoes not see a non-number on disk;importanceon disk crashes the index upsert after the file is written (dev as well).Learned
validate_importancehad no OverflowError guard, soint(float('inf'))crashed every write path that touched the entry, on events on dev too (validators.py).Captured in
The
KINDStable and its five tests; the docstring ofvalidate_importance; the comment on the blank/null rule inEntry.validation_errors; the fragment.Tokens
Not reported.
Fixes #1537
Report, round 2
Words-only change at 0580fac (fragment sentences and the test module header; no code or assertion changed).
Head
d508760d63fef668c62893627b4574b76130d74f(git ls-remote origin fix/1537-importance-range-every-typereturns the same SHA).origin/devwas already merged. The pre-push hook's full run passed.New rows and the null-set column (
dev -> head, note; an event gives the same answers on the head)Same legend as round 1. The null and blank rows are the "write sets null or blank" column: the CLI cells are
-f importance=nulland-f importance=(text), the MCP cell is"importance": null.Events: same as notes on the head for every row above
Event rows that differ from the note on dev (the null set): [('null', 'VALIDATION_FAILED | importance: 5', 'ok | importance: null'), ('blank', 'VALIDATION_FAILED | importance: 5', 'ok | importance: null')]
Verdicts, written by hand from the property (they are the
KINDSrows): the six non-whole edge numbers are "bad" on disk, on set and on add (a number is compared as it is);1e1is a whole-valued float, "good" everywhere; the string"10.9"is bad on every surface; the string"1e1"is bad on disk and over MCP, and good on the command line, because the CLI reads numeric text as a number (-f importance=1e1writes10.0); create is "refused, or what is stored is in 1-10" (a create cuts a decimal to a whole number in the model before the check, which is how 10.9 became 10 on dev too).5.5stays "good" and its row now says it is the stated limit, not the rule.What I decided
validate_importance(pyrite/schema/validators.py) compares ints and floats as they are, reads a string only as whole-number text, triesfloat()for any other type, and still cannot raise. So10.000001,10.5,10.9,0.5,0.99and-0.5are refused on the head, and5.5is still accepted as given.kb_updatewith"importance": nullis accepted on a note and on an event; the file then holdsimportance: null, which reads as absent. It follows from "null is absent". On dev an event refused it. The CLI texts-f importance=and=nullare strings, refused on every type. Pinned bytest_an_mcp_update_setting_importance_null_is_accepted_on_every_typeandtest_a_cli_update_setting_importance_to_blank_or_null_text_is_refused, and named in the fragment._IndexOverflowErroronly for theNO_OUTCOME/INTERNALanswer with the file rewritten, and thexfailhasstrict=True, raises=_IndexOverflowError. Any other failure is a real failure. The reason names An update of an entry the index cannot store writes the file, then answers NO_OUTCOME (a 30-digit importance) #1584.NO_OUTCOME(CLI) orINTERNAL(MCP), and the index has no row for the entry (I checked: it had none before the update either, because the indexer cannot store the value). Same on 0.26.3.Final fragment (
changelog.d/1537-importance-range-every-type.changed.md)Tests
tests/test_importance_range_on_every_type.py:1155 passed, 4 xfailed. With this round's change removed (the round-1validators.pyput back):38 failed, 1117 passed, 4 xfailed(14 set, 12 on-disk, 6 add, 6 check).24268 passed, 256 skipped, 7 xfailed.tests/test_plugin_contract.py,tests/test_write_refusal_names_the_field.py,tests/test_response_text_is_pyrites.pyandextensions/*/tests:2364 passed, 4 xfailed.pyrite/services/kb_service.pyis not edited.Unsure
nullrefused on the CLI": it is one rule (null is absent; text is a string) but reads as two answers."1e1"as a string is refused over MCP and accepted on the CLI. That follows from how each surface hands the value over, and the matrix pins both.base.py,validators.py); round 2 touches one (validators.py); the whole change touches three (base.py,core_types.py,validators.py).Left (one line each, for follow-up issues)
5.5written as given;model_validationvsrange);qa validatereads the index's coerced value, so it stays silent about what an update now warns about;!!str 7gets a row;Learned
validators.py).xfailwithoutraises=accepts any failure as the expected one; the cell has to raise its own marker for the known failure.Captured in
The
KINDSrows and the two null-set tests; thevalidate_importancedocstring; the_IndexOverflowErrorcomment andraises=; the fragment.Tokens
Not reported.
Fixes #1537
Generated by Claude Code