Packages

Kira now ships with a real package manager and a built-in Foundation package.

The default workflow is official-registry-first, lockfile-backed, and source-only. Local path dependencies and pinned git dependencies are also first-class.

Built-in Foundation

Every managed Kira install now bundles a Foundation package. A plain `import Foundation` resolves to the bundled package first, before any installed package of the same name.

Foundation uses a package source tree under `app/`. That means `app/foundation.kira` is the root `Foundation` module, while files such as `app/Types/Primitives.kira` are visible within the Foundation package tree.

A package manifest

kiraexamples/hello/kira.toml

[package]
name = "Hello"
version = "0.1.0"
kind = "app"
kira = "0.1.0"

[defaults]
execution_mode = "vm"
build_target = "host"

[dependencies]
FrostUI = "0.1.0"
LocalDemo = { path = "../LocalDemo" }
GameKit = { git = "https://github.com/Sunlight-Horizon/GameKit.git", rev = "a1b2c3d4" }

Core commands

Use `kira sync` to resolve and lock dependencies, `kira add` and `kira remove` to edit the manifest, and `kira update` to refresh exact registry versions.

Security rules

Registry archives are verified with SHA-256 before extraction. Packages are source-only. No install scripts, postinstall hooks, lifecycle hooks, or arbitrary shell execution are allowed.

Working with dependencies

kirakira CLI

kira sync
kira add FrostUI
kira add --git https://github.com/Sunlight-Horizon/GameKit.git --rev a1b2c3d4 GameKit
kira remove FrostUI
kira update
kira package pack
kira package inspect generated/Hello-0.1.0.tar

What runs today

The default VM execution path now prints integers, floats, strings, booleans, raw pointers, and named struct values. The native and hybrid backends still have a narrower `print(...)` surface while their lowering/runtime support catches up.