Repository navigation
Conversation
Keep existing lineage and every contributing producer root across response observation, detached delivery and shunt aggregation. Refuse unknown automatic context and retain unacknowledged reports. Native bootstrap and direct MCP publication remain unqualified. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Load the isolated home before response-test imports and apply the formatter pinned by CI. Preserve every test assertion and the existing native-client qualification requirements. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Recognize the existing Cline host marker and bind the two consumer fixtures before invoking real hooks. Check the current claim filename in the delivery cleanup assertion and state the raw session identity requirement. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Keep delivery classifications and reviewed source fingerprints aligned with the existing-family plugin wrappers. Preserve all sender admission assertions and unrelated inventory records. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Bind existing task families before parent capture and repository requests. Retain queued prompt roots and recheck them before context publication or acknowledgement. Preserve unknown and legacy evidence without assigning a clean family. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Observe every contributing root before returning a response, then stop automatic consumers and file lookup acknowledgements when protection changes during the request. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Keep both durable family marks while checking the response refusal instead of dereferencing the withheld body. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Recheck retained protection after awaited work and before primer cache writes. Keep ordinary primer output and cache refresh covered alongside marked-response and sibling-mark suppression. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Recheck retained authority before publishing the local decision. Preserve ordinary health primer controls and require malformed JSON health to protect the family and stay silent. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Resolve local records through the process token SID and protected owner ACLs. Bound native jobs contain compiler descendants across caller death, and strict JSON checks retain the existing record contract. Preserve native positive and refusal assertions within the existing time limits. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Native creation fails before its ownership assertions. Preserve fixed phase and numeric failure evidence through the existing generic refusal without exposing raw helper output or changing its deadlines. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
A startup phase alone cannot distinguish a captured marker from the parser default. Record fixed entry boundaries and bounded capture counts on the existing launches while preserving their deadlines and authority checks. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Hosted calls reach script entry but time out before the first encoding assignment completes. Keep the same construction and assignment while recording their separate fixed boundaries. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Use the same typed constructors and arguments at the measured first-construction boundary while retaining diagnostics, authority checks and deadlines. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Use an exclusive claim before publishing an immutable alias. Keep existing privacy state when startup hooks overlap or a producer exits. Account Windows timer setup against the original absolute deadline and distinguish native timer termination from other helper failures. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Select the JSON alias before corrupting it so the existing refusal assertions still exercise damaged resume metadata. Resolve the plugin version conflict with main while retaining the unused 1.2.40 behavior version in both manifests. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Allow an explicit initial SessionStart event to establish its host-scoped family while retaining refusal for inherited, damaged and protected sessions. Extend the real hook-entry controls to both native clients. Add fixed Windows setup phases to locate native deadline failures without changing operation budgets, authority checks, jobs or cleanup. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Avoid copying a security descriptor and attempting directory creation for each existing ancestor. Missing directories still receive the private descriptor and the same pinned-handle validation. Keep operation deadlines, authority checks, job containment and exact cleanup unchanged. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Drain fixed helper diagnostic frames in the existing real witnesses and include observer elapsed time when startup fails. Keep raw stderr out of the report and bound the retained frames and numeric fields. Preserve the native workload, deadlines, process identity checks, forced termination and cleanup assertions. No product operation or timing limit changes. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The second interpreter and duplicate native bootstrap consume the bounded setup window. A suspended compiler joins its private job before execution. The guardian stops compiler descendants and removes their owned files before record access, retaining the original absolute deadlines. The existing shunt regressions include bounded server and child observations in failure messages without changing their assertions. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Capture fixed numeric compiler diagnostics after owned descendants stop. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Preserve both hook regression groups and bind the local-query fixture to its existing family. Check ordinary and marked startup publication through the native session harness. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Establish the contract and recall fixture aliases before prompt delivery. Preserve all request and output assertions, and format the plugin manifest with the repository formatter. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Keep fixed parsing, construction and encoding markers inside the existing budget. Record request entry and failure-only queue metadata in the shunt fixture without changing its assertions or timing. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Keep the checked claim after publication so loss of an alias cannot create a clean replacement session. Cover both startup hosts and the retained claim ACL. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Use the existing strict reader and fixed primitive responses to remove general PowerShell JSON commands from the bounded helper path. Require exact string fields and reject duplicate request keys while preserving stored-record semantics and native authority checks. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The two integration cases share a path and namespace. A row written by one case can enter the other case's exact result assertion when test order changes. Keep every assertion and pass a separate registered org through each case. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
5 tasks done
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…in-existing-session-lineage Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Report only the bounded sample count and prefix category after the existing reader closes. Keep those observations outside phase and error selection, and restore the marked aggregate fixture's original call order. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Observe the existing root creation method and both checked record writes before readback. Diagnostic I/O stays private and cannot interrupt authority or cleanup; all native deadlines remain unchanged. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Flush both response streams after owned compilation cleanup before ending this process. Keep native watchdogs armed and preserve failure when a terminal call returns. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Keep fresh directory and file authority checks while removing redundant parent-creation attempts. The two private calls run while CreateRoot retains every parent; an unexpected missing parent refuses. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
A missing clean delivery leaves an owned claim without proving its producer. Record bounded control-validity and row counts after the original failure while preserving every assertion and successful path. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Recognize the fixed fatal-error prefix within the existing bounded numeric diagnostic scanner. Exercise the real PowerShell scanner for fixed frames, deduplication, cutoff and rejected text without exposing compiler output. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Retain the child-process assertion while reporting only an allowlisted error code. Both Windows runs fail before scanner observations, and raw child errors must stay private. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The scanner harness emits only allowlisted labels and checked integers. Build that fixed JSON directly so its native check does not need the general PowerShell serializer; keep the fixtures, assertions and child limits. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The lifetime witness fails before announcing its child. Record only whether the fixed expected pipe path and compiler code occur on one bounded output line; retain the refusal and cleanup. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The native protection call can stop after record dispatch without exposing whether it opened and flushed the state file. Emit two fixed progress markers while retaining the checks, durable write, refusal and cleanup. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Witness the assigned suspended compiler under the existing native job deadlines, then qualify real resumed compilation with a separate fixed-input control. Retain the original lifetime assertions and limits. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Record four fixed test-only phases around the assigned-process check and receipt construction. Retain the serializer, deadlines and termination assertions; the current failure stops before any receipt is announced. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The witness reaches receipt construction before exiting without an announcement. Keep its fields and lifetime assertions while removing the general JSON serializer from this fixed test receipt. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Record a bounded primary stage and error category before rethrowing. Keep cleanup assertions and native deadlines unchanged. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Cleanup timeouts can mask the last completed observation. Report only fixed boundary labels and distinguish directory equality from existence. Keep the existing assertions, cleanup commands and deadlines. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The directory assertion and cleanup observer mask different failures. Retain bounded comparison facts and distinguish completed input reads from JSON conversion without changing the assertions or deadlines. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Resolve the existing owned directory before deriving the compiler path used by the exact directory assertion. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Default resolution retains the short spelling in the expected path, while the compiler receipt uses the long spelling. Resolve the existing fixture directory through the native path before appending its child. The exact assertion and all lifetime budgets remain unchanged. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
An empty observation conflates missing or exited processes, changed identities and swallowed process-state errors. Retain bounded outcomes from the existing reads and call timing against the operation deadline. Assertions, observer codecs, process calls and budgets stay fixed. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Retain the cutoff already supplied to the witness and capped clock facts on either side of the existing lookup statements. Distinguish a thrown conversion from an unreturned interval. Assertions, process calls, conversion expressions and budgets stay fixed. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The pre-death check started a fresh interpreter after the native deadlines were armed and could miss the compiler's live window. Have the existing witness recheck its exact compiler handle after capturing both identities, then require observed parent exit before the same cutoff. Keep the post-death absence checks and all budgets. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The parent relays the guardian's stderr and loses later cleanup phases when the test kills it. Inherit that existing stderr handle and report the validated phase ring on post-death failure. Keep the original assertions, exceptions and deadlines. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The parent-death trace ends at the startup receipt. Emit one fixed phase after the existing exact-handle wait returns, and accept only its zero code in the bounded collector. Preserve assertions, waits, deadlines and cleanup. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Include the fixture clock correction while preserving the session privacy implementation and native assertions. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related: #920
Changelog category
Changelog entry
Automatic coding-agent hooks retain their session family's privacy state across responses and detached delivery. Explicit Claude Code and Codex startup establishes one durable family; unknown, damaged or protected families suppress capture, signup and the session primer.
Why
A response can make a session private after a hook starts or queues work. Automatic consumers must retain every original contributor and observe response privacy before sending or acknowledging content. Selecting a clean family later cannot release protected work.
Scope and risk
Hook entry binds the raw session identifier before normalization. Only an installed host's exact startup event establishes a family. Resume, fork, compact, subagent and other adapter events resolve existing state. Concurrent startup reuses an immutable alias; existing privacy marks never reset. Conflicting anchors cannot choose a replacement, and a failed privacy write does not leave another known contributor unmarked.
Response, callback, shunt and detached-job contexts carry all contributing roots. Cline retains producer roots through its queue and rechecks them before stdout publication and acknowledgement. Unknown or protected reports remain unsent and failed claims unacknowledged. Unattributed files are preserved, and queue names isolate older consumers.
Alias publication uses an exclusive private regular-file claim tied to its created object. Claims remain beside immutable aliases; cleanup closes descriptors without deleting the claimed pathname. A complete alias survives producer death, while an unpublished claim stays unavailable without takeover or expiry. This adds a permanent content-free marker per alias. Receipt checks detect observed replacements; they do not promise continuous pathname ownership against another process with the same user's directory access.
Windows records require the process token owner, protected owner-only DACLs, checked non-reparse handles, single-link files and pinned NTFS ancestors. Request parsing and fixed response encoding share the record-method assembly. Requests require exact lowercase keys and operations, string fields and no duplicate decoded keys. Privacy writes append and flush before success.
The guardian starts the fixed compiler suspended, assigns its native job and checks the absolute deadline before resume. Each operation retains its 1500 ms primary budget and 2000 ms total ceiling, including cleanup reserve. Compilation descendants stop before assembly loading and owned-file deletion. The record operation shares the earlier cutoff; fixed success is emitted only after the checked return path. A returned success-termination attempt becomes failure without retry.
Diagnostics retain bounded fixed phases, numeric codes, counts and format categories. They omit raw requests, output, identities, paths and stacks. The scanner reads at most 8192 bytes and retains four deduplicated compiler codes. A rolling diagnostic ring holds at most 24 validated frames. A retained wait-returned marker establishes only the checked wait and following report statement. Missing frames establish no inverse cause, and added diagnostic work can affect scheduling or broken pipes.
The lifetime fixture requires a trusted observation of the exact live suspended compiler before its cutoff, then actual Node-parent death before that cutoff. It preserves the original post-exit wait, exact PID/start-time absence, directory absence and final cleanup assertions. Separate controls cover real compilation, escaped/reordered requests, all operations and sixteen malformed inputs. These positive premises cannot be replaced by compiler failure or deadline termination.
Compatibility, rollout and rollback
1.2.47. Generated copies retain their canonical content; uniqueness must be rechecked before merge.Tests and remaining verification
The current-main composition preserves the original opaque hunks' added/deleted bytes. It incorporates the separately merged run-id and replicated-erasure fixture fixes. Manifest JSON, mirror blob equality and whitespace checks pass. These static checks do not qualify runtime behavior. Full hosted CI and a fresh independent review are required on the pushed head; restricted source and changed surrounding context remain unreviewed.
The earlier composed-head run passed all six unit shards but failed both Windows platform jobs and integration shard four. Both integration failures were the same missing lease-table fixture, addressed on main. The next composition fails three close-admission cases at their shared preparation-clock predicate; its unit shard five also fails one document-extraction linear-time check. Those causes remain unresolved. These observations do not qualify this new head.
The retained Windows results establish distinct failed premises. On x86, helper-death and parent-death cases stop before their receipt with a compiler-environment error followed by a cleanup marker. The codec control exits 1460 at its first status assertion. Malformed-request testing stops during fresh-root setup. On ARM, helper-death reaches primary completion before its final observer times out; parent-death has separate primary and final input-read observer timeouts. The codec control passes, but malformed-request testing stops during protection setup. Both scanner and fixed-input compiler controls pass on both architectures in that invocation. No exact source defect or safe repair follows from these observations. Other failure bodies remain unclassified.
No deadline, timeout, threshold or positive assertion is relaxed. No retry, warmup, authority bypass or new diagnostic marker is added by this composition. Windows timing, authority and cleanup, native privacy before first storage or rendering, direct MCP publication and private source creation remain unqualified. The native CLI harness checks model input, CLI streams and automatic HTTP bodies; it does not inspect native first storage or rendering. The PR remains a draft until the required behavior, review and full CI pass.
AI assistance in the code
AI-generated: An agent wrote the change.
I can explain every line of this diff and how it interacts with the rest of Loom.
Checklist