Three commits, each landing on its own merit:
refactor(api) name ai's resources for what they are. Five identity nouns came
from casibase and were published under /v1/ai/* while IAM publishes the same
five words at /v1/iam/* — one noun, two addresses, and no way to tell which
held the row. permissions was a pure MIRROR (every method in
controllers/permission.go was an iam.* call), so it and its controller are
gone and the console's two live calls go to IAM directly; checked, both
surviving callers — FileTree.js and PermissionUtil.js — use only the two
functions that remain. users was usage wearing an identity name and is now
/v1/ai/usages/{user-names,by-user}; applications are kubernetes deployments
and are now /v1/ai/deployments; sessions are ai's OWN cookie sessions and
stay, as /v1/ai/signin-sessions.
docs /api/ -> /v1/iam/ in ZAP.md. Prefix only.
fix(license) the Apache-2.0 §4(c) attribution line on 7 upstream-derived files
that carried Hanzo-only copyright.
WHAT IS DELIBERATELY NOT HERE: the branch tip, 55c79e71 "wip: preserve in-flight
work". It is two scratch files and a go.mod line. zzz_surface_measure_test.go
says of itself "TEMPORARY measurement harness (scratch; not for commit)" and
writes its result to a hardcoded /home/z/.cache path — it belongs to whoever was
measuring typed surfaces, not to main. The go.mod half asked for go 1.26.5, which
main already has. So the tip carries nothing main wants and one thing it must not
take; the three commits below it are merged and the tip is left on its branch.
go build ./... clean; ./routers, ., cmd/openapi and cmd/routerdoc green.
Co-authored-by: Hanzo Dev <[email protected]>
Getting Started with Create React App
This project was bootstrapped with Create React App.
Available Scripts
In the project directory, you can run:
npm start
Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.
You may also see any lint errors in the console.
npm test
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
npm run build
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
npm run eject
Note: this is a one-way operation. Once you eject, you can't go back!
If you aren't satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you're on your own.
You don't have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn't feel obligated to use this feature. However we understand that this tool wouldn't be useful if you couldn't customize it when you are ready for it.
Learn More
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
Code Splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
Analyzing the Bundle Size
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
Making a Progressive Web App
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
Advanced Configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
Deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
npm run build fails to minify
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify