Repository navigation
Update kin source - #1868
Update kin source#1868kin-public-export[bot] wants to merge 8 commits into
Conversation
Signed-off-by: Troy Fortin <troy@firelock.ai> Signed-off-by: kin-public-export <export@firelock.ai>
…n-fixtures Bind Managed requests to repositories and harden Mac packaging Signed-off-by: kin-public-export <export@firelock.ai>
Hold managed builds to runtime admission in every daemon request Signed-off-by: kin-public-export <export@firelock.ai>
fix(kin): use Suite.kin_run in coverage_read_open diverged control Signed-off-by: kin-public-export <export@firelock.ai>
…iner-network fix(kin): share host networking for the capped memory-footprint container Signed-off-by: kin-public-export <export@firelock.ai>
feat(kin): complete the local workbench on persisted engine paths Signed-off-by: kin-public-export <export@firelock.ai>
fix(kin): replace superseded daemons and consolidate single-install markers Signed-off-by: kin-public-export <export@firelock.ai>
Bound cross-repo spine read wait and preserve uncommitted durability disclosure Signed-off-by: kin-public-export <export@firelock.ai>
| "One test run names at most {ENTITIES_PER_REQUEST} entities." | ||
| )); | ||
| } | ||
| let mut ids = Vec::with_capacity(entities.len()); |
|
Removed from the merge queue by a failing This PR was admitted to the queue, built as a speculative merge, and dropped. Its own PR-level checks and mergeable state are unaffected and still read clean, so nothing else on this page shows that it happened.
Fix the cause, then have the captain re-submit. If the failure is in the squash commit message rather than the code, remember the queue mints that message from this PR's title and body, so anything placed there is authored straight into public history after every local Git hook has already run. What the hygiene gate refuses there is an assistant-session trace: a |
|
Superseded by updated export candidate with cross-platform runtime admission and acceptance gate fixes. |
Update the public source from the maintained development tree.
Validation: public metadata and full-history secret scans passed, along with the component checks in an isolated public checkout. This PR requires the repository's normal review and checks before merging.