6 Commits

Author SHA1 Message Date
0xKT
8700656155 chore(*): merge upstream v0.1.11 into the gitlab trunk
Absorbs the GitHub release into the downstream trunk. A merge rather than a
rebase so v0.1.11 becomes a real ancestor: the next sync then starts from
v0.1.11 instead of the July fork point, and the eventual contribution back to
GitHub can tell our commits from the upstream ones it already has.

Notable conflict resolutions, 19 hunks over 14 files:

* providers/litellm_provider.py takes upstream's wire_model delegation. Both
  sides had fixed the same gateway-prefix bug; upstream moved the logic into
  providers/wire.py and deleted _canonicalize_explicit_prefix, so keeping our
  call would reference a method that no longer exists.
* cli/onboard_commands.py takes upstream's three-way file split. Our only
  change to that file was _NON_CREDENTIAL_CHANNEL_FIELDS, ported to its new
  home in cli/onboard_channels.py.
* agent/loop/main.py keeps our stream reconnect loop and grafts upstream's
  terminal error-delta handling into it; takes upstream's _route_result_images
  helper, which also covers the no-vision case our inline version did not, and
  keeps our read_skill/use_skill reporting; takes upstream's ordering that
  routes before assembly, since assembly decides whether an attachment is
  inlined as a picture, while keeping our per-session model override.
* agent/subagent/manager.py keeps our backend dispatch and spawn history, and
  threads the provider/model pair spawn snapshots into backend.run so a live
  /model switch reaches subagents. The SubagentBackend protocol gained the
  pair as optional keywords, travelling per call for the same reason workspace
  already does.

Three breakages git merged cleanly and never flagged:

* web_rpc/methods_config.py imported six EverOS symbols from onboard_commands,
  which upstream moved to onboard_everos.
* tui_rpc/methods/turn.py passed a single directory to _resolve_path, whose
  third parameter we had changed to a tuple. Left as it was, an attachment was
  dropped in silence whenever restrict_to_workspace is on.
* config/schema.py carried a second configuredness rule next to the one
  upstream routes through providers.auth, so routing bypassed the
  endpoints-first check and read a flat key that no request would use. It now
  delegates, with include_external for parity with list_providers.

Verification: uv run ruff check passes; uv run pytest reports 6823 passed and
4 failed. All four fail on origin/main as well (one theme assertion, three
channel QR cases) and are left for a separate fix. Upstream's own 53 changed
test files pass, and so do our 85, which is what pins both sides' semantics
through these resolutions.

Co-authored-by: Claude (claude-opus-5) <noreply@anthropic.com>
2026-08-12 23:59:07 +08:00
LivXue
2a6f46c1eb feat(*): bring the ravenx core work onto the shared trunk
Land the accumulated core development from the ravenx workspace as a
single change on top of origin/main. It covers the gateway web-app RPC
channel, pluggable sub-agent execution backends with third-party CLI
and OpenAI-API presets, the sub-agent DAG subsystem and its TUI
surface, vendor-aware provider resolution, the deliverable token store
and the deliver_files tool, and the skill tool gating rework.

The web UI itself is deliberately excluded. ui-webui/ and
start_webapp.sh land separately, together with the lint ignores and the
third-party notice that reference them, because the repository asset
policy for that tree has to be settled first.

Condensed from 68 commits whose history predates this repository's
linear-trunk rule; the three-way merge against origin/main applied
without conflicts.

A follow-up commit fixes a stale assertion that arrived with the import:
read_local_body grew hub-shaped metadata and its test still described
the older four-key return.

