Repository navigation
plan: harden placement driver before SSH (agent-harness#1504) - #1556
Draft
ViperJuice wants to merge 6 commits into
Draft
ViperJuice wants to merge 6 commits into
ViperJuice wants to merge 6 commits into
Conversation
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.
The approved agent-harness#1504 plan hardens sealing, worker accumulation, result bounds and duration parsing before SSH builds on the driver. Seven plan reviews and a qualified Fable-only president approved immutable plan digest46b6c610 for serial implementation. The implementation remains local and unpublished at76da92f7, with nine owned changed paths and the nonlocal placement flag off.
125 driver tests,326 focused regressions/all219424 ladder orderings, lint and12 mutation kills passed. The original full native-ai suite remains failed:7failed/13428passed/640skipped/1xfailed. All six nonlive failures now pass on the implementation and unchanged baseline after verification-process-only open-file limit, short temporary path, Git default-branch and exact historical-object recovery. No tests, source, markers or frozen fixtures were changed. A separate socket control also passed with the original eight-worker layout.
The live D8 jailed-Claude timeout remains unqualified, with cause unproven. The successful upstream hosted-main JUnit skipped that live case for absent credentials; it is not live-seat or local implementation proof. AC6 and the failed lifecycle remain unmet. The original full runner must pass before supported implementation publication; a prepared runner retains the live test and original gate scope while recording the measured environment repairs.
Next: refresh source/upstream and actual seat readiness, rerun the original full verification, then complete actual-source seven-role CR, independent review, manual tools-enabled Opus5.5 max subscription self-PTY and owner-approved Gemini3.8FlashHigh, actual Fable-only president, exact-head hosted checks and postmerge proof. Required Opus/president attempts on other work reported weekly429/reset October17 at18UTC/2pmEastern. Authentication works but does not prove quota readiness. No weaker model, SDK/API or president fallback.
Upstream main18861766 changed only the gitleaks allowlist since6ec; its newly observed test run is not claimed passed. agent-harness#1549 remains separate and open. agent-harness#1502 launch wiring, agent-harness#1506 backend contracts and agent-harness#896 follow-ons remain. SSH-first stays driver verification, separately reviewed flag-off SSH/harmless qualification, reconnect, actual required placed Opus TUI, subordinate-uid Codex/Grok and cloud. No backend, dependency, license, architecture, flag-on or merge adoption is claimed.
Need help on this PR? Tag
@codesmith-botwith what you need.