628b5f2 accepted a cursor only if re-encoding the parsed key gave the
same string. That closed the format both ways: any encoding change, even
a compatible one (an optional field, key order, to_rfc3339 shared with
API responses), would turn cursors issued by a replica of the other
version into 400 during make rolling_update, which the tests cannot see.
decode_cursor now checks the fields one by one: v must be exactly the
integer 1, t and i must be strings, i must be in the server's notation
(lowercase 8-4-4-4-12). Unknown fields are ignored, so a tampered cursor
is still a 400 while the format stays open for compatible changes. The
rule records how to change the format: a new CURSOR_VERSION, with both
versions accepted while replicas are replaced.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
decode_cursor checked only for KeyError, TypeError and ValueError, so a
server-issued cursor whose item id was replaced with [], {}, 123 or
false crashed UUID() with AttributeError and answered 500. It now checks
the types of "t" and "i" before parsing and accepts only the exact
string the server would issue for the parsed key: re-encoding must give
the received cursor, so v=true, an extra field or the id in another
notation is a 400 instead of a page.
pydantic's UUID also accepts ids without hyphens, with the urn:uuid:
prefix and in braces, wider than the contract's format: uuid. chat_id in
the path of the three chat endpoints and member_ids elements now use
UuidIn, which requires the 8-4-4-4-12 form in any case. Response models
and the OpenAPI schema are unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add black-box tests for the strict-id-validation change: a server-issued
cursor with one field changed (non-string or non-canonical item id,
v=true, extra field) on both lists, member_ids with values of other JSON
types, a non-array member_ids and other UUID notations, and chat_id in
the path of the three chat endpoints. Sync the change's delta specs into
api-conventions, chats and pagination so the coverage check knows the
new scenarios.
The cursor and UUID-notation tests fail on the current code by design;
the fix follows in the next commit.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The change moves to openspec/changes/archive/2026-10-13-fix-known-issues.
Its delta requirements join the main specs: graceful-shutdown "Остановка
во время старта", load-benchmark "События Docker профилей отказа и
замены", student-tests "Доказательства исключений сверки в репозитории"
and "PostgreSQL стенда отказов без аварийных перезапусков". AGENTS and
REPORT now say all eight lab 3 changes are archived and none is active.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Evidence section "Правки по verify": stop-at-start under system Python
3.9.6, cache-check with and without --require-test-keys, auth-storage,
the postgres log read failure path, student tests, failure checks and
the quick failover and rollout profiles on f02694e. The REPORT header
lists what changed after the clean clone commit.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
REPORT: 133 and 129 + 4 in the clean clone section, the postgres log
summary of failure_checks, the isolated count on the final code.
AGENTS: do not copy lab 3 evidence, cache-check --require-test-keys.
script-failures: the closed KNOWN_ISSUES entry points to decision 7.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
stop_stream terminates the events CLI, waits 10 s and kills it after
that. The rollout profile starts k6 inside the try, so a k6 start
failure no longer leaves the project events stream running.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docker compose logs runs with check=False; a non-zero exit prints
"postgres log unavailable" and fails the run instead of being reported
as a setup failure.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cache-check gains --require-test-keys: without keys of the test database
it fails instead of passing, and a plain PASS now says the temporary
database was not checked. The coverage exclusion names the flag.
auth-storage logs in only the first user, as the design says.
stop-at-start installs its signal handlers right before the try that
restores them and kills docker logs -f when reading is interrupted.
The student-tests rule warns that copied evidence keeps the check green.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The *.log rule kept LB, rollout script and 5xx logs of committed
labels out of git while REPORT.md cites them. The 59 logs (556 KB)
hold no tokens, passwords or host paths; quick-* labels stay ignored.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Report the failover ranges strictly over phases 1-5 with phase 06
apart, add per-window memory peaks to the failover table, describe
which intervals the window maximum covers, and note the per-second
rows and per-request zeros of the taken labels fixed in f34cb9a.
Record the design findings, the raw logs ignored by git as a known
issue, and the checks after the fixes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The samples.csv row of an interval that touches the start of a freeze
now gets the window of its unfrozen part, as the window aggregates do
since the thaw correction. CPU per successful request is no longer
computed for a container absent from the window. The definitions in
the summary describe which intervals the window maximum covers.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A sample interval that crosses docker pause or unpause carried the CPU
spent before the pause and the burst after unpause into the failover
window by proportional split. Use the pause and unpause moments from
Docker events so that interval CPU lands outside the frozen span.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Run bench/sampler.sh in a new scan mode (cgroup walk, no network, no
psql or LB polling) for the whole load of the failover and rollout
profiles. bench/resources.py turns the samples into per-window CPU,
throttling and memory of every component and the VM, with
samples.csv, resources.csv and summary sections; CPU per successful
request only in steady windows. Check the peak CPU budget before the
stand starts.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Fix the findings of the final REPORT.md review: prerequisites, the
defence scenario, swap sources, the single explanation of the R* drop
at PostgreSQL 0.5 CPU, known defects in the limitations, a dead link,
stale counts and references. Remove the device name from evidence.
Remove the lab plan now that every change is archived: its decisions
live in REPORT.md and the archived designs, live references point
there, and AGENTS.md drops the transitional section.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
datetime.UTC exists only since Python 3.11, so make instances failed on
the macOS system python3 listed in the report prerequisites. Use
timezone.utc and postponed annotations instead.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Fill the remaining report sections: clean clone run with versions and
prerequisites, lab 2 carry-over, transaction boundaries, teacher
agreements, skeleton variable mapping, rubric cross-check, experiment
overview, limitations summary, sources and AI usage. Record the clean
clone run of every documented command on default ports.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sync load-benchmark (series comparison table, track 1 before/after
rules, db4 series) and service-configuration (default pool 10 + 0)
into the main specs, move the change to the archive and drop it from
the transitional state in AGENTS.md.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Fix the two-step threshold (x1.118), CPU-per-request spread and
PostgreSQL ranges in REPORT.md and design, record the LB side check
(lb_chkdown, error_codes) in evidence, add the db4 series to the
load-benchmark delta, refresh AGENTS.md, bench.md, PLAN.md and
proposal, and log the swapouts_delta passport defect.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>