mirror of
https://github.com/morluto/rea.git
synced 2026-11-05 14:26:07 +00:00
212063ff6c2aee2548aeabc111179e1c56daa4c0
3
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
 Edgar ArakelyanandClaude Opus 5.5
|
212063ff6c |
fix(browser): address review of saved values and slug spellings
- Basic credentials and values saved with `secret: true` are redacted however short, as declared secrets are; page values keep the 8-character floor - a literal Basic password other than empty is refused, since Evidence records literals as written - `save_response` takes only a request the step starts, so an earlier autosave cannot answer it, matches its path as the browser spells it, and stops watching requests when the step ends - saving reads are bounded: a request step streams its answer up to 4,000,000 characters; a UI step refuses a larger received size unread - goto placeholders fill the destination URL before structured query values join it - reading a composed string stops at the reading cap before comparing or allocating more - a slug's `&` spelling follows every create the plan accepted and every held entity; direct slug rules and composed strings take it from held entities when the create slugs none, and a slug rule they contradict is not learned Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
Edgar ArakelyanandClaude Opus 5.5
|
31d6e1d978 |
fix(environment): learn addresses a UI-made create spells, and check templates on later creates
Recording through the UI let Grafana generate folder uids, and three write model gaps then served folders whose address kept the first folder's slug: - a template around a generated value won over a composed string that also reads the title's slug; the composed string now wins when it reads a field besides the template's value - later creates checked composed strings against their own answers, but not templates, so coverage served a template a later folder contradicted; a template is now checked the same way - a slug dropped `&`, which Grafana's Go slugs spell as the word; a slug rule or part learns `ampersand: "and"` from the call that shows it, and calls that slugged no `&` agree with either spelling An address whose uid equals its title's slug could come from either field. The entities the type holds now pick the one reading they share, and when they cannot, a later create that tells the fields apart lends its composed rule to the first create, whose body contract is learned again with it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
aba487eec0 |
feat(environment): learn creates from every call, with sorted arrays and referenced entities (#7034)
* feat(environment): explain values an application derives from other fields
Prompt-built environments withheld creates whose responses carry values the
application derives deterministically, which the write model kept as
constants or could not match across calls:
- A composed string is literal text plus parts read from the fields other
rules write: a field's value, its slug, or a clock's calendar digits. A
create composes a string only when another entity of the type spells it
the same way and none spells it otherwise, and never from two sources
serving could tell apart; an update composes an unsent change from members
stored as sent and unchanged fields that also spell its value before the
call. A composed field no longer pins the members it reads.
- A trimmed clock format drops trailing fraction zeros, as Go spells
nanoseconds. It is learned from the type's values, a later create or a
later update, and spreads to the plan's other clocks unless a value shows
a fixed width.
- A large integer no entity of the type holds, among distinct ones of the
same length and kind, is a generated unique value, served as a seeded
integer.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(environment): record the derived-values verification
Gates, tests, write plans over 69 recorded captures and served write tasks on the baseline and on this branch.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(environment): learn a create plan from every call
A later create the plan does not take is explained on its own and merged when both calls show the same fields, every field both rule they rule alike, and a field neither rules holds one value: members either call sent are accepted, only those every call sent are required, and an echoed member a call left out takes the value that call stored, kept in the body's defaults.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(environment): sorted arrays, referenced entities and nested view keys
- An echo is `sorted` when the application stored the sent strings in
code-point order; serving stores them sorted, and a plain echo and a
sorted one agree in update and create plans.
- A `reference` is an object field holding fields of the entity a sent
member names, as the state holds it. The member is accepted with any
value; replay and serving look the entity up, and serving refuses a call
naming one the environment does not hold.
- A view names in `nested_fields` the keys it always shows of objects it
shows with fewer keys than an entity stores; a stored object it never
recorded renders with them. The view spelling learner moves to its own
module.
- Every later create, not only one the plan refuses, is merged into its
plan when it agrees, keeping the plan's rule order.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(environment): keep clock spellings, linked ids and word boundaries honest
- A later update's clocks take the plan's spelling, sibling-trimmed
clocks included, wherever the call's values fit it, so an update whose
later call trims only one of two clocks is served.
- A held value that ends its fraction in a zero keeps a create's clock
at a fixed width, whatever order the held spellings come in.
- A large integer that another field of the created entity also holds
is linked, as a repeated token is: it is never unique, and the create
is withheld as unexplained-change.
- Composed parts are delimited by whole characters through the shared
joinsBefore/joinsAfter, so an astral letter joins a match to its word.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(environment): keep a same-width fixed clock out of trimming
A held .123456780 beside a held .12345678 keeps the create's clock at
nine digits in either order; the cases fail on
|