feat(lib-core): biblioteca atomica @pulse-libs/core v1.0.0-beta.1

Esta commit conteudo a estrutura atomica completa:

- types:     Result<T,E>, AsyncState<T>, Paginated<T>, SortConfig<T>
- utils:     date, str, num, cn, debounce, throttle, storage, arr, obj
- validators: Zod schemas — email, password, uuid, url, phone, CPF/CNPJ, sanitizedStr, safeParse
- hooks:     useToggle, useAsync, useDebounce, useLocalStorage, useMedia, useInterval, useOnClickOutside, useClipboard, useFetch
- components: Button, Input, Alert, Card, Spinner (atomic design pattern)
- build:     tsup v8 ESM+CJS + DTS + sourcemaps — 0 erros
- tests:     57 testes 100% usuarios
- docker:    multi-stage Dockerfile (node 20-alpine)
- config:    vitest, tsup, tsconfig strict, .npmignore

Filosofia atomica:/utils ← /types ← /validators ← /hooks ← /components
Build: npm run build | Test: npm test | Publish: npm publish

🤖 Generated with Pulse (openclaw + nova-self-improver)
This commit is contained in:
pulse-agent
2026-05-19 21:43:03 -03:00
parent ae39e45460
commit bbdb68a6de
7030 changed files with 2040595 additions and 0 deletions
@@ -0,0 +1,30 @@
# Projects
<!-- ============================================================
PROJECTS.md — Project Registry
============================================================
FORMAT: One ## block per project. The slug (## heading text)
is the canonical project ID used in task IDs, file names,
and SQLite foreign keys. Keep it lowercase and hyphenated.
FIELDS:
Name Human-readable display name (any capitalization).
Status One of: active | paused | done
Description One-sentence summary of the project's purpose.
FILE CONVENTIONS:
Task file: tasks/<slug>-tasks.md (required)
Plan file: plans/<slug>-plan.md (optional)
NOTE: Do not add task counts or progress bars here. Those are
computed by the sync/export scripts and belong in dashboards,
not in this registry file.
============================================================ -->
## example-project
- Name: Example Project
- Status: active
- Description: A starter project to demonstrate the TaskFlow format — replace with your own.
<!-- Add additional ## blocks below. Each block is one project. -->
@@ -0,0 +1,61 @@
# {{Project Name}} — Plan
<!-- ============================================================
PLAN FILE
============================================================
File name: plans/<slug>-plan.md
This is a freeform architecture/design document. It is NOT
synced to SQLite. Agents read it at session start for context.
It is the right place for:
- High-level vision and goals
- Architecture decisions (with rationale)
- Phase breakdowns and milestones
- Open questions and tradeoffs
- Anything too long or structural for a task line
There is no required format. The sections below are suggested
starting points — delete or rename them freely.
============================================================ -->
## Vision
<!-- What is this project trying to accomplish? What does success look like?
One paragraph. Be concrete. -->
## Architecture
<!-- How is the system structured? Key components, data flows, external dependencies.
Diagrams (ASCII or Mermaid) welcome. -->
## Decisions
<!-- Resolved design decisions. Format: short title + rationale.
Example:
| # | Decision | Resolution |
|---|---|---|
| 1 | Auth strategy | Use OAuth2 PKCE — avoids storing client secrets server-side |
| 2 | Storage | SQLite for local, S3 for media — keeps infra simple |
-->
## Open Questions
<!-- Unresolved questions or tradeoffs still being evaluated.
Remove items as they are resolved (move to Decisions above).
Example:
- Should we paginate the feed at 20 or 50 items?
- Redis vs. in-process cache for rate limiting?
-->
## Phases / Milestones
<!-- Optional. Break down the project into phases or milestones.
Example:
### Phase 1 — MVP
- Core sync logic
- Basic CLI
### Phase 2 — Polish
- Error handling
- Tests
-->
@@ -0,0 +1,57 @@
# {{Project Name}} — Tasks
<!-- ============================================================
TASK FILE FORMAT
============================================================
File name: tasks/<slug>-tasks.md
One file per project. Slug matches the ## heading in PROJECTS.md.
TASK LINE FORMAT:
- [x| ] (task:<slug>-NNN) [<priority>] [<owner>] <title>
FIELDS:
[ ] / [x] Open / completed. The sync engine drives status
from the section header, not this checkbox.
Use [x] for Done (and optionally Pending Validation).
(task:<id>) Task ID. Format: <slug>-NNN (zero-padded, sequential).
Custom prefixes are allowed but tooling assumes this pattern.
[<priority>] REQUIRED. Must come BEFORE the owner tag.
Defaults: P0 (critical) | P1 (high) | P2 (normal) | P3 (low) | P9 (someday)
[<owner>] Optional. Agent or model tag (e.g., codex, sonnet, claude).
<title> Human-readable task title.
NOTES (optional, immediately below task line):
- note: <text>
⚠️ Notes are one-way in v1: removing a note in markdown does
not clear it in the DB. This is a known limitation.
SECTION HEADERS (fixed — do not rename):
## In Progress → DB status: in_progress
## Pending Validation → DB status: pending_validation
## Backlog → DB status: backlog
## Blocked → DB status: blocked
## Done → DB status: done
TAG ORDER RULE:
Priority tag MUST come before owner tag. The parser is positional.
✅ - [ ] (task:myproject-007) [P1] [codex] Implement search
❌ - [ ] (task:myproject-007) [codex] [P1] Implement search
============================================================ -->
## In Progress
## Pending Validation
## Backlog
<!-- Example task — replace with your own and assign the next sequential ID -->
- [ ] (task:{{slug}}-001) [P2] First task for this project
## Blocked
## Done