feat(agent-world): Directory section#2
Merged
Conversation
Second Agent World section (off the Wave 0 foundation). Adds the Directory
screen + its native data path, appending only at the foundation's three banners.
- tinyplace core: directory.resolve, directory.reverse, directory.list_identities,
directory.skills handlers (manifest.rs) + controller registration (schemas.rs)
- bridge: directory.{resolve,reverse,listIdentities,skills} over core_rpc_relay
- UI: DirectorySection.tsx ported from tiny.place; mounted at /agent-world/directory
with sub-nav entry (i18n keys already seeded in the foundation)
- tests: directory_section_handlers_are_registered (rust); bridge Vitest (16 total)
Gates green: cargo check, 7 rust tests, typecheck, eslint, vitest 16/16, i18n parity.
Resolve AgentWorld.tsx onto the new TwoPanelLayout shell (Explore + Directory in SECTIONS with icons). Restyle DirectorySection to the app theme + PanelScaffold (drop the dark gray-* classes and the duplicate header).
Relative <Navigate>/navigate under /agent-world/* never matched → blank section. Use absolute /agent-world/<slug> paths. (Directory section had no bg-ocean.)
…e (Directory)
Propagates the Profiles foundation fixes to the Directory section:
- manifest.rs: directory_list_agents fetches raw /directory/agents JSON
instead of the SDK's typed list_agents(), which fails to deserialize
skills/tags (backend returns {id,name} objects, SDK types Vec<String>).
- DirectorySection.getHandle: username may already carry a leading '@';
strip before re-prefixing so handles render once, not @@.
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.
Directory section (section 1 of 6)
Builds on the Wave 0 foundation (#1). Adds the Directory screen and its native data path, appending only at the foundation's three banners — no changes to
core/all.rsor other sections, so this merges cleanly alongside the sibling section PRs.What's in it
directory.resolve,directory.reverse,directory.list_identities,directory.skillshandlers inmanifest.rs+ controller registration inschemas.rs(RPC:openhuman.tinyplace_directory_*).list_agents/get_agentalready existed from the foundation.directory.{resolve,reverse,listIdentities,skills}ininvokeApiClient.tsovercore_rpc_relay.DirectorySection.tsxported from tiny.place, mounted at/agent-world/directorywith a sub-nav entry. i18n keys were seeded in the foundation.directory_section_handlers_are_registered(Rust); bridge Vitest (16 total).Gates (all green locally)
GGML_NATIVE=OFF cargo check· 7 Rust tests ·pnpm typecheck·eslint· Vitest 16/16 ·pnpm i18n:check(missing: 0).Base:
graycyrus/openhuman:main.