check:features

Introduction

check:features checks every feature your selected product declares. It tells you where each one lives, whether its link in features/ works, whether it is installed and, for an editable one, whether its git tree is clean.

splent check:features

  splent_io/splent_feature_notes@v1.2.7
  [✔] Found in cache
  [✔] Symlink OK (relative)
  [✔] Installed in the product container (active)

  splent_io/splent_feature_reports
  [✔] Found in workspace root
  [✔] Symlink OK (relative)
  [⚠] Not installed yet (product:derive installs it)
  [⚠] Uncommitted changes

  All features OK (5 checks passed).

Warnings do not fail it. A failed check ([✖]) ends the run with N check(s) failed. and exit 1. splent doctor runs it in its Product section.

---

Fixing what it reports

A feature that is not found, or a missing or broken link, is fixed by product:resolve, which fetches the pinned releases and links every feature. A feature not installed yet is installed by product:derive.

---

Reference

It reads features plus the list of the current environment, features_dev when SPLENT_ENV is unset, features_prod for prod or production and features_test for test or testing.

Check	Pinned feature	Editable feature
Location	In .splent_cache/, with src/	At the workspace root, with src/
Link	A relative link in features/ to the cache	A relative link in features/ to the workspace root
Install	Installed according to the product’s manifest, which the web container’s install script updates, or present in the CLI’s own Python	The same
Git	Not checked	A clean working tree, else a warning

An absolute link, or a folder where a link should be, is a warning.

It needs a selected product (SPLENT_APP). Without one it prints ❌ SPLENT_APP not set. and exits 1.

See feature:status for the lifecycle state and mode of each feature.