tina4-nodejs 3.13.97 → 3.13.98
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/CLAUDE.md +36 -0
- package/package.json +1 -1
package/CLAUDE.md
CHANGED
|
@@ -1426,6 +1426,42 @@ Always read and follow the instructions in .claude/skills/tina4-developer-nodejs
|
|
|
1426
1426
|
## Tina4-js Frontend Skill
|
|
1427
1427
|
Always read and follow the instructions in .claude/skills/tina4-js/SKILL.md when working with tina4-js frontend code. Read its referenced files in .claude/skills/tina4-js/references/ as needed.
|
|
1428
1428
|
|
|
1429
|
+
## The Uniform Plan (cross-framework audit + consolidations)
|
|
1430
|
+
|
|
1431
|
+
Tina4 is one framework in four languages, so the feature-by-feature audit and the
|
|
1432
|
+
contract-fixture consolidations live in ONE framework-agnostic place, not per
|
|
1433
|
+
repo: **`tina4-documentation/plan/v3/`** (the `tina4-documentation` repo, `main`
|
|
1434
|
+
branch). Cite plan docs by repo-prefixed path.
|
|
1435
|
+
|
|
1436
|
+
- `plan/v3/98-feature-audit.md` - the master audit tracker: audit every feature,
|
|
1437
|
+
pick the best implementation (ADR-0004 "best implementation prevails"), park a
|
|
1438
|
+
plan. Planning first; implementation follows per feature.
|
|
1439
|
+
- `plan/v3/features/NNN-*.md` - one parked plan per feature: the chosen pattern,
|
|
1440
|
+
the methodology, and the tests to write.
|
|
1441
|
+
- `plan/v3/fixtures/*_contract.json` + `plan/v3/CONTRACT-MAP.md` - the executable
|
|
1442
|
+
consolidations. The SAME bytes drive the contract runners in all four
|
|
1443
|
+
frameworks, mapped feature -> fixture -> ADR -> proven/owed.
|
|
1444
|
+
- `plan/v3/DECISIONS.md` + `plan/v3/decisions/` - the ADR log. Consult it before
|
|
1445
|
+
changing any cross-framework contract, and supersede an ADR explicitly rather
|
|
1446
|
+
than silently. `MASTER-SPEC.md` is the feature source-of-truth, but its NUMBERS
|
|
1447
|
+
are stale; the fixtures, `CONTRACT-MAP.md`, and
|
|
1448
|
+
`scripts/audit-contract-fixtures.py` carry current truth.
|
|
1449
|
+
|
|
1450
|
+
This repo's own `plan/` holds LANGUAGE-SPECIFIC task plans (`PARITY.md`,
|
|
1451
|
+
`SCAFFOLDING.md`, `TESTS.md`, `AI-CONTEXT.md`, and per-task files). The
|
|
1452
|
+
CROSS-framework audit and consolidation work is the central plan above.
|
|
1453
|
+
|
|
1454
|
+
**To advance a feature (the update loop):** pick the next feature from the parity
|
|
1455
|
+
backlog -> MEASURE all four side by side (assume no parity; no mocks, real
|
|
1456
|
+
services on the lab) -> DECIDE the best implementation, writing or superseding an
|
|
1457
|
+
ADR when the contract changes -> write the executable
|
|
1458
|
+
`fixtures/<feature>_contract.json` and fix the divergences in ALL FOUR with named
|
|
1459
|
+
positive and negative regressions -> flip owed->proven, run
|
|
1460
|
+
`scripts/audit-contract-fixtures.py`, and update the `CONTRACT-MAP.md` row from
|
|
1461
|
+
those counts -> verify yourself at HEAD on the lab -> ship `feature/release<ver>`
|
|
1462
|
+
-> `v3` -> tag. Pushing plan edits into tina4-documentation is a MERGE, never a
|
|
1463
|
+
rebase (the subtree graft + the PDF-sync bot).
|
|
1464
|
+
|
|
1429
1465
|
## First Principle: Documentation Matches Code Reality
|
|
1430
1466
|
|
|
1431
1467
|
**This rule overrides everything else in this file.**
|