Repository navigation
docs: carry ready-session timeout entries into operational-home-layout skill - #81
Merged
Merged
Conversation
Take upstream's operational-home-layout skill and add only the ready-session-timeout config and <id>.ready-timeout state lines. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
feat: merge upstream main into ready-session timeout and move its layout lines into the home-layout skill
…ut' into fm/ready-session-timeout-house-integration-r2
jazz127
added
the
house-only
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
1 participant
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.
Purpose
Integrate the ready-session timeout feature’s instructions into
housethrough its durablehousefeature/ready-session-timeoutbranch, after the upstream layout merge.Change
This merge adds the
config/ready-session-timeoutandstate/<id>.ready-timeoutrows to.agents/skills/operational-home-layout/SKILL.md. Current house behavior and other feature lines are preserved. The durable branch is house-based, so this is not a clean upstream contribution candidate.Validation and merge order
The upstream merge into
houselanded first. No-mistakes passed review, targeted tests, documentation, and lint; house CI is running. The pipeline’s local probes are synthetic/offline built-CLI validation, with no real-account validation claimed.evidence-artifact: /tmp/fm-firstmate-upstream-5872-merge-r1/pr81-evidence.txt
evidence-command: no-mistakes axi status
evidence-captured: 2026-09-27T13:47:52Z
Pipeline attestation