Repository navigation
Release 2026-11-19 - #156
Open
github-actions[bot] wants to merge 23 commits into
Open
github-actions[bot] wants to merge 23 commits into
github-actions[bot] wants to merge 23 commits into
Conversation
adr-face-store: one {face}.store.md per face, server keys with a closed load trigger, client keys with a persistence, error defaults per class, store reads and writes as screen and shell outcomes, and data bindings on the shell layout.
store-coherence.sh checks the store's tables, vocabularies and on-change chains, and every store read and write in screens and shells. screen-coherence.sh accepts the store outcomes, several outcomes per cell and the navigation Then column, and checks a shell's bindings. face-exposure.sh checks the actions a store loads and a shell binds. spec-identity.sh holds one store per face and resolves shell_layout:.
…derived contract
A new specification skill owns {face}.store.md. The screen format gains the store forms and the shell layout its bindings; faces gain shell_layout:. The derived contract adds the store kind, the shell's binding claims and DR-K1..4. The React skill renders the store as a seed defaulting to TanStack Query and Zustand.
# Conflicts: # docs/adr/_index.md
A sync PR (head main or sync/) was retargeted to the new release when its own was published; with no commits between them GitHub answered 422 and the loop stopped. Now retarget skips them and closes those whose release is no longer the open one.
On every push to main, the newest release/YYYY-MM-DD branch that is behind it gets a PR from sync/<release>, pointed at main, so conflicts are resolved in the PR without touching main. With the SYNC_RELEASE_APP_ID variable and SYNC_RELEASE_APP_KEY secret, the PR is opened with that App's token, so its required checks run.
`id` is not a universal semantic type and the fixtures carry no semantic-types.md, so INSPIRE Factory refused the clean fixture with DR-T1.
INSPIRE Factory keys units by id alone and refuses a plan where a store shares its id with another unit (PR-14). The review now reports it while the spec is written: a face `admin` beside a layout `admin` is an error.
Several outcomes are joined by "; ". Splitting on any ";" broke a part that holds one, and disagreed with INSPIRE Factory, which splits on "; ".
… pytest check INSPIRE Factory now reads each test check's JSON report, and a run whose plan has units with claims does not start when no check declares one. /inspire-config writes `report` by default, like run_related: the reporter flags in run and run_related (Vitest --reporter=json, Jest --json, pytest --json-report) and the path `.inspire-report-<check>.json` from the root. Updating a file proposes the same for a check without one, and validation flags a missing or mismatched report, pytest without pytest-json-report, and a .gitignore that does not cover it. INSPIRE names no Factory version: the Factory declares the INSPIRE floor. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The release job's token lacked checks, statuses and actions read access, which gh pr checks needs; its error was discarded and a green Release check could read as missing. Same fix as inspire-factory#217. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fix(release): let the daily release read the release PR's checks
A PR into a release branch carries no CHANGELOG change; the release PR writes that version's section.
ci(release): sync the open release with main, and keep retarget off the sync PRs
feat: a face declares its application state in one store (I7)
…spire-config-test-reports
…cks ran
The Factory no longer adds the citing tests to run_related's files: that
is what `{tests}` does. Say instead that a test run_related does not
select never counts in the unit.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An e2e test seldom imports the file a unit changes, so with {files} its
citations never count in the unit. /inspire-config now writes run_related
with {tests} on Jest and Vitest e2e checks, and proposes it on update.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
feat(inspire-config): write the test report of every Jest, Vitest and pytest check
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.
Release diaria. Se publica sola tras la daily si está aprobada y los checks en verde.
Antes de aprobar:
marketplace.json,plugin/manifests/<version>.jsony sección enCHANGELOG.md(skill/template-release)Release notes