[chappie-daemon]

The startup banner went through logger.info(...), so with JSON output the logo arrived inside one record with \n escapes:

{"level":30,"scope":"primary:app-primary","msg":"\n ███▄    █  ▒█████    ██████ ▄▄▄█████▓ ██▀███ …"}
{"level":30,"scope":"primary:app-primary","msg":"                                  v3.10.0"}

A banner is read by a person. The logo and its centred facts now go to stdout as plain text:

 ███▄    █  ▒█████    ██████ ▄▄▄█████▓ ██▀███  ▓█████ ▄▄▄       ███▄ ▄███▓
 ██ ▀█   █ ▒██▒  ██▒▒██    ▒ ▓  ██▒ ▓▒▓██ ▒ ██▒▓█   ▀▒████▄    ▓██▒▀█▀ ██▒
…
                                 v3.10.0
                        NIPs implemented: 1,2,3,…
                           Pay-to-relay disabled

Notes

• Nothing is lost for a log pipeline. logger.info here is createLogger, which turns an object argument into a formatted string before handing it to pino, so every other line in this file is text too — adding a "structured" record beside the banner would have been a string in a msg field, not fields. I tried that first and dropped it.
• logCentered used logger.info(' '.repeat(start), input) — a printf call with no placeholder. pino kept the extra argument, but relying on that was luck; the padding is now part of the string.
• The banner text moved to src/utils/banner.ts (RELAY_BANNER_LINES, centre), testable without a database, a cluster or a settings document. Its spec pins that no line exceeds the 74-column block — a wrapped line turns the logo into noise — and that an overlong line is left alone rather than truncated.
• app.spec.ts's fakeProcess gains a stdout, and a new case pins that run() writes the banner there as text.

Verification

• test/unit/app/app.spec.ts — 7 passing, including the new banner case
• test/unit/utils/banner.spec.ts — 4 passing
• src/app/app.ts type-checks; the banner renders as shown through a direct stdout write
• real confirmation is the next image: docker compose logs nostream

LOG_FORMAT=json

The banner is for a person reading docker compose logs. A log pipeline that requires every line to parse is the other audience, and it now has a switch: with LOG_FORMAT=json the artwork is replaced by one record, written before any worker forks:

{"level":30,"time":1793486578015,"pid":159864,"hostname":"cb6c98492fcc","msg":"relay starting","version":"3.10.0","supportedNips":[1,2,...],"payments":"disabled","eventStore":"postgres","clientWorkers":16,"maintenanceWorkers":1,"relayMonitor":false,"dvmWorkers":0}

Observed on a real run of this branch: LOG_FORMAT=json → the line above, zero non-JSON lines; unset → the logo and its centred facts as text. Anything but json (trimmed, case-insensitive) keeps the banner, so a typo fails towards the readable default. Documented in CONFIGURATION.md.

The record is written through the same stdout writer as the banner rather than through createLogger, for two reasons: the factory stringifies an object argument into msg before pino sees it, so fields would be lost, and a test can then read stdout instead of reaching into a pino instance built at import time.

[changeset-bot]

🦋 Changeset detected

Latest commit: fb861f5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
nostream	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[greptile-apps]

Confidence Score: 5/5

[Low impact] The PR appears safe to merge, with two non-blocking logging gaps worth fixing.

Findings

1.  JSON logs still contain text ▶
2.  Tor address disappears from logs ▶

Summary

The PR prints the startup banner directly to stdout and adds a JSON alternative.

• Startup shows a text banner by default and a JSON record when requested.

_{Reviews (2) · Last reviewed commit: "feat(startup): replace the banner with o..." · Reviewed by Greptile}

[coveralls]

Coverage Report for CI Build 41250216072

Warning

Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes.
Quick fix: rebase this PR. Learn more →

Coverage increased (+0.02%) to 77.425%

Details

• Coverage increased (+0.02%) from the base build.
• Patch coverage: 5 uncovered changes across 1 file (27 of 32 lines covered, 84.38%).
• No coverage regressions found.

Uncovered Changes

File	Changed	Covered	%
src/app/app.ts	26	21	80.77%
Total (2 files)	32	27	84.38%

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	11855
Covered Lines:	9591
Line Coverage:	80.9%
Relevant Branches:	6240
Covered Branches:	4419
Branch Coverage:	70.82%
Branches in Coverage %:	Yes
Coverage Strength:	773.48 hits per line

---

💛 - Coveralls

[greptile-apps]

JSON logs still contain text

With NODE_ENV=development and LOG_FORMAT=json, only the startup record becomes JSON. src/logger.ts still sends normal logs through pino-pretty, so readers expecting JSON cannot parse those lines despite the documented promise. Make the logger honor LOG_FORMAT=json too, and test both settings together.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Tor address disappears from logs

With LOG_FORMAT=json, logLine also drops the later Tor address message. The replacement startup record has no Tor address, and addOnion reports it only at debug level. At the default log level, operators lose the address previously printed at startup. Keep this later message as a JSON log instead of suppressing it with the artwork.