@adula/kit 0.2.0-alpha.1 → 0.2.0-alpha.2

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/README.md CHANGED
@@ -1,10 +1,10 @@
1
1
  # @adula/kit
2
2
 
3
- Unreleased 0.2.0-alpha.1 resource framework for AdonisJS 7 and PostgreSQL 17. Node 24 or later is required. MIT licensed. The target is the complete approved 1.0 scope; it has not passed acceptance.
3
+ Experimental 0.2.0-alpha.2 resource framework for AdonisJS 7 and PostgreSQL 17. Node 24 or later is required. MIT licensed. The target is the complete approved 1.0 scope; it has not passed acceptance.
4
4
 
5
5
  ## Install into a consumer
6
6
 
7
- Follow the canonical [installation guide](https://github.com/adulash/adula-kit/blob/main/docs/installation.md). For a new application, the separate `@adula/create-app` initializer installs the AdonisJS host and application screens from an empty directory; it is available locally until publication. For an existing official AdonisJS 7 React/PostgreSQL application, install the kit/UI archives and documented UI prerequisites, configure the kit, migrate and create the intended administrator before `node ace adula:install`. The Ace command completes initialization inside that host. No educational customers/orders/tasks modules are installed by either path.
7
+ Follow the canonical [installation guide](https://github.com/adulash/adula-kit/blob/main/docs/installation.md). For a new application, the separate `@adula/create-app` initializer installs the AdonisJS host and application screens from an empty directory; it is published on npm as an experimental alpha. For an existing official AdonisJS 7 React/PostgreSQL application, install the kit/UI archives and documented UI prerequisites, configure the kit, migrate and create the intended administrator before `node ace adula:install`. The Ace command completes initialization inside that host. No educational customers/orders/tasks modules are installed by either path.
8
8
 
9
9
  The managed rules require the bundled `.agents/skills/adula-frontend-design/SKILL.md` for UI work. It is tailored to business workflows, asks for missing company identity at project kickoff, and uses project-owned shadcn components with modal forms and record details by default. User-requested presentation exceptions remain supported. Company identity belongs in `docs/design-identity.md`, which installation never overwrites. Doctor verifies the design skill along with the idea-review skill.
10
10
 
@@ -28,4 +28,4 @@ Doctor measures the deployment's `storage/uploads` directory and warns above 5 d
28
28
 
29
29
  ## Current limitations
30
30
 
31
- Attachment ownership, upload/download, storage migration, authentication lifecycle/rate limiting, generic resource UI and core administration have local integration consumers and tests. Real OAuth/SMTP, full Tuyau field contracts, human/performance acceptance, XState workflows, later business features, staging/offsite restoration and a genuine minor-version consumer upgrade remain open. Submission envelopes are durable records in pending_definition state, not running workflows. See [implementation status](https://github.com/adulash/adula-kit/blob/main/docs/implementation-status.md), [gaps](https://github.com/adulash/adula-kit/blob/main/KIT_GAPS.md) and [1.0 acceptance](https://github.com/adulash/adula-kit/blob/main/docs/acceptance-1.0.md). No package has been published.
31
+ Attachment ownership, upload/download, storage migration, authentication lifecycle/rate limiting, generic resource UI and core administration have local integration consumers and tests. Real OAuth/SMTP, full Tuyau field contracts, human/performance acceptance, XState workflows, later business features, staging/offsite restoration and a genuine minor-version consumer upgrade remain open. Submission envelopes are durable records in pending_definition state, not running workflows. See [implementation status](https://github.com/adulash/adula-kit/blob/main/docs/implementation-status.md), [gaps](https://github.com/adulash/adula-kit/blob/main/KIT_GAPS.md) and [1.0 acceptance](https://github.com/adulash/adula-kit/blob/main/docs/acceptance-1.0.md). Version 0.2.0-alpha.2 targets alpha; the owner-authorized latest alias remains on 0.2.0-alpha.1.
@@ -1,6 +1,6 @@
1
1
  # Current capabilities
2
2
 
3
- Version 0.2.0-alpha.1, unreleased. Resource definitions and registry; six flat condition operators (typed limits documented in KIT_GAPS.md); CASL evaluation with structural ltree scope; JSON/Inertia resource CRUD; field contracts; keyset pagination; sequences/lookups/settings; soft deletion; optimistic concurrency; atomic inline writes/activity/outbox; deduplicated database listeners; org moves; attachment ownership/storage migration; saved views; core administration services; resource/module commands; copied shadcn UI and installation diagnostics.
3
+ Version 0.2.0-alpha.2, experimental alpha. Resource definitions and registry; six flat condition operators (typed limits documented in KIT_GAPS.md); CASL evaluation with structural ltree scope; JSON/Inertia resource CRUD; field contracts; keyset pagination; sequences/lookups/settings; soft deletion; optimistic concurrency; atomic inline writes/activity/outbox; deduplicated database listeners; org moves; attachment ownership/storage migration; saved views; core administration services; resource/module commands; copied shadcn UI and installation diagnostics.
4
4
 
5
5
  The reference consumer wires authentication/session lifecycle, admin screens, authorized attachments, optional MCP, Redis actor caching, a queue worker, one scheduler and backup/restore drills. Educational modules are isolated test fixtures, not installed application features. The agent ships business frontend-design and idea-review skills, company identity intake and modal defaults. Real SMTP receipt/recovery and isolated offsite local/source-S3 attachment recovery are documented in the source repository's confirmed-achievements ledger. OAuth is optional and externally unverified. Source-S3 recovery is integrated into the operational backup commands and verified directly; local Docker backup/recovery also passed; natural scheduled operation and staging remain pending; each consumer must verify its own configuration.
6
6
 
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@adula/kit",
3
3
  "description": "Resource-driven business applications for AdonisJS 7",
4
- "version": "0.2.0-alpha.1",
4
+ "version": "0.2.0-alpha.2",
5
5
  "engines": {
6
6
  "node": ">=24.0.0"
7
7
  },