Conversation
Retire the Intent Trace authoring scope. The requirements module gains thin runtime wiring for import-first requirement evidence: --from-openspec and --from-speckit flags with conservative layout auto-detection, gate-finding surfacing in validate with CI-usable exit codes, and layered-config profile resolution when --profile is omitted. Parsing, hashing, and gate logic stay core-owned (nold-ai/specfact-cli#350). Reprioritize Track B: openspec-01 moves to order 2, requirements-03-backlog-sync is parked as of 2026-07-13. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Runtime shipped via PR #326 (issue #165 closed 2026-07-08). Archive merges delta specs into canonical openspec/specs (requirements-module, backlog-adapter, module-io-contract); the two deltas targeting not-yet-existing canonical specs were converted from MODIFIED to ADDED to seed those specs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…tasks Validate command switches from a hardcoded startup profile default to core layered-config resolution when --profile is omitted; explicit flag wins. Paired with core scope in nold-ai/specfact-cli#350. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
## Summary - implement #168 using the shipped core #350 native OpenSpec and Spec Kit import helpers - add fail-closed schema handling, conservative source auto-detection, profile-aware validation, and core gate-count reporting - update `docs/Gemfile.lock` to concurrent-ruby 1.3.7 ## Scope This PR delivers the requirements-module adapter work for #168. It also includes a small companion `specfact-code-review` correction: the KISS parameter-count analyzer now identifies actual Typer applications before exempting their callbacks. That prevents the requirements CLI from producing a false-positive warning while retaining checks for unrelated `*.command` and `*.callback` decorators. ## Bundle impact - `nold-ai/specfact-requirements` released as `0.2.3`, with synchronized registry artifact and integrity metadata. - `nold-ai/specfact-code-review` released as `0.47.51`, with synchronized registry artifact and integrity metadata. ## Validation - `hatch run test` — 884 passed, with 2 third-party deprecation warnings. - `hatch run smart-test` — 884 passed. - `hatch run contract-test` — 28 passed. - `openspec validate openspec-01-intent-trace --strict` — passed. - Changed-code review — 0 findings. - Module signature/version-bump verification — passed. ## Documentation - Updated the Requirements bundle overview, generated command references, and `llms.txt` for optional native-source paths. - Recorded failing-before and passing-after evidence in the active OpenSpec change. ## CI and checklist - [x] Formatter, lint, type, import-boundary, manifest, and signature checks pass. - [x] Requirements and code-review regression coverage added. - [x] Registry artifacts match the released manifest versions. - [x] No CI-skip markers are used. Closes #168 --------- Co-authored-by: Dominikus Nold <djm81@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
## Summary Prepare corrected releases for the requirements and code-review modules: - `nold-ai/specfact-requirements`: `0.2.3` → `0.2.4` - `nold-ai/specfact-code-review`: `0.47.51` → `0.47.52` ## Root cause The prior feature PR committed registry entries and tarballs before the canonical `publish-modules` workflow ran. The source manifests were later signed by CI, while the committed tarballs still embedded unsigned manifests. Because `dev` already recorded the same versions, a manual publish dispatch selected no corrective release. ## Release path This change intentionally leaves `registry/**` untouched and keeps local manifests checksum-only. After merge to `dev`, CI must generate the signed manifest and registry publication PRs for these new versions. ## Validation - `hatch run yaml-lint` - `hatch run verify-modules-signature --payload-from-filesystem --enforce-version-bump --allow-missing-public-key` - pre-commit format, YAML, import-boundary, command-reference, documentation, and manifest-signature checks --------- Co-authored-by: Dominikus Nold <djm81@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Automated registry publish update from workflow run 29364507530. Bundle selection reasons: - `specfact-code-review`: changed, registry-outdated - `specfact-requirements`: changed, registry-outdated Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
Strix is installed on this repository, but we couldn't run this PR security review because this workspace's trial has ended. Add a card to resume code reviews here. |
Contributor
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 26 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (7)
📒 Files selected for processing (42)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
djm81
added
documentation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7f120bd415
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
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.
Summary
Promote the current
devbranch tomain.Included release work
0.2.4and Code Review0.47.52.Validation
Validation was completed on the contributing PRs, including module-signature, manifest, lint, contract, and test gates.
Note
devandmainhave diverged; resolve any GitHub-reported merge conflicts before merge.