chore(SessionLedger): add MIT LICENSE - #444
Conversation
🤖 CodeAnt AI — Review Status
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
|
Warning Review limit reached
Next review available in: 5 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
codeant-ai
Bot
added
the
size:S
![codeant-ai[bot]](https://avatars.githubusercontent.com/in/646884?s=60&v=4){kind=small}
| @@ -0,0 +1,22 @@ | |||
| MIT License | |||
There was a problem hiding this comment.
Suggestion: The new canonical top-level license identifies the project as MIT-only, while Cargo.toml, CITATION.cff, and the packaging scripts declare and distribute the project under the dual MIT OR Apache-2.0 terms. Repository hosts and downstream tooling commonly use LICENSE as the authoritative license, so this can misrepresent the project's licensing contract and omit the Apache-2.0 option. Keep the canonical file consistent with the dual-license layout, such as retaining only LICENSE-MIT and LICENSE-APACHE or making this file explicitly describe both licenses. [api mismatch]
Severity Level: Major ⚠️
- ⚠️ License metadata conflicts across repository and packages.
- ⚠️ Downstream users may miss the Apache-2.0 licensing option.
- ⚠️ Automated license detection may report MIT-only licensing.
(Use Cmd/Ctrl + Click for best experience)
Prompt for AI Agent 🤖
This is a comment left during a code review.
**Path:** LICENSE
**Line:** 1:1
**Comment:**
*Api Mismatch: The new canonical top-level license identifies the project as MIT-only, while `Cargo.toml`, `CITATION.cff`, and the packaging scripts declare and distribute the project under the dual `MIT OR Apache-2.0` terms. Repository hosts and downstream tooling commonly use `LICENSE` as the authoritative license, so this can misrepresent the project's licensing contract and omit the Apache-2.0 option. Keep the canonical file consistent with the dual-license layout, such as retaining only `LICENSE-MIT` and `LICENSE-APACHE` or making this file explicitly describe both licenses.
Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fixAdds `crates/sl-viewer/tests/properties_viewer_history.rs` with 15
proptest properties pinning `history_tab::to_timeline_entry` and
`history_tab::all_timeline_entries` reductions:
* `to_timeline_entry`:
* `summary.id`, `summary.title` (mirrors `Option<String>`),
`summary.message_count`, `corpus`, `cwd` are carried through.
* `summary.intent_state` is always `IntentState::Extracted`.
* `message_previews` is capped at 3 (the documented cap) and is
empty when the session has no messages.
* `total_messages` matches `session.messages.len()`.
* `unfinished` is `false` for empty sessions, `false` when the
last message content (case-insensitive) contains one of the six
documented done-phrases ("looks good", "approved", "ship it",
"all good", "thanks", "done"), and `true` otherwise.
* Deterministic across calls.
* `all_timeline_entries`:
* Output length equals input length.
* Sorted by `total_messages` descending (newest-first by message
count, per the documented comment).
* Every session id appears exactly once.
* Deterministic across calls.
Updates WBS-6.2 evidence list, TRACEABILITY.json, and CHANGELOG.
Co-authored-by: SessionLedger Bot <team@sessionledger.local>
User description
From WBS audit.
CodeAnt-AI Description
Add an MIT license for permitted software use
What Changed
Impact
✅ Clearer reuse permissions✅ Easier software distribution✅ Explicit warranty and liability terms💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.