fix(javascript): retain shorter literal metadata encodings (#1408)

Choose the shorter complete JSON or digest key and string display label.
Short values keep their existing identities and labels, while large values
retain the payload-copy reduction without an arbitrary truncation limit.

docs/javascript-application-workflows.md

@@ -91,16 +91,18 @@ mapped candidate, but structural reachability, semantic influence, runtime
 observation, and causal proof remain separate claims.
 
 Semantic literal nodes keep their complete value in `properties.value`; literal
-queries match that field. String labels read `string literal` rather than
-repeating the payload. A literal's `identity.role_key` commits its canonical
-JSON value as `value-sha256:<digest>`, together with its binding and property
-role. This keeps large values out of identity and display metadata without
+queries match that field. String labels use `string literal` when that is
+shorter than the complete JSON value. A literal's `identity.role_key` commits
+its canonical JSON value as `value-sha256:<digest>` when the digest key is
+shorter; smaller values keep their existing JSON key. This keeps large values
+out of identity and display metadata without expanding short values or
 truncating their Evidence.
 
-New analyses therefore produce different literal node IDs from the earlier
-payload-bearing role keys. Use IDs returned by the selected parent graph and
-read literal values from `properties.value`, rather than decoding role keys or
-labels. Previously stored graphs and their original IDs remain valid inputs.
+New analyses therefore produce different IDs for hashed literals from the
+earlier payload-bearing role keys. Use IDs returned by the selected parent
+graph and read literal values from `properties.value`, rather than decoding
+role keys or labels. Previously stored graphs and their original IDs remain
+valid inputs.
 
 ## Version comparison