Co-authored-by: Claude (claude-opus-5) <noreply@anthropic.com>
2026-08-06 09:44:24 +00:00
0xKT
cfa76989a3 docs: closing keyword goes in the PR description, once per issue (#283)
## Summary

GitHub pairs one closing keyword with one reference. `Fixes #NNN, #MMM`
closes
the first and merely mentions the second. PR #279 wrote seven issues
after a
single keyword and left six of them open after merge; they were closed
by hand.

Two one-line changes state the rule where a description actually gets
written:

- `.github/pull_request_template.md` - the `Related Issues` hint.
- `AGENTS.md`, section 3.7 - the `Related Issues` filling rule.

A third drops `Closes #123` from the commit-footer list in section 3.1.
That
line was wrong on its own terms: section 3.3 already records that this
repo
squash-merges and drops individual commit bodies, so a closing keyword
in a
commit footer never reaches `main` and closes nothing.

The template hint also stops naming `#123`, which is a live open issue
here, and
a placeholder should not be a real number.

## Type

- [ ] Fix
- [ ] Feature
- [x] Docs
- [ ] CI / tooling
- [ ] Refactor
- [ ] Other

## Verification

Documentation only; no code paths change.

```
uv run pre-commit run --from-ref origin/main --to-ref HEAD   -> all hooks Passed or Skipped
make lint-python                                             -> ruff check / format --check clean
make test-python                                             -> 5525 passed, 48 skipped,
                                                                13 deselected in 271.05s
npx commitlint --from origin/main --to HEAD --config commitlint.config.cjs   -> OK
PYTHONPATH=. uv run python scripts/check_commit_messages.py origin/main..HEAD -> OK
PYTHONPATH=. uv run python scripts/check_large_files.py origin/main..HEAD     -> OK

grep -nP "[^\x00-\x7F]" .github/pull_request_template.md     -> 0 matches. The template is
    embedded into every PR description, which CI lints as ASCII-only, so it has to stay ASCII.
```

- [x] Relevant tests pass locally
- [x] Relevant lint / type checks pass locally
- [x] User-facing docs or screenshots are updated when needed

## Risk

No behaviour change. The visible effect is a slightly longer hint under
`Related Issues` when a new PR opens.

Rollback is a revert of this branch.

- [x] Security impact considered
- [x] Backward compatibility considered
- [x] Rollback path is clear for risky changes

## Related Issues

N/A

---------

Co-authored-by: Claude (claude-opus-5[1m]) <noreply@anthropic.com>
2026-08-10 12:17:53 +08:00
Elliot Chen
7f180b42ae chore: prepare repository for public launch (#13)
## Summary
- switch project metadata and license text to Apache-2.0 while retaining
upstream notices
- add public-ready community files: issue templates, SECURITY,
CONTRIBUTING, CODE_OF_CONDUCT, Dependabot, and a stricter PR template
- align README license copy with the public launch posture

## Repository settings updated via GitHub API
- squash-only merge enabled; merge commit and rebase merge disabled
- delete branch on merge and update branch enabled
- Discussions enabled; Projects and Wiki disabled
- Actions default workflow permissions set to read-only and PR
self-approval disabled
- description and homepage updated for Raven

## Verification
- npm ci --ignore-scripts --no-audit --no-fund (root)
- npm ci --ignore-scripts --no-audit --no-fund (ui-tui)
- npm ci --ignore-scripts --no-audit --no-fund (bridge)
- npx --no-install commitlint --from origin/main --to HEAD --config
commitlint.config.cjs
- PYTHONPATH=. python3 scripts/check_commit_messages.py
origin/main..HEAD
- uv run pre-commit run --from-ref origin/main --to-ref HEAD
- git diff --check origin/main...HEAD

## Notes
- GitHub branch protection/rulesets returned 403 while the repository is
private on the current plan. Enable required checks after making the
repository public.
- Auto-merge remained disabled after the API patch, likely due
repository/org availability or policy.
2026-06-30 13:00:28 +08:00
JasonJarvan
15ea43ee8e docs: point commit-scope at README and finish public-phase cleanup
Replace the hardcoded, stale commit-scope list in CLAUDE.md section 3.3
with a pointer to the README Repo layout section, and finish the
public-phase wording: drop the internal-AI-stats framing and the
GitLab-era JIRA / merge-request residue from the trailer rules, the
PR-open flow, and the PR template.

Co-authored-by: Claude (claude-opus-4-8) <noreply@anthropic.com>
2026-06-29 09:05:11 +00:00
0xKT
dc0fb2822c raven init 2026-06-29 00:23:07 +08:00