fimo 2.4.0-staging.1 → 2.4.0-staging.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/assets/skills/fimo-cli/SKILL.md +3 -2
- package/assets/skills/fimo-cli/references/agent-setup.md +2 -1
- package/assets/skills/fimo-cli/references/agents.md +13 -1
- package/assets/skills/fimo-cli/references/branches.md +4 -4
- package/assets/skills/fimo-cli/references/deploy.md +3 -6
- package/assets/skills/fimo-cli/references/domains.md +5 -5
- package/assets/skills/fimo-cli/references/forms.md +4 -2
- package/assets/skills/fimo-cli/references/hosting.md +5 -4
- package/assets/skills/fimo-cli/references/preview.md +1 -1
- package/assets/skills/fimo-cli/references/projects.md +5 -5
- package/assets/skills/fimo-cli/references/site-checks.md +73 -0
- package/assets/skills/fimo-code/SKILL.md +1 -0
- package/assets/skills/fimo-code/references/assets.md +4 -2
- package/assets/skills/fimo-code/references/best-practices/next.md +0 -2
- package/assets/skills/fimo-code/references/content/schema.md +4 -1
- package/assets/skills/fimo-code/references/design.md +2 -2
- package/assets/skills/fimo-code/references/frameworks/astro.md +37 -1
- package/assets/skills/fimo-code/references/frameworks/compatibility.md +5 -5
- package/assets/skills/fimo-code/references/frameworks/hosting.md +23 -2
- package/assets/skills/fimo-code/references/frameworks/next/app-router.md +7 -21
- package/assets/skills/fimo-code/references/frameworks/next/seo.md +168 -0
- package/assets/skills/fimo-code/references/frameworks/next.md +1 -1
- package/assets/skills/fimo-code/references/frameworks/seo-head.md +78 -0
- package/assets/skills/fimo-code/references/frameworks/sveltekit.md +57 -4
- package/assets/skills/fimo-migration/SKILL.md +33 -33
- package/assets/skills/fimo-migration/references/content.md +1 -1
- package/assets/skills/fimo-migration/references/frameworks/nextjs.md +7 -0
- package/assets/skills/fimo-migration/references/import-contract.md +4 -6
- package/assets/skills/fimo-migration/references/manifest.md +4 -3
- package/assets/skills/fimo-migration/references/qa.md +6 -0
- package/assets/skills/fimo-migration/references/questions-and-improvements.md +1 -1
- package/assets/skills/fimo-migration/references/workflow.md +7 -5
- package/assets/skills/fimo-studio/references/agents.md +7 -1
- package/assets/skills/fimo-studio/references/billing-and-credits.md +21 -7
- package/assets/skills/fimo-studio/references/seo-settings.md +2 -0
- package/dist/cli/bundle.json +2 -2
- package/dist/cli/index.js +502 -986
- package/dist/runtime/astro/server-runtime.js +2 -2
- package/dist/runtime/paths/get-fimo-paths.js +1 -1
- package/dist/runtime/seo/head.d.ts +31 -0
- package/dist/runtime/seo/head.js +47 -0
- package/dist/runtime/seo/index.d.ts +2 -0
- package/dist/runtime/seo/index.js +1 -0
- package/dist/runtime/seo/resolver.d.ts +16 -2
- package/dist/runtime/seo/resolver.js +10 -0
- package/dist/runtime/seo/server.d.ts +13 -0
- package/dist/runtime/seo/server.js +23 -0
- package/dist/runtime/shared/branch-identity.d.ts +3 -5
- package/dist/runtime/shared/branch-identity.js +3 -5
- package/dist/runtime/shared/fimo-config.server.d.ts +2 -0
- package/dist/runtime/shared/fimo-config.server.js +18 -14
- package/dist/scripts/export-static.d.ts +3 -4
- package/dist/scripts/export-static.js +3 -20
- package/dist/scripts/sync-schemas.js +12 -5
- package/package.json +12 -8
- package/templates/astro/.fimo/config.json +1 -0
- package/templates/astro/AGENTS.md +1 -1
- package/templates/astro/astro.config.mjs +1 -0
- package/templates/astro/package.json +2 -2
- package/templates/astro/src/layouts/Base.astro +20 -4
- package/templates/astro/src/pages/[locale]/index.astro +1 -1
- package/templates/astro/src/pages/[locale]/projects/[slug].astro +4 -1
- package/templates/astro/src/pages/index.astro +1 -1
- package/templates/astro/src/pages/projects/[slug].astro +4 -1
- package/templates/nextjs/AGENTS.md +1 -1
- package/templates/nextjs/package.json +3 -3
- package/templates/nextjs/src/app/layout.tsx +5 -3
- package/templates/nextjs/src/app/page.tsx +6 -0
- package/templates/react-router/package.json +4 -4
- package/templates/sveltekit/AGENTS.md +1 -1
- package/templates/sveltekit/package.json +2 -2
- package/templates/sveltekit/src/routes/+layout.server.ts +4 -0
- package/templates/sveltekit/src/routes/+layout.svelte +12 -0
- package/templates/sveltekit/src/routes/[[locale=locale]]/+page.svelte +0 -5
- package/templates/vite/package.json +4 -4
- package/assets/skills/fimo-migration/scripts/build-canonical-manifest.mjs +0 -595
|
@@ -19,13 +19,13 @@ From a linked project directory, `fimo credits` shows the same organization bala
|
|
|
19
19
|
|
|
20
20
|
## Buying More Credits
|
|
21
21
|
|
|
22
|
-
Buying credits is available
|
|
22
|
+
Buying credits is available while a paid plan is effective, including after scheduling its cancellation. Cancellation stops automatic spending immediately but keeps the current plan until renewal. A deliberate credit purchase still charges the payment method on file.
|
|
23
23
|
|
|
24
24
|
1. Click the credit display near the chat input.
|
|
25
25
|
2. Click **Buy credits**.
|
|
26
26
|
3. Enter a dollar amount (up to $10,000) or pick one of the presets: **$25**, **$50**, **$100**, or **$200**.
|
|
27
|
-
4.
|
|
28
|
-
5. Confirm the purchase. Your card on file is charged and the credits are added
|
|
27
|
+
4. Check the rate shown in the dialog. It comes from your current plan, so the same dollar amount can buy a different number of credits on Pay as you go than on Pro.
|
|
28
|
+
5. Confirm the purchase. Your card on file is charged and the credits are added after confirmation; there is no separate checkout page to complete. If confirmation stays pending, retry the same purchase or contact support. Do not start another purchase to replace an unresolved one.
|
|
29
29
|
|
|
30
30
|
## Refilling Credits Automatically
|
|
31
31
|
|
|
@@ -33,9 +33,9 @@ Organization billing admins on a paid plan can configure auto-refill from **Sett
|
|
|
33
33
|
|
|
34
34
|
1. Choose the balance threshold that should trigger a refill.
|
|
35
35
|
2. Choose the dollar amount to purchase when the balance crosses that threshold.
|
|
36
|
-
3.
|
|
36
|
+
3. Check the plan rate shown in the dialog, then save. Fimo charges the payment method on file and buys credits at that rate when the balance crosses the threshold.
|
|
37
37
|
|
|
38
|
-
Turn auto-refill off from the same control.
|
|
38
|
+
Turn auto-refill off from the same control. Leaving a paid plan locks automatic-spending controls while Fimo confirms the stop with the billing provider. The page states when confirmation is pending rather than presenting an old enabled setting as current.
|
|
39
39
|
|
|
40
40
|
## Upgrading Your Plan
|
|
41
41
|
|
|
@@ -51,12 +51,26 @@ From there:
|
|
|
51
51
|
3. Pick a plan and complete checkout.
|
|
52
52
|
4. Your new monthly credit pool is available right away.
|
|
53
53
|
|
|
54
|
+
## Extra usage budget
|
|
55
|
+
|
|
56
|
+
Open **Billing & usage**, then **Details** beside public bandwidth. Billing admins on Pay as you go or Pro can edit one **Monthly budget** for extra public bandwidth and autonomous agent runtime. The page shows each meter's cost and **Spent this period**. This budget does not cover AI credit purchases or auto-refill.
|
|
57
|
+
|
|
58
|
+
- Enabling extra usage covers both meters. An existing bandwidth-only budget requires explicit consent before it also covers agent runtime.
|
|
59
|
+
- Agents shows included hours, usage, extra cost, and the reset date, with a link to the shared budget. Pay as you go includes 3 hours, then $0.75/hour; Pro includes 40 hours, then $0.33/hour.
|
|
60
|
+
- At the budget, additional paid usage stops; remaining included allowances stay usable. Running agents stop at a safe point, so stopping is not instantaneous.
|
|
61
|
+
- Disabling extra usage preserves charges already incurred. The budget cannot be lowered below existing extra-usage charges.
|
|
62
|
+
|
|
54
63
|
## Changing or leaving a paid plan
|
|
55
64
|
|
|
56
65
|
- Free to Pay as you go or Pro, and Pay as you go to Pro, use checkout and take effect after payment succeeds.
|
|
66
|
+
- Moving down from a paid monthly plan stops auto-refill and paid extra usage immediately, whether the destination is Free or Pay as you go. The current plan, remaining allowances, credits, and reset date stay unchanged until the destination takes over at renewal. Manual credit purchases remain available while the paid plan is active.
|
|
67
|
+
- Automatic spending cannot be enabled while a plan change is scheduled. Keep your plan first; then you can immediately enable auto-refill and paid extra usage independently. Keeping the plan itself leaves both off.
|
|
68
|
+
- Usage before the change remains payable. Enabling extra usage again does not make usage from the off-period billable.
|
|
57
69
|
- Pro to Pay as you go or Free takes effect at the end of the current billing period. Billing shows the destination and effective date until then.
|
|
58
|
-
-
|
|
59
|
-
- Pay as you go
|
|
70
|
+
- Review the confirmation before scheduling Pro to Pay as you go. It explains the immediate spending stop, retained benefits and charges already incurred; opening it does not change the plan.
|
|
71
|
+
- Switching the scheduled destination between Free and Pay as you go keeps the same effective date and the same moment automatic spending stopped. Nothing is re-granted. Team organizations reach Free through **Cancel subscription**, not the plan dialog.
|
|
72
|
+
- Choosing the current plan again before that date cancels the scheduled change and its Pay as you go successor.
|
|
73
|
+
- Pay as you go requires an active payment method. Removing its only valid card returns the organization to Free immediately, and a scheduled Pay as you go with no card on file lands on Free on its effective date instead.
|
|
60
74
|
- A failed Pro renewal follows the payment-recovery flow. It never silently changes the organization to Pay as you go.
|
|
61
75
|
|
|
62
76
|
## Legacy plan transitions
|
|
@@ -24,6 +24,8 @@ This is the image that shows up when someone shares your link on social media (F
|
|
|
24
24
|
|
|
25
25
|
All SEO changes auto-save as you make them. However, a small amber reminder appears in the top-right corner: "Publish your website to apply your changes." Click Publish to push the changes to your live site.
|
|
26
26
|
|
|
27
|
+
Current templates include SEO wiring. For older Next.js, Astro or SvelteKit sites, ask the coding agent to update Fimo and connect these values to the app's existing SEO flow. Route-specific content must reach that flow too. Load the matching recipe: `fimo skills get fimo-code --ref frameworks/next`, `fimo skills get fimo-code --ref frameworks/astro`, or `fimo skills get fimo-code --ref frameworks/sveltekit`.
|
|
28
|
+
|
|
27
29
|
## Why SEO Matters
|
|
28
30
|
|
|
29
31
|
- **Favicon** -- Makes your site look professional and easy to find among open tabs.
|
package/dist/cli/bundle.json
CHANGED