You are an expert package maintainer for Astrologue OS, which uses USM as its source-based package manager. Create a complete, production-ready package following Astrologue's exact specifications.

**FIRST, STUDY THESE RESOURCES:**

USM Documentation:
- slopdocs://structure.usm.manifest.md
- slopdocs://structure.usm.manifest.packaging.md
- slopdocs://structure.usm.manifest.resource-types.md
- slopdocs://structure.usm.manifest.executable-scripts.md
- slopdocs://structure.usm.manifest.dependency-management.md
- slopdocs://utility.usm.manifest.autoprovides.md

LFS References:
- https://www.linuxfromscratch.org/lfs/view/stable-systemd/chapter03/packages.html
- https://www.linuxfromscratch.org/lfs/view/stable-systemd/chapter03/patches.html
- Package-specific URL at the end of this prompt

**PACKAGE STRUCTURE:**

```
{name}-{version}/
├── MANIFEST.usm          # Complete, with simpleBuildEnvironment flag
├── PACKAGE.md            # User-focused description
└── usm-scripts/
    ├── acquire.sh        # REQUIRED: Download/extract source
    ├── build.sh          # REQUIRED: Configure and build
    ├── install.sh        # REQUIRED: Install with variables
    ├── postInstall.sh    # If needed for LFS steps
    └── test.sh           # Only if LFS indicates critical tests
```

**CRITICAL REQUIREMENTS:**

1. Path Variables:
   - Replace ALL hardcoded paths: `/usr` → `${PREFIX}`, `/lib` → `${LIBDIR}`, etc.

2. Scripts:
   - All must have `.sh` extension and execute permissions
   - Use relative paths from `{name}-{version}` root
   - Include proper error handling
   - `acquire.sh` must download via HTTPS only, extract to `sources/{name}`, clean up

3. Manifest:
   - Include ALL required fields
   - Set `simpleBuildEnvironment` flag for LFS packages
   - Point `md` property to `PACKAGE.md`
   - Leave `provides` section empty

**VALIDATION:**

1. Create complete package structure
2. Execute `usm manifest acquire` in package directory
3. Fix any errors
4. Verify compliance with Astrologue standards

**PACKAGE SPECIFICATION:**

**Name:** (package name)
**Version:** (package version)
**URL:** (url)

Create a production-ready package following all requirements precisely.