finding(runtime): through the @objectstack/hono catch-all, PUT /meta/:type/:name ignores If-Match, If-None-Match and ?mode=draft — a stale token writes (200, not 409) and a draft save lands ACTIVE

Filing gate: ① a reproducible defect, class (a), a wrong answer at the published @objectstack/hono createHonoApp door, measured by a probe. Found by #22114's dev (PR #22126, report 6051172466, out_of_scope_findings[0], and the round-1 host-wiring read in 6050372265), filed by the domain:spec seat 3 (seat post #18883, session_01RPo7FUd6bSnAfkWMAKi848). ⛔ Not graded or routed here; ⛔ not a claim.

Contract

ADR-0008: PUT /api/v1/meta/:type/:name takes an opt-in If-Match, and a stale one is refused 409 METADATA_CONFLICT. PR feat(meta): the /meta item read serves the version token, If-None-Match: * pins a first write, and the 409 carries currentVersion #22126 (meta(/meta door): the draft read serves no version token, so no client can pin its first draft save with If-Match; the 409 METADATA_CONFLICT body names the current version only in prose #22114) adds If-None-Match: * (expect no row) to the same door.
?mode=draft saves a draft and leaves the active row alone.
RestServer (packages/rest/src/rest-server.ts) honours all three today.

What is measured

The dev ran a scratch probe at PR #22126's head e2a28fadf. It mounted createHonoApp({ kernel, prefix: '/api/v1', cors: false }) over the real ObjectStackProtocolImplementation, on ObjectQL and better-sqlite3 :memory:, with identity stubbed to manage_metadata. Requests went through app.request:

request	catch-all answer	`RestServer` answer
`PUT /api/v1/meta/view/case_grid`	200 (`v1`)	200
`PUT` again, with `If-Match` = the stale first token	200, written (row reads `v3 …`, seq 3)	409 `METADATA_CONFLICT`
`PUT` with `If-None-Match: *` over the existing row	200, written	409 (with PR #22126)
`PUT …?mode=draft`	200, receipt `state: 'active'`; the row lands ACTIVE	a draft row; active untouched

Where it is (read in source by the dev)

createHonoApp's ${prefix}/* catch-all (packages/adapters/hono/src/index.ts:725 app.all, :739 dispatcher.dispatch(…, c.req.raw)) reaches handleMetadataRequest(deps, path, _context, method, body, query) (packages/runtime/src/domains/meta.ts:874). That function takes no headers.
Its PUT branch (:1274) calls protocol.saveMetaItem({ type, name, item, organizationId, writeFace: 'meta-dispatch', ...packageId }) (:1430–:1434) with no parentVersion and no mode. meta.ts holds 0 occurrences of if-match / If-None-Match / parentVersion.
Who mounts it. objectstack serve / os dev mount createRestApiPlugin and then the dispatcher plugin's explicit routes, with no ${prefix}/meta route (dispatcher-plugin.ts:1283–:1285), so /meta writes there are RestServer's. No app, example or package in this repository calls createHonoApp. dispatcher-plugin.ts:1321 names it "the @objectstack/hono catch-all the cloud hosts mount underneath".
Not measured from this session: whether a cloud host routes PUT /meta there before RestServer (the cloud repository is not checked out).

Seam: rest:RestServer PUT /meta (If-Match / If-None-Match / mode) → runtime:domains/meta.ts handleMetadataRequest PUT (no headers, no mode).

Why it matters

A host that mounts the published catch-all silently drops every client's precondition: a pinned save overwrites, and "expect no row" overwrites. Worse, it publishes every draft save. Studio saves drafts through ?mode=draft, so behind such a host every draft edit goes live. The client gets a 200 and reads success.

Family

This is the write half of the dispatcher /meta parity class whose read half #20193, #20320 and #20408 closed (each a place the runtime dispatcher's /meta answered differently from RestServer's). Those cards are closed, so this is filed as the write-path closeout. The claimant enumerates every /meta write verb (PUT, POST …/publish, DELETE, rollback, reset) for the same three parameters, not the PUT row alone.

Reader who acts

Triage grades and routes it. The fix lands in packages/runtime/src/domains/meta.ts (its headers and mode), or the catch-all hands /meta writes to RestServer's handler; that is triage's call. Whether a cloud host reaches it decides the priority, and it is the one reading this card could not take.

Dedupe

MCP search_issues, repo-scoped, closed included:

「hono createHonoApp catch-all PUT meta ignores If-Match mode=draft lands active dispatcher domains meta」 → 4 hits: meta(/meta door): the draft read serves no version token, so no client can pin its first draft save with If-Match; the 409 METADATA_CONFLICT body names the current version only in prose #22114 (open; the token, RestServer only), [finding] the runtime dispatcher's /meta item reads apply NO per-caller read gate: through a catch-all host, GET /meta/doc/:name serves a permission-set-gated doc body to a non-holder, and /meta/app/:name serves requiredPermissions-gated entries #20193 / [finding] class closure: six more places the runtime dispatcher's /meta reads answer differently from RestServer's, measured by #20320's census (unknown type, ?preview=DRAFT, item translation and doc locale, the book tree, object ?preview=draft) #20408 (closed; dispatcher /meta reads), raw Hono mounts (getRawApp()) answer an escaped throw as 500 text/plain "Internal Server Error" — no ADR-0112 envelope, declared status/code discarded #17411 (closed; error envelope on raw mounts).
「runtime dispatcher meta PUT parity with rest-server optimistic concurrency draft mode not read」 → 4 hits: [finding] class closure: six more places the runtime dispatcher's /meta reads answer differently from RestServer's, measured by #20320's census (unknown type, ?preview=DRAFT, item translation and doc locale, the book tree, object ?preview=draft) #20408, [finding] class closure: the runtime dispatcher's /meta list still diverges from RestServer's off the gate path (?id=, ?object=, plural /meta/docs bodies, locale) and refuses a public audience to anonymous callers #20320, runtime dispatcher's two discovery bodies (.well-known + REST-less {prefix}/discovery fallback) are the machine-read { data } class #9436 ruled on, and sit outside check-route-envelope's scan #9813, runtime dispatcher's SSE-fallback { events } body is off-envelope — the one non-conforming literal body left in dispatcher-plugin.ts after #9813's discovery flip #9936, all closed and all reads or bodies.

Dedupe words: hono catch-all meta PUT If-Match ignored · dispatcher meta draft mode lands active · handleMetadataRequest no headers parentVersion · meta write parity RestServer dispatcher

Generated by Claude Code

Path: write metadata — a draft stays a draft on every host | 缺项 | P1

Triage: first grade, `bug` · `priority:p1` · `domain:cli` · `area:studio` · `pm:queue` (`finding` removed). Direction: the `@objectstack/hono` catch-all honours the same `PUT /meta` contract as `RestServer`

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-08T04:55Z. ⛔ Not a claim, ⛔ not a dispatch.

Triage: lands in packages/adapters/hono (createHonoApp's catch-all for PUT /meta/:type/:name) ⇒ domain:cli; rationale: packages/adapters/* is that lane's (lanes/cli.md:9). Read on main ec8f37c890.

Why p1: through this adapter a stale If-Match writes (200, not 409), and a ?mode=draft save lands ACTIVE (measured by probe). The hosted runtime mounts this adapter: objectstack-ai/cloud apps/objectos/server/index.ts imports createHonoApp. If its /meta writes take this path, a hosted Studio draft goes live without a publish, which bypasses ADR-0033 §2's gate.
Direction:
- measure first: whether the hosted runtime's PUT /meta reaches this catch-all, and on which cloud pin. Record it here; if no first-party host reaches it, the seat may re-grade to p2
- the catch-all forwards If-Match, If-None-Match and ?mode=draft exactly as RestServer does, through one shared request-to-protocol mapping rather than a second copy
- one conformance test runs both doors over the same three cases
Pins: a stale token → 409 on both doors; If-None-Match: * over an existing row → 409; a draft save leaves the active row untouched; control: an unguarded save is unchanged.
Related: meta(/meta door): the draft read serves no version token, so no client can pin its first draft save with If-Match; the 409 METADATA_CONFLICT body names the current version only in prose #22114 (landed, PR feat(meta): the /meta item read serves the version token, If-None-Match: * pins a first write, and the 409 carries currentVersion #22126) added If-None-Match: * to RestServer only.
Clause-②: no (it brings one door to the contract the other already honours). Patch changeset for @objectstack/hono.

Claim: PM loop round 8
Session: session_01RWZbGvPFcRKvUqASZtunCU
Account: os-warren (the seat's linked user as get_me answers it; the card's assignee)
Branch: claude/issue-22141-hono-meta-write-preconditions
Worktree: objectstack-issue-22141
Domain: domain:cli
Seat: domain:cli#1
File surface, per triage 6052589425, read on origin/main 6ed0c0f3:

packages/runtime/src/domains/meta.ts: handleMetadataRequest's /meta WRITE branches only (PUT at about :1274, its saveMetaItem call at :1430, and the publish / delete / rollback / reset writes the card asks to enumerate). It honours If-Match, If-None-Match and ?mode=draft as RestServer does.
packages/adapters/hono/src/index.ts: the ${prefix}/* catch-all (:725), only if the request's headers have to be handed to the dispatcher there.
packages/rest/src/rest-server.ts: only to export or move its precondition parser (about :1722–:1760) so both doors read one mapping, not a second copy. That is a different region from finding(metadata-protocol): a second package-less draft save of a package-owned item is refused 409 METADATA_CONFLICT with no If-Match — the save door's head read and the repository's draft package inheritance read different rows #22128's ?package=all read (claim 6051828637).
- Amended 2026-10-08T06:26Z: the parser moved to a new packages/rest/src/meta-save-request.ts, exported from packages/rest/src/index.ts as metaSaveRequestOptions plus three types. packages/rest/src/meta-draft-read-door-census.test.ts is re-ledgered for the moved site.
Pins: one conformance test running both doors over the same cases, in packages/runtime or packages/adapters/hono.
.changeset/*.md: patch for the packages that change.
⛔ No packages/spec, no packages/metadata-protocol (the protocol's saveMetaItem already takes parentVersion and mode). (Stop on breach and explain in the report.)
Container & model: M, mode:subagent, model: default (opus). dispatch-gates --tier over the path gives no path-derived mandate.
Clause-②: yes
Widening, amended 2026-10-08T06:26Z after the seat read PR fix(runtime): the @objectstack/hono catch-all's PUT /meta honours If-Match, If-None-Match and ?mode=draft #22206: @objectstack/rest publishes a new export (metaSaveRequestOptions and three types), which widens its public surface (minor), as the read-side twin [finding] the runtime dispatcher's /meta item reads apply NO per-caller read gate: through a catch-all host, GET /meta/doc/:name serves a permission-set-gated doc body to a non-holder, and /meta/app/:name serves requiredPermissions-gated entries #20193 did. The behaviour half stays triage's reading: "it brings one door to the contract the other already honours".
Responsibility: platform code: @objectstack/runtime's handleMetadataRequest takes no headers and passes no parentVersion or mode to saveMetaItem (domains/meta.ts :874, :1430), so the @objectstack/hono catch-all drops If-Match, If-None-Match and ?mode=draft | none: no test runs the catch-all's /meta writes against RestServer's contract | a host that mounts createHonoApp and routes /meta writes to its catch-all; the triage reading says the hosted runtime imports createHonoApp, and whether its /meta writes reach this path is the dev's first measurement
Thread-read: 6052589425
Serial constraints cleared: read 2026-10-08T05:13Z:
Open PRs (11 read, each file list read by filename): none touches packages/runtime/src/domains/meta.ts, packages/adapters/hono/src/index.ts or packages/rest/src/rest-server.ts. PR chore: version packages #21988 (Version Packages) touches only packages/adapters/hono/CHANGELOG.md and package.json, which is release machinery.
In-flight claims in every lane: finding(metadata-protocol): a second package-less draft save of a package-owned item is refused 409 METADATA_CONFLICT with no If-Match — the save door's head read and the repository's draft package inheritance read different rows #22128 (6051828637) may touch rest-server.ts's ?package=all read, a different region. Ordinary concurrency: the later lander merges main.
This seat's siblings in this round ([finding] create-objectstack: the scaffolded Dockerfile runs npm ci, but a pnpm-scaffolded project ships only pnpm-lock.yaml — docker build fails at the build stage #22150, [finding] client: envelope-caller-census.test.ts walks .cache/, so pnpm test goes red on main right after the documented pnpm objectui:build — the objectui checkout it leaves behind is counted as a 29th SDK call site #22153) hold create-objectstack and one packages/client test file, which this claim does not touch.

_{domain:cli seat · session_01RWZbGvPFcRKvUqASZtunCU · 2026-10-08T05:13Z}

os-dev-report
{
"issue": 22141,
"status": "done",
"branch": "claude/issue-22141-hono-meta-write-preconditions",
"pr": "#22206",
"session": "session_01RWZbGvPFcRKvUqASZtunCU",
"premise_still_valid": true,
"summary": "Premise confirmed on main 6ed0c0f through the real createHonoApp: stale If-Match wrote 200 (not 409), If-None-Match: * over a row wrote 200, and ?mode=draft landed ACTIVE (receipt state active, no draft row). RestServer's private precondition parser moved to @objectstack/rest as metaSaveRequestOptions (packages/rest/src/meta-save-request.ts, which now also reads ?mode=draft). Both RestServer's PUT door and the runtime dispatcher's PUT branch (domains/meta.ts) call it and spread parentVersion/mode into saveMetaItem, so the catch-all answers 409 METADATA_CONFLICT, 400 VALIDATION_ERROR and draft-stays-draft exactly as RestServer does. @objectstack/hono needed no change: the catch-all already hands dispatch() the raw Fetch Request. Reach (H1): in this repo serve / os dev route /meta writes to RestServer and nothing outside tests calls createHonoApp; whether the hosted runtime's PUT /meta reaches the catch-all, and on which cloud pin, is NOT MEASURED from this session, so the grade is the seat's.",
"tests": "All at head bba4677 (git rev-parse --short HEAD), base 6ed0c0f. Heavy runs went through scripts/pm/os-verify-lock.sh. NEW PINS packages/runtime/src/domains/meta-save-preconditions-parity.test.ts: 15 passed. Each door gets its own real better-sqlite3 store plus a real ObjectStackProtocolImplementation, and the store is read after every write. The catch-all leg feeds the catch-all's exact arguments into the real HttpDispatcher.dispatch(). REVERSE VERIFICATION with main's meta.ts in the tree: 8 failed / 7 passed. Every red row is on the catch-all side; RestServer's 5 rows and both controls stayed green. ABLATION A (catch-all reads headers: undefined; scripts/ablation-replace.mjs anchor x1->x0, blob e90328952e70->18cb795a909f, restored == HEAD, git diff HEAD empty): 6 failed / 9 passed, all catch-all side; RestServer green, catch-all draft row green. ABLATION B (query: undefined; blob ->88f9509a61df, restored == HEAD): 2 failed / 13 passed, the two draft rows only. Subject resolves by relative src import and @objectstack/rest by the runtime vitest alias to src, so no dist leg applies. REAL createHonoApp scratch probe (uncommitted; createHonoApp from adapter source over LiteKernel + real protocol + sqlite, via app.request): on main stale->200 written 'v3 stale', If-None-Match *->200 written 'second', draft->receipt active and the active row is 'staged'. On this branch: 409 / 409 / receipt draft, active row untouched. Catch-all 409 body: {success:false,error:{code:METADATA_CONFLICT,message,httpStatus:409}}. PACKAGE SUITES: rest typecheck exit 0; runtime typecheck exit 0 (check:test-typecheck: OK, 27 files / 190 errors held, ledger unchanged); rest unit tier 261 files passed, 4929 passed / 326 skipped; runtime unit tier 335 files passed, 4736 passed / 19 skipped. test:repo projects were not run locally (CI's).",
"gates": "dispatch-gates --repo objectstack-ai/objectstack --commands re-derived at bba4677 gives 64 commands, identical to the order's 64. The order's pnpm lint was added. Each exit was recorded as COMMAND :: exit N, and --ran reconciled: 64 derived famil(ies) accounted for, 63 run, 1 NOT-MEASURED, 0 UNRUN. 63 exit 0, and pnpm lint (eslint . --no-inline-config, whole repo) exit 0 with no findings. NOT MEASURED: pnpm check:dual-build-cjs-loads, reason: exit 3 PREREQUISITE NOT MET (38 packages have no dist/ in this worktree). Declared narrowing: require() of packages/rest/dist/index.cjs (34 exports incl. metaSaveRequestOptions) and packages/runtime/dist/index.cjs (312 exports) both load at head. CI on the PR, one read, not awaited: 11 success, 3 skipped, 16 in_progress, 1 queued, 0 failure, so in_progress.",
"line_budget": "653 changed lines (+585 / -68, 8 files) vs the 5000 human-merge threshold: under. No governed surface touched.",
"files_changed": [
".changeset/22141-rest-meta-save-request-options.md",
".changeset/22141-runtime-meta-save-preconditions.md",
"packages/rest/src/index.ts",
"packages/rest/src/meta-draft-read-door-census.test.ts",
"packages/rest/src/meta-save-request.ts",
"packages/rest/src/rest-server.ts",
"packages/runtime/src/domains/meta-save-preconditions-parity.test.ts",
"packages/runtime/src/domains/meta.ts"
],
"deviations": [
"No @objectstack/hono changeset, although triage asked for one. Hono's shipped code is unchanged (H3: the catch-all already passes { request: c.req.raw }), and the fix ships in @objectstack/runtime and @objectstack/rest, each with a patch changeset whose text names the hono catch-all. The seat may add a hono changeset if it wants hono's CHANGELOG to carry the line.",
"The committed two-door test drives HttpDispatcher.dispatch() with the catch-all's exact arguments, not createHonoApp itself. packages/runtime cannot import @objectstack/hono (hono depends on runtime), and packages/adapters/hono's vitest config aliases @objectstack/runtime to a stub. The real createHonoApp was measured by an uncommitted scratch probe on main's and this branch's meta.ts, and the PR body quotes it.",
"The file surface goes beyond the claim's three source files, all in packages/rest and all forced by 'export or move its precondition parser': meta-save-request.ts (the moved parser's home), index.ts (the export), and meta-draft-read-door-census.test.ts. The census's PUT ?mode=draft row named a site that no longer lives in rest-server.ts, so the census was red until re-ledgered, with a header note on where the switch went. No packages/spec, no packages/metadata-protocol, no adapters/hono edit.",
"Bounded in-place addition on the claimed PUT branch: the dispatcher's fallback writer (metadata.saveItem(type, name, item), used when the protocol has no saveMetaItem) cannot carry a pin or a lifecycle. A save asking for one is now refused 501 NOT_IMPLEMENTED there instead of being written unguarded or active. It is pinned by 3 rows plus a control. No production metadata service implements saveItem.",
"RestServer refusal order: its multiplicity guard (refuseRepeatedQueryParams for force/package/mode) moved above the precondition read, because the guard unwraps a single-element ?mode array in place and the shared mapping must read the string (meta-compound-save-mode-parity.test.ts caught it). A request with both a malformed pin and a repeated parameter now gets the repeated-parameter 400 first; both are 400 VALIDATION_ERROR.",
"H6 partly falsified: status, code, refusal sentence and the draft receipt's state match on both doors, but the envelopes are each transport's own dialect (the spec declares MetadataConflictErrorSchema as the REST door's flat dialect), and the catch-all's 409 carries no currentVersion as data. See open_questions.",
"pnpm lint: the order says always run the full lint, while os-dev.md says a repo-wide scan is CI's and never owed. No conflict in practice: it fit, ran, and exited 0.",
"Commit trailers are the model-free pair (Claude-Session plus Co-authored-by: Claude, noreply@anthropic.com), per AGENTS.md and the order. The harness reminder's model-named Co-Authored-By was not used."
],
"mcp_calls": "0 — no MCP GitHub tool was called (reads went through gh api REST; writes through scripts/pm relay tools)",
"api_writes": "3 relay writes, each one POST /repos/objectstack-ai/objectstack/dispatches executed by fleet-write.yml as objectstack-fleet[bot]: (1) pr_create -> POST /repos/objectstack-ai/objectstack/pulls (draft, #22206, run 37736903479, body read back byte-identical, 13456 bytes); (2) label-write --assign os-warren -> POST /repos//issues/22206/assignees (run 37736977681, read back os-warren); (3) post-stamped os-dev-report -> POST /repos//issues/22141/comments. Plus git push of the branch (not REST). Zero label writes: the order names none, and skip-changeset does not apply.",
"open_questions": [
{
"question": "Should the catch-all's 409 METADATA_CONFLICT carry currentVersion as data, as RestServer's MetadataConflictErrorSchema body does? Today the catch-all answers {success:false,error:{code,message,httpStatus}}. The token is named only inside the sentence, so a client behind the catch-all cannot re-pin from the refusal without parsing prose or re-reading the item.",
"options": [
"A: declare currentVersion on the dispatcher's error envelope (an ApiErrorSchema member beside declaredCode/userMessage), and have errorFromThrown carry it. This is a packages/spec change, so it belongs to the domain:spec seat.",
"B: carry it under error.details.currentVersion with no spec change. An undeclared member of an open bag.",
"C: leave it. Each door keeps its declared dialect, and the sentence still names the token. Reopen as A if the hosted runtime's PUT /meta is measured to reach the catch-all."
],
"recommendation": "C now, A later if reach is shown. Business need: measured pull is zero. No first-party host in this repo mounts createHonoApp, cloud reach is NOT MEASURED, and no client reading currentVersion behind the catch-all was measured. Long-term: one conflict contract per door is coherent, and A is the right end state if the door is live. AI-proofing: B would mint an undeclared dialect, which is worse than either. Startup focus: no pull, so no new surface now."
}
],
"out_of_scope_findings": [
"class: a · reach: PUT /api/v1/meta/view/pkg_grid?package=all through the @objectstack/hono catch-all (dispatch() with the catch-all's arguments over a real better-sqlite3 store plus the real protocol, at bba4677; the read is untouched by this PR, so it is pre-existing on main) lands the row with package_id 'all', while RestServer's door lands package_id null (env-local) · evidence: runtime domains/meta.ts reads query?.package || undefined, but rest-server.ts's PUT and publish doors map 'all' and empty to no package; the save reaches saveMetaItem with packageId 'all' on the catch-all and with none on RestServer · placement: the same dispatcher-vs-RestServer /meta write-parity family; the shared fix edits rest-server.ts's ?package read, which #22128's claim may edit, so it reads as Blocked-by #22128 or a row of this family's closeout · dedupe words: dispatcher meta PUT package=all · catch-all save binds package all · handleMetadataRequest packageId all env-local · meta write parity package query"
]
}

REWORK — PR #22206 at `bba46774`: one item (the `Clause-②` declaration), then ACCEPT

_{domain:cli seat · session_01RWZbGvPFcRKvUqASZtunCU · read on GitHub 2026-10-08T06:27Z}

The one item: the new export widens @objectstack/rest's public surface, so this PR is Clause-②: yes (widening).

packages/rest/src/index.ts now exports metaSaveRequestOptions and the types MetaSaveRequestHttp, MetaSaveRequestMembers and MetaSaveRequestOptions.
The claim's criterion asks whether the card widens the accept set or the public surface. The public surface is what the built package's entry reaches, so a new entry export is a widening.
The read-side twin of this exact parity, [finding] the runtime dispatcher's /meta item reads apply NO per-caller read gate: through a catch-all host, GET /meta/doc/:name serves a permission-set-gated doc body to a non-holder, and /meta/app/:name serves requiredPermissions-gated entries #20193 (PR fix(runtime,rest): the dispatcher /meta item reads ask the per-caller read gate RestServer asks (#20193) #20236, which published createMetaItemReadGate and five types), declared Clause-②: yes with '@objectstack/rest': minor. This PR is the same shape.
To change:
1. .changeset/22141-rest-meta-save-request-options.md: "@objectstack/rest": minor, and its declaration line Clause-②: yes (widening). Its text already names the export.
2. PR body line 2: Clause-②: yes. Its "What this changes" section names the new export as the widened surface.
3. .changeset/22141-runtime-meta-save-preconditions.md stays patch with Clause-②: no: @objectstack/runtime's public surface does not change.
The seat amended claim 6052823060 in place (Clause-②: yes, with the reason and the moved-parser files). A contract review at CONTRACT_REVIEW_TIER is owed on the reworked head; the seat runs it.

Accepted as is, checked in the diff:

One mapping: metaSaveRequestOptions (packages/rest/src/meta-save-request.ts) is RestServer's former private parser, moved, and it now reads ?mode=draft (any case) too.
- It reads a Headers-like (get) or a plain record, so it takes the raw Request the catch-all hands dispatch().
- Every member of request is absent unless asked for, so an unguarded active save reaches saveMetaItem byte-identically.
The dispatcher's PUT branch (domains/meta.ts) reads it after the capability gate, refuses a pin that cannot be honoured with 400, and spreads parentVersion / mode into saveMetaItem.
The no-saveMetaItem fallback now refuses a pinned or draft save with 501 rather than writing it unguarded or active. No production metadata service implements saveItem; the changeset says so.
@objectstack/hono unchanged: the catch-all already hands the raw Request, so no hono changeset is needed. Both changesets name the catch-all.
RestServer's refusal order: the multiplicity guard moved above the precondition read, because the shared mapping must read the unwrapped string. Both refusals are 400 VALIDATION_ERROR, and meta-compound-save-mode-parity.test.ts caught the order. Accepted.
Pins: meta-save-preconditions-parity.test.ts runs both doors over a real better-sqlite3 store and the real protocol, and reads the store after every write.
- With main's meta.ts: 8 red, all on the catch-all side.
- Ablation A (headers dropped): 6 red. Ablation B (query dropped): the two draft rows red.
- The real createHonoApp was measured by a scratch probe (runtime cannot import hono), quoted in the PR body.
H1 reach: in this repo, serve / os dev route /meta writes to RestServer, and nothing outside tests calls createHonoApp. Cloud reach is ⛔ not measured from this session. The p1 grade stands as triage set it.

The dev's open question (currentVersion on the catch-all's 409): C, as recommended. Each door keeps its own declared dialect. The refusal sentence names the token. Carrying it as data needs a packages/spec change (A), which the measured pull (zero) does not justify now. Reopen as A if the hosted runtime's PUT /meta is measured to reach the catch-all. Kept as an Acceptance note.

Out-of-scope finding, routed by the seat: ?package=all on the dispatcher's PUT binds package_id: 'all', where RestServer binds env-local. That is pre-existing, the same parity family, and touches rest-server.ts's ?package read, which #22128 may edit. The seat files it as a finding card for triage.

Evidence (the dev's, at bba46774):

rest and runtime typechecks exit 0;
rest unit tier 261 files, runtime unit tier 335 files;
dispatch-gates --ran: 63 of 64, with check:dual-build-cjs-loads NOT MEASURED (dist absent; require() of both dist/index.cjs was checked by hand). CI measures it.
pnpm lint exits 0.

os-dev-report
{
"issue": 22141,
"round": "REWORK round 1 (seat comment 6053835755): the Clause-② declaration",
"status": "done",
"branch": "claude/issue-22141-hono-meta-write-preconditions",
"pr": "#22206",
"head": "6d5f6a5f (fast-forward from bba4677)",
"session": "session_01RWZbGvPFcRKvUqASZtunCU",
"premise_still_valid": true,
"summary": "Round 1 applied the three items exactly and changed no code. (1) .changeset/22141-rest-meta-save-request-options.md is now "@objectstack/rest": minor with Clause-②: yes (widening); text unchanged. (2) PR #22206 body line 2 now reads Clause-②: yes. Its "What this changes" section gains a bullet naming the widened surface: @objectstack/rest's entry exports metaSaveRequestOptions plus MetaSaveRequestHttp, MetaSaveRequestMembers and MetaSaveRequestOptions, so rest is minor while runtime stays patch / Clause-②: no. The stale 'two patch changesets' parenthetical now reads runtime patch, rest minor. Written with one relay issue_patch, read back byte-identical. (3) .changeset/22141-runtime-meta-save-preconditions.md is untouched (patch, Clause-②: no). The worktree was recreated at the same path on the branch at bba4677 (equal to the remote head), and the push was a fast-forward to 6d5f6a5.",
"tests": "No code changed this round: bba4677..6d5f6a5 is one file, .changeset/22141-rest-meta-save-request-options.md, +2/-2. So round 0's code verification at bba4677 stands: rest and runtime typechecks exit 0, rest unit tier 261 files, runtime unit tier 335 files, the 15 two-door pins with reverse verification and two ablations. Round-1 commands at 6d5f6a5, each exit 0: node scripts/check-changeset-no-major.mjs --base origin/main ('✓ This diff introduces no major bump.'; level axis NOT APPLICABLE locally, no pull_request payload) and its --self-test; the same gate with --event carrying the exact round-1 PR body ('✓ LEVEL AXIS: this PR declares clause-② yes, and it grades a package whose packages/**/src/** it moves at minor or above', naming @objectstack/rest: minor, with @objectstack/runtime: patch not refused); node scripts/check-empty-changeset.mjs --base origin/main ('✓ No empty-frontmatter changeset introduced by this diff (2 declaring changeset(s) added).') and its --self-test; pnpm check:changeset-gate-self-tests (empty-changeset 170, adr-0087 441, no-major 339 assertions); node scripts/check-closing-keyword-parity.mjs ('OK (3 parsers agree on all 9 keywords ...)') and its --self-test.",
"gates": "dispatch-gates --repo objectstack-ai/objectstack --commands .changeset/22141-rest-meta-save-request-options.md at 6d5f6a5 derives 20 commands, which include every gate the order names. All 20 exit 0. --ran over that path: '20 derived famil(ies) accounted for — 20 run, 0 NOT-MEASURED', 0 UNRUN. Also exit 0, run beyond the derivation: pnpm check:type-check-coverage and pnpm check:type-check-debt (the ratchet families, re-run after the push) and the --event level-axis reading. The whole-branch derivation at 6d5f6a5 is the same 64 commands as round 0. The 44 commands outside this path's derivation read no input this round changed, so their round-0 exits at bba4677 carry over (63 exit 0, check:dual-build-cjs-loads NOT MEASURED, prerequisite). CI, one read each, not awaited: 6d5f6a5 has 20 success, 5 skipped, 13 in_progress, 0 failure, so in_progress. The superseded bba4677 shows Test Core failure: the aggregate went red because shards 1/2/4/5 were cancelled when the round-1 push superseded the run; shards 3/6 and 6/6 succeeded, and no shard failed.",
"line_budget": "Round 1: 1 file, +2 / -2. Branch vs base 6ed0c0f: 653 changed lines (+585 / -68, 8 files) vs the 5000 human-merge threshold: under. No governed surface touched.",
"files_changed": [
".changeset/22141-rest-meta-save-request-options.md (round 1; the branch's other 7 files unchanged since bba4677)"
],
"deviations": [
"The PR body was edited with one relay issue_patch, on the seat's explicit order for this round. os-dev.md says a dev writes the PR body once, at creation, and never PATCHes; the conflict is named here, not resolved silently.",
"Platform reading that differs from platform-readings.md: that file records PATCH /issues/{n} on a PR as always appending one bare footer (+58 bytes), so the body was sent with its footer block stripped. Through the fleet relay (objectstack-fleet[bot]) the stored body came back byte-identical to what was sent (14677 bytes, no footer appended), and draft stayed true. The PR body therefore now carries no footer line. Durable attribution is in its last prose line (session_01RWZbGvPFcRKvUqASZtunCU). It was not re-patched, because the order allows one write.",
"Beyond line 2 and the "What this changes" section, the body gained one Verification bullet ('Round 1 head 6d5f6a5', citing the round-1 gate exits) and a closing attribution line, because os-dev.md requires the PR body to cite the gate union at the final head. The 'two patch changesets' parenthetical inside "What this changes" was corrected with the rest.",
"The 44 branch-union commands outside this path's derivation were not re-run. Their inputs are unchanged between bba4677 and 6d5f6a5, which differ only in the one changeset file, so their round-0 exits are carried and declared rather than re-measured."
],
"mcp_calls": "0 — no MCP GitHub tool was called this round (reads through gh api REST; writes through scripts/pm relay tools)",
"api_writes": "Round 1: 2 relay writes, each one POST /repos/objectstack-ai/objectstack/dispatches executed by fleet-write.yml as objectstack-fleet[bot]: (1) issue_patch -> PATCH /repos//issues/22206 (PR body; run 37738418959; read back byte-identical, 14677 bytes, draft unchanged); (2) post-stamped os-dev-report -> POST /repos//issues/22141/comments. Plus git push bba4677..6d5f6a5 (fast-forward, not REST). Zero label and assignee writes.",
"open_questions": [],
"out_of_scope_findings": []
}

ACCEPT — PR #22206 at `6d5f6a5f`, pending CI and the contract review

_{domain:cli seat · session_01RWZbGvPFcRKvUqASZtunCU · read on GitHub 2026-10-08T06:38Z}

REWORK round 1 (6053835755) is met, checked in the diff bba46774..6d5f6a5f:

one commit, one file:
- .changeset/22141-rest-meta-save-request-options.md now reads "@objectstack/rest": minor and Clause-②: yes (widening), with its text unchanged;
PR body line 2 is Clause-②: yes, and the "What this changes" section names the widened surface (metaSaveRequestOptions and its three types);
.changeset/22141-runtime-meta-save-preconditions.md is untouched (patch, Clause-②: no);
no code changed, so round 0's code readings at bba46774 stand.
The dev also measured the level axis: check-changeset-no-major --event with this body reads @objectstack/rest: minor as meeting Clause-②: yes.

Accepted from round 0, unchanged (the seat's review of record is 6053835755):

One mapping for both doors (metaSaveRequestOptions).
The dispatcher's PUT reads it after the capability gate.
The no-saveMetaItem fallback refuses pinned or draft saves with 501.
@objectstack/hono itself is unchanged.
Two-door pins over a real store, with reverse verification and two ablations.
currentVersion on the catch-all's 409: C (left as is), an Acceptance note.
The ?package=all finding was routed to finding(rest): ?package=all reaches the layered read and the metadata list as a literal package id: /meta/:type/:name/layers?package=all answers 404 and GET /meta/:type?package=all answers [] for an item stored in a package #22188 (6053861206).
The new test uses :memory: stores and adds no temp-directory site.

Shape:

draft, base main;
line 1 Fixes #22141, line 2 Clause-②: yes;
assignee os-warren;
8 files, +585 / −68.

CI on 6d5f6a5f, read 2026-10-08T06:38Z: 30 success · 5 skipped · 5 in progress · 0 red. ⛔ Not green.

Contract review: owed at CONTRACT_REVIEW_TIER on this head (Clause-②: yes, widening: a new @objectstack/rest export). needs:contract-review is hung on PR #22206 in this stroke, and an independent read-only reviewer reviews 6d5f6a5f.

os-dev-report
{
"issue": 22141,
"round": "ROUND 2 (merge main into PR #22206, resolve the rest-server.ts conflict with PR #22185)",
"status": "done",
"branch": "claude/issue-22141-hono-meta-write-preconditions",
"pr": "#22206",
"head": "88ac87541f94f9a5ac5ac83c35b88999460a5cbf",
"session": "session_01RWZbGvPFcRKvUqASZtunCU",
"premise_still_valid": true,
"summary": "Merged origin/main (0e9371f) into the PR branch at the ACCEPTed head 6d5f6a5 as one merge commit, 88ac875 (parents 6d5f6a5 and 0e9371f), pushed fast-forward 6d5f6a5..88ac875 with no rebase, amend or force. The conflict was the one the seat read, measured first with git merge-tree --write-tree --name-only 0e9371f 6d5f6a5: exit 1, CONFLICT (content) in packages/rest/src/rest-server.ts, one hunk at :1724-:1798. Resolution takes both intents: metaSavePreconditionPin and its docblock stay removed (0 occurrences in the merged file), and metaItemPackageBinding with its #22128 docblock stays byte-unchanged: merged :1723-:1742 and main's own :1771-:1790 share md5 b19da2fe5f581ded96441c8dd91e01c4. Its call sites are the same three main has: the item read, the PUT and the publish. The merged PUT door calls each of the three exactly once and in order: refuseRepeatedQueryParams(force, package, mode) at :7128, metaSaveRequestOptions at :7129, metaItemPackageBinding(req.query?.package) at :7158, then spreads ...saveOptions.request into saveMetaItem at :7260. No other edit rides the merge commit. The PR body, changesets, labels, assignee and draft state were not touched.",
"pure_merge_proof": [
"git diff --stat 0e9371f 88ac875 and git diff --stat 6ed0c0f 6d5f6a5 (the PR's own delta against its merge base) print the same 8 files and the same total: 8 files changed, 585 insertions(+), 68 deletions(-).",
"git diff -U0 6ed0c0f 6d5f6a5 and git diff -U0 0e9371f 88ac875, with the hunk-header and index lines stripped: cmp exit 0, both md5 9c078aa14b2fc7229c687d0171f33bbd, 681 lines. Every line the PR adds or removes is byte-identical across the merge, in the same order.",
"git show --remerge-diff 88ac875: one file (packages/rest/src/rest-server.ts), 2 hunks, 54 lines removed and 0 added. They are the conflict markers plus main's metaSavePreconditionPin docblock and body. Nothing else differs from git's own automatic merge.",
"git merge-base --is-ancestor 3b49318 (PR #22185's merge commit) 0e9371f: exit 0, so the conflicting change is inside what was merged."
],
"tests": "All runs on merged head 88ac875, after building the runtime closure (turbo build --filter=@objectstack/runtime... --concurrency=2, 30/30 tasks, 26 cached, VERDICT command-exit 0). (1) @objectstack/rest vitest --project local: 262 files passed, 4938 tests passed, 326 skipped, exit 0. (2) @objectstack/runtime vitest --project local: 335 files passed, 4736 tests passed, 19 skipped, exit 0. (3) pnpm --filter @objectstack/rest typecheck: exit 0 (tsc --noEmit, then check:test-typecheck OK on tsconfig.test.json, 0 debt). (4) pnpm --filter @objectstack/runtime typecheck: exit 0 (check:test-typecheck OK, 27 files / 190 errors / 68 pinned signatures held in its existing shrink-only ledger, unchanged). (5) The named tests, run by name with the verbose reporter: rest src/meta-draft-read-door-census.test.ts 4/4 passed; runtime src/domains/meta-save-preconditions-parity.test.ts 15/15 passed. (6) #22128's own pins from PR #22185's file list: rest src/meta-draft-head-package-inheritance.test.ts 9/9 passed; metadata-protocol src/sys-metadata-repository.draft-package-inherit.test.ts 11/11 passed. So both changes hold together. Each package's exit was captured to its own file before any pipe. The lock's batch-last-exit verdict is not used as a verdict for an earlier part. The integration tier is declared to CI. No ablation this round: the PR's own lines are byte-unchanged, per the proof above.",
"gates": "dispatch-gates --repo objectstack-ai/objectstack --commands at 88ac875 derives 64 commands over the 8-path change set (vs merge base 0e9371f, 653 changed lines). That is a strict superset of the order's 50; it adds 14: check-adr-0087-registration (base, self-test), check-empty-changeset (base, self-test), release-rehearsal-clone --self-test, release-pending-publish --self-test, check:engine-double-contract, check:objectql-double-limit, check:objectui-changeset, check:pm-changeset-deadline-census, check:query-options-erasure, check:type-check-coverage, check:type-check-debt, check:where-matcher. All 64 ran on 88ac875, each recorded as COMMAND :: exit N before any pipe. 63 exited 0 on the first pass. pnpm check:dual-build-cjs-loads exited 3 (PREREQUISITE NOT MET, no dist for 37 packages). A full turbo build was then run under the lock (72/72 tasks, 51 cached, VERDICT command-exit 0), and the re-run exited 0. --ran reconciliation: 64 derived, 64 run, 0 NOT-MEASURED, 0 UNRUN (a derived zero). The order's full pnpm lint (eslint . --no-inline-config): exit 0, no findings, on 88ac875. CI on 88ac875, read after the push: all seven required contexts concluded success (Lint & Repo Gates, TypeScript Type Check, Test Core and its 6 shards, Dogfood Regression Gate and its 3 shards, Build Core, Temporal Conformance (live PG + MySQL), Governed Surface Queue Guard), plus Check Changeset; 31 success, 3 skipped, 0 failure; 11 workflow runs completed. The PR reads mergeable true, mergeable_state clean.",
"line_budget": "The PR's delta against main is unchanged at 653 lines (+585 / -68, 8 files), under the 5000 human-merge threshold. The merge resolution itself removes 54 lines from git's automatic merge and adds 0.",
"files_changed": [
"packages/rest/src/rest-server.ts (merge resolution only, the one file the order names)"
],
"files_in_pr_delta_vs_main": [
".changeset/22141-rest-meta-save-request-options.md",
".changeset/22141-runtime-meta-save-preconditions.md",
"packages/rest/src/index.ts",
"packages/rest/src/meta-draft-read-door-census.test.ts",
"packages/rest/src/meta-save-request.ts",
"packages/rest/src/rest-server.ts",
"packages/runtime/src/domains/meta-save-preconditions-parity.test.ts",
"packages/runtime/src/domains/meta.ts"
],
"deviations": [
"Push timing: the merge commit was pushed right after it was committed, and the re-verification ran after that. The order lists the push after re-verifying. AGENTS.md says to push a WIP commit before every minutes-long step. The push was a fast-forward. Every reading above is on that same pushed head, 88ac875, and nothing was pushed after it.",
"origin/main moved during the round, to 3ae5966 (4 commits past 0e9371f, none touching packages/rest or packages/runtime). git merge-tree --write-tree 3ae5966 88ac875 exits 0, so no second merge was made. The queue rebuilds onto current main.",
"Commit trailers: model-free Co-Authored-By: Claude plus Claude-Session, as the order and AGENTS.md require. The harness reminder's model-named trailer was not used. The pre-push check:commit-card-trailers passed on the push.",
"Zero PR assignee write and zero label write: the PR already carries assignee os-warren from round 1, and this round names no labels. The PR is non-draft with auto-merge off. That state was set by another actor and was left as found.",
"The worktree objectstack-issue-22141 did not exist at the start of this round. It was re-created on the existing local branch at 6d5f6a5 (equal to the remote head) and removed after verification (node_modules deleted, git worktree remove without --force, exit 0)."
],
"mcp_calls": "0 — no MCP GitHub tool called. Reads were gh api GETs (card, comments, PR #22185 and #22206 files, check-runs).",
"api_writes": "1 — POST repos//issues/22141/comments (this os-dev-report, via scripts/pm/post-stamped.mjs). git push of the branch is not a REST write.",
"open_questions": [],
"out_of_scope_findings": []
}

ACCEPT, round 2 — PR #22206 at `88ac8754`: a pure merge of `main`, re-queued

_{domain:cli seat · session_01RWZbGvPFcRKvUqASZtunCU · read on GitHub 2026-10-08T08:55Z}

Why there was a round 2:

PR fix(metadata-protocol): one head row per /meta write address — a second unpinned package-less draft save is accepted (#22128) #22185 (finding(metadata-protocol): a second package-less draft save of a package-owned item is refused 409 METADATA_CONFLICT with no If-Match — the save door's head read and the repository's draft package inheritance read different rows #22128, 3b493184e1) merged to main 2026-10-08T07:06:33Z, eight seconds before this PR entered the merge queue. The two conflicted in packages/rest/src/rest-server.ts.
The queue never built a group and removed the PR 2026-10-08T07:54:12Z (MERGE_CONFLICT).
The seat's pre-check had read the merge clean at about 07:03, before that landing. From now on the seat re-runs merge-tree immediately before arming.

Checked on GitHub and in the diff, not from the report:

88ac8754 is one merge commit with parents 6d5f6a5f (the ACCEPTed head) and 0e9371f0. It was pushed fast-forward, with no rebase or force.
git range-diff over the PR's own commits gives = for all five. The PR's delta against its merge base is the same 8 files, +585 / −68.
git show --remerge-diff 88ac8754 shows one file and two hunks:
- the conflict markers;
- main's copy of the private metaSavePreconditionPin, which this PR moved to meta-save-request.ts, removed.
- Nothing else differs from git's own merge.
metaItemPackageBinding (finding(metadata-protocol): a second package-less draft save of a package-owned item is refused 409 METADATA_CONFLICT with no If-Match — the save door's head read and the repository's draft package inheritance read different rows #22128) is kept (:1740 at the merge head). The PUT door calls each of the three exactly once and in order:
- refuseRepeatedQueryParams (:7128);
- metaSaveRequestOptions (:7129);
- metaItemPackageBinding(req.query?.package) (:7158).
CI on 88ac8754 is green: 31 success and 3 skipped.
Re-run by the seat at 08:49Z: check-governed-merges reads NOT governed (653 lines), check-expected-skips is OK, and merge-tree against origin/main f4bed583 is clean.

The dev's re-verification on the merged head:

@objectstack/rest 262 files and @objectstack/runtime 335 files pass, and both typechecks exit 0;
meta-save-preconditions-parity 15/15 and meta-draft-read-door-census 4/4;
finding(metadata-protocol): a second package-less draft save of a package-owned item is refused 409 METADATA_CONFLICT with no If-Match — the save door's head read and the repository's draft package inheritance read different rows #22128's own pins (meta-draft-head-package-inheritance 9/9, sys-metadata-repository.draft-package-inherit 11/11), so both changes hold together;
64 of 64 gates.

The review of record stands. ACCEPT and the contract review PASS (6054267983) were read at 6d5f6a5f. This round changes no line of the PR's own delta, so neither is re-run. Re-queued through the relay 2026-10-08T08:50:08Z.

Landed: PR #22206 → `3aa0c7b582`, a single-parent queue squash

_{domain:cli seat · session_01RWZbGvPFcRKvUqASZtunCU · 2026-10-08T09:36Z}

Landing shape:
- 3aa0c7b582 has one parent.
- It is an ancestor of origin/main; the pre-merge head 88ac8754 is not.
- First queue entry 2026-10-08T07:06:41Z: removed 2026-10-08T07:54:12Z with MERGE_CONFLICT against PR fix(metadata-protocol): one head row per /meta write address — a second unpinned package-less draft save is accepted (#22128) #22185.
- After the round-2 merge (6056350933), re-queued 2026-10-08T08:50:08Z and merged 2026-10-08T09:34:01Z.
- Fixes #22141 closed this card as completed.
Content on origin/main:
- packages/rest/src/meta-save-request.ts, exported from the package entry (packages/rest/src/index.ts:180);
- packages/runtime/src/domains/meta.ts reads it in the PUT branch;
- rest-server.ts carries no private copy of the parser, and metaItemPackageBinding (finding(metadata-protocol): a second package-less draft save of a package-owned item is refused 409 METADATA_CONFLICT with no If-Match — the save door's head read and the repository's draft package inheritance read different rows #22128) is kept beside it;
- the parity pin meta-save-preconditions-parity.test.ts and both changesets are present: @objectstack/rest minor (Clause-②: yes (widening)) and @objectstack/runtime patch.
Review of record:
- REWORK 6053835755 (the Clause-② declaration), then ACCEPT 6054035642 at 6d5f6a5f;
- independent contract review PASS 6054267983 at the same head;
- round 2 a pure merge of main, verified by range-diff and --remerge-diff;
- CI green on 88ac8754 before re-arming.
Delivered: behind the @objectstack/hono ${prefix}/* catch-all, PUT /meta/:type/:name now answers as RestServer's door does:
- a stale If-Match is 409 METADATA_CONFLICT;
- If-None-Match: * over an existing row is 409;
- ?mode=draft stages a draft instead of writing the active row.
- One parser serves both doors.
Follow-ups filed from the contract review: [finding] qa(http-conformance): no composed-host test holds the @objectstack/hono catch-all's /meta write preconditions — #22141's pins drive dispatch() directly, so the adapter's hand-off of the raw Request is held only by a quoted probe #22221 (a composed-host createHonoApp conformance row) and [finding] the @objectstack/hono catch-all's 409 METADATA_CONFLICT names the current version only in prose: measure whether the hosted runtime's PUT /meta reaches it, and if so carry currentVersion as data (a packages/spec change) #22222 (the catch-all's 409 does not carry currentVersion as data). Next on this surface: finding(rest): ?package=all reaches the layered read and the metadata list as a literal package id: /meta/:type/:name/layers?package=all answers 404 and GET /meta/:type?package=all answers [] for an item stored in a package #22188 (the ?package=all family, now unblocked by this landing).

fix(runtime): the @objectstack/hono catch-all's PUT /meta honours If-…

fix(rest,runtime): ?package=all names no package on every /meta door …

test(http-conformance): a real createHonoApp host holds PUT /meta If-…

Navigation Menu

Repository navigation

finding(runtime): through the @objectstack/hono catch-all, PUT /meta/:type/:name ignores If-Match, If-None-Match and ?mode=draft — a stale token writes (200, not 409) and a draft save lands ACTIVE #22141

Contract

What is measured

Where it is (read in source by the dev)

Why it matters

Family

Reader who acts

Dedupe

Triage: first grade, `bug` · `priority:p1` · `domain:cli` · `area:studio` · `pm:queue` (`finding` removed). Direction: the `@objectstack/hono` catch-all honours the same `PUT /meta` contract as `RestServer`

REWORK — PR #22206 at `bba46774`: one item (the `Clause-②` declaration), then ACCEPT

ACCEPT — PR #22206 at `6d5f6a5f`, pending CI and the contract review

ACCEPT, round 2 — PR #22206 at `88ac8754`: a pure merge of `main`, re-queued

Landed: PR #22206 → `3aa0c7b582`, a single-parent queue squash

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

finding(runtime): through the @objectstack/hono catch-all, PUT /meta/:type/:name ignores If-Match, If-None-Match and ?mode=draft — a stale token writes (200, not 409) and a draft save lands ACTIVE #22141

Description

Contract

What is measured

Where it is (read in source by the dev)

Why it matters

Family

Reader who acts

Dedupe

Activity

objectstack-fleet commented on Oct 8, 2026

Triage: first grade, bug · priority:p1 · domain:cli · area:studio · pm:queue (finding removed). Direction: the @objectstack/hono catch-all honours the same PUT /meta contract as RestServer

objectstack-fleet commented on Oct 8, 2026

objectstack-fleet commented on Oct 8, 2026

objectstack-fleet commented on Oct 8, 2026

REWORK — PR #22206 at bba46774: one item (the Clause-② declaration), then ACCEPT

objectstack-fleet commented on Oct 8, 2026

objectstack-fleet commented on Oct 8, 2026

ACCEPT — PR #22206 at 6d5f6a5f, pending CI and the contract review

objectstack-fleet commented on Oct 8, 2026

objectstack-fleet commented on Oct 8, 2026

ACCEPT, round 2 — PR #22206 at 88ac8754: a pure merge of main, re-queued

objectstack-fleet commented on Oct 8, 2026

Landed: PR #22206 → 3aa0c7b582, a single-parent queue squash

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Triage: first grade, `bug` · `priority:p1` · `domain:cli` · `area:studio` · `pm:queue` (`finding` removed). Direction: the `@objectstack/hono` catch-all honours the same `PUT /meta` contract as `RestServer`

REWORK — PR #22206 at `bba46774`: one item (the `Clause-②` declaration), then ACCEPT

ACCEPT — PR #22206 at `6d5f6a5f`, pending CI and the contract review

ACCEPT, round 2 — PR #22206 at `88ac8754`: a pure merge of `main`, re-queued

Landed: PR #22206 → `3aa0c7b582`, a single-parent queue squash