Repository navigation
refactor: frontend as innate-fe domain plugin, add swagger (issue #2) - #3
Merged
Merged
Conversation
Split datasource from frontend and make the frontend a pluggable domain (track A) while keeping this repo standalone. - frontend becomes @innate/domain-feeds: exports webDomain (routes + navItems/homeTile capability) + plugin.json for innate-fe-cli gen - drop shell chrome (AppSidebar/AppHeader/theme) and vendored shadcn components/ui; @innate/ui + @innate/web-domain come from innate-fe-cli install (private registry, no local packages/ mirror) - standalone host keeps a compact grouped left nav (GitHub / DeepSeek Harness) driven by the same navItems capability - fix dsh route hooks that broke under the pathless layout - backend: OpenAPI spec + Swagger UI at /docs - CI/deploy checkout innate-fe and run innate-fe-cli install; add dev/dev:seed/setup:innate scripts - docs: datasource/frontend separation analysis + migration plan
The Folo gitlink was dangling (no .gitmodules ever committed), so clones reported a permanent phantom deletion and the pin carried no intent. Record external sources declaratively in registry.yaml instead: repo URL, pinned commit, kind (research), and the docs that analyzed it. Sources are checked out on demand and never vendored into this tree.
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.
Closes #2
Summary
Refactor per issue #2: confirm datasource/frontend separation, then make the frontend a pluggable innate-fe domain while keeping this repo standalone.
Analysis (
docs/arch-design/datasource-frontend-separation.md): separation already holds — the frontend only reaches data viaservices/(API + static dual-mode). Three couplings recorded (types written twice,shared/not a real package, basic UI embedded in the frontend).Migration (
docs/arch-design/innate-fe-plugin-migration.md) implemented P0–P2, P4:frontendbecomes@innate/domain-feeds(track A domain): exportswebDomain(routes +navItems/homeTilecapability) andplugin.json, soinnate-fe-cli gencan pull it into a webshell — this repo is not merged into innate-fe.AppSidebar/AppHeader/theme + vendored shadcncomponents/ui/, ~8.6k lines).@innate/ui/@innate/web-domaincome frominnate-fe-cli install(private registry) — the localpackages/mirror was verified redundant and dropped.navItemscapability the plugin mode consumes.from: "/dsh/...")./docs.Folodangling gitlink replaced by declarativeregistry.yaml.innate-fe-cli install;dev/dev:seed/setup:innatescripts.Verification
bun run typecheck(backend + frontend) cleanbun run test— 34 passedVITE_STATIC_MODE=true,404.html/.nojekyll/107 manifest chunks, base path correct)/docsall exercised via PlaywrightNotes for reviewers
INNATE_FE_TOKENrepo secret is required for CI to read the privatevariableway/innate-febase repo.plugins.registry.yamland runninggenfor real) needs a change on the innate-fe side.