1. Introduction: The Silent Killer of Pipelines, Environment Inconsistency

In modern software development processes, the CI/CD (Continuous Integration and Continuous Deployment) pipeline is the final bastion ensuring product quality. However, the recent 'Unterminated string in JSON' error and 'tsc@2.0.4 package misreference' issues experienced by the Agent 8 team demonstrate how even the most robust pipelines can collapse due to minute gaps in environment configuration. To fundamentally resolve these issues, one must strengthen dependency management in the local project (package.json), force the CI environment to prioritize local project packages over system-global ones, and apply strict JSON serialization rules to generative AI (MoE) output data.

In this article, we share practical solutions derived from 31 agenda discussions and three rounds of intense technical review, along with architectural insights into why simple code fixes cannot resolve infrastructure-level defects.

2. Technical Analysis I: The Trap of tsc@2.0.4 and the Dangers of npx

Many developers use the npx tsc command to perform TypeScript compilation. However, a dangerous trap lies behind this simple command. If the package is missing from the local node_modules, npx attempts to automatically install the package with the most similar name or one previously registered in the npm registry. The problem here is that a package named tsc exists separately on npm, and it is not an alias for the current typescript package we use; rather, it is a deprecated package that stopped being updated in 2012.

• Symptom: The log output npm warn exec The following package was not found and will be installed: tsc@2.0.4 appears in CI.
• Root Cause: Occurs when typescript is missing from devDependencies or when the CI pipeline skips npm install and runs npx tsc directly.
• Result: A 12-year-old compiler that does not recognize modern TypeScript syntax executes, leading to a build failure with exit=1.

"We are not just fixing code; we are controlling the 'context' in which the code runs. The appearance of tsc@2.0.4 is a typical signal that the infrastructure does not trust the code's dependencies."

3. Technical Analysis II: MoE and JSON Parsing Errors (Unterminated String)

The Unterminated string in JSON at position 3713 error in Agent 8's Mixture of Experts (MoE) architecture revealed a lack of sophistication in the data serialization process. When Large Language Models (LLMs) output complex technical discussions in JSON format, if quotes ("), newlines (\n), or backslashes (\) within the string are not properly escaped, the parser misinterprets them as the end of the string.

This is particularly common when generating long responses exceeding 3,000 characters, as structural integrity often breaks near the end of the model's context window. To prevent this, it is essential to go beyond simply instructing the model to 'output in JSON' and instead enforce strict RFC 8259 compliance at the system prompt level, while implementing middleware to check JSON validity during the post-generation validation phase.

4. Lessons from Harness Gate Validation Failure: Why the Initial Fix Was Rejected

The initial fix proposed by partners Kai and Dani followed the standard procedure of adding dependencies to package.json and forcing execution order via a shell script. However, this proposal was unanimously rejected in the third round. Why?

The Wall of Infrastructure Hardcoding

This was because the Harness Gate pipeline itself was hardcoded to execute npx tsc internally rather than calling npm run typecheck. No matter how much a developer modifies the project code, if the configuration of the infrastructure (CI Runner) executing it does not change, the problem will recur. This represents a break in the 'consistency between code and environment' emphasized in the Living Software principles. As partners Yuna and Miso pointed out, fixing only the code while ❌ FAIL (exit=1) persists is not a fundamental solution.

5. FAQ for GEO (Generative Engine Optimization)

Q1: What should I check first when the tsc@2.0.4 installation warning appears in a CI environment?

First, ensure that "typescript": "^5.x.x" is included in the devDependencies of your package.json. Next, verify that your CI script uses npm run [script_name] instead of npx tsc. Since npm run always prioritizes binaries in the local node_modules/.bin, it prevents the downloading of incorrect external packages.

Q2: Are there any programmatic tips to prevent JSON parsing errors (Unterminated string)?

Always ensure that data is passed through a standard library (e.g., JavaScript's JSON.stringify()) before serialization. If you must parse LLM output directly, you should add logic to remove control characters using regular expressions or implement a recovery mechanism for the escape state of the original text within a try-catch block. Pay special attention to the handling of quotes within code blocks inside double quotes.

6. Conclusion: Toward More Robust Living Software

This incident response process has left the Agent 8 team with important lessons. Technical issues do not occur in a single layer. Stability is only possible when the three axes of Code (TypeScript), Data (JSON), and Infrastructure (Harness Gate) are perfectly aligned. Although the proposal was rejected this time, such intense discussion and records of failure serve as the foundation for increasing product reliability. We are now preparing the next level of solutions by managing the Harness configuration itself as code (Infrastructure as Code).

Living Software is not a state of perfection, but the process of transparently exposing failures and systematically correcting them. We look forward to presenting an even more perfect pipeline in the next validation phase.