Elixir good first issues

AI Summary: The `ptc init --example` command does not list available embedded examples. Users must intentionally provide an invalid example name to trigger an error message that reveals the catalogue. The issue suggests adding a `--list-examples` flag or including the example names directly in the `ptc help init` output to improve discoverability for new users.

AI Summary: The user is reporting a friction point in the documentation for inspecting wire records in MCP (Model-Centric Programming). While the documentation states these records are retained, it fails to clearly identify the command or method for reading them. This leads users to resort to less supported methods like using `strings` on sealed artifacts.

AI Summary: The CLI tool 'ptc' provides a misleading error message when a project document is not found or incorrectly configured. It incorrectly reports a missing 'application manifest' instead of indicating that the project document itself is missing or that the application path within the document is incorrect. This ambiguity causes confusion for new users, leading them to inspect the wrong files.

AI Summary: This issue describes a friction point in the `ptc` tool where `println` output is not immediately visible to the user during a run. The output is stored in a private inspection artifact, but this artifact is not enabled by default, and there's no runtime indication that the prints were retained. The user expects a clear message on stderr when prints are retained, indicating their location.

AI Summary: This issue proposes enhancing existing tests for tachyon envelope parsing. Currently, tests only check for the presence of an error, but the goal is to also validate that the specific error message is as expected, leading to more robust testing.

AI Summary: The "Polls closing soon" section on the Home dashboard displays a confusing "Polls have been reset" message when the refresh button is pressed. This indicates a mismatch between the action performed (refreshing poll data) and the user-facing notification.

AI Summary: When running a private-class result with no specified destination, the CLI exits with a generic internal error (exit 70). However, when a destination is provided but is incorrect, a more specific and actionable error ('private_destination_required') is correctly raised. This suggests a missed branch in error handling where the absence of a destination should also trigger the specific error.

AI Summary: The `ptc repl` command, when used to document prelude exports like `agent.core/run`, incorrectly reports "No documentation found" unless a `--project` flag is specified. This is problematic because the generated `AGENTS.md` file and `ptc docs agent-guide` instruct users to run these commands without the project flag, leading to a false impression that functions do not exist. The `apropos` command also suffers from similar issues, returning incomplete results.

AI Summary: This issue requests the completion of the Italian translation for the application's user interface, flash messages, emails, and error pages. It requires updating Gettext catalogs, ensuring correct number and date formatting for Italian conventions, and handling formal address. The goal is a fully localized Italian experience, avoiding English fallbacks.

AI Summary: This issue proposes adding support for a 'pre-re' (pre-renewal) version of a game, likely due to the complexity of implementing new mechanics and skills in the current 're' (renewal) version. The developer plans to achieve this by splitting database and NPC code, and implementing conditional compilation for mechanics, skills, and other game elements.

AI Summary: The `ptc init` command incorrectly refuses to initialize in any directory that already exists, including empty directories and Git repositories. The error message is unhelpful, lacking details about the specific path or rule that caused the failure. This prevents users from initializing `ptc` in existing projects or even in newly created, empty directories.

AI Summary: The PTC Viewer incorrectly returns a 200 OK status code and renders the runs index for any unknown non-API path. This leads to a confusing user experience where mistyped or invalid run URLs appear to work, but display incorrect content, hindering users trying to diagnose issues.

AI Summary: The `ptc repl` command provides a less informative error message for `credential_unavailable` compared to `ptc run`. While `ptc run` clearly states the provider, operation, and remedies, `ptc repl` wraps the error in a generic `command_failed` message, obscuring crucial details. This inconsistency creates friction for new users who encounter the REPL first and need clear guidance on resolving credential issues.

AI Summary: The documentation for designing agent workflows incorrectly presents `returned-value` and `quarantined` as shipped API functions. In reality, these are private helper functions defined within the `support-triage` example's `workflow.clj` file, leading to confusion and wasted validation cycles for new users who cannot find them.

AI Summary: The `ptc doctor --connect` command incorrectly writes Erlang logger notices to stdout when a TLS failure occurs, corrupting the JSON output and making it unparseable. This issue specifically affects TLS certificate expiry errors, while other connection errors produce clean output. The expected behavior is for all runtime logs to go to stderr, leaving stdout exclusively for the machine-readable JSON report.

AI Summary: This issue highlights a problem with error reporting for component override descriptors. The same generic error message is displayed for three distinct types of descriptor mistakes, providing no specific details to help the user diagnose the problem. Additionally, the error message incorrectly references a fixed filename ('component-override.json') instead of the actual file provided by the user.

AI Summary: The `--envelope` flag in the `ptc` CLI tool silently overwrites the project's default envelope artifact instead of duplicating it. This leads to under-reporting in spend ledgers, as runs using the flag are not saved in the `.ptc/envelopes/` directory. The documentation does not clearly state this behavior, causing confusion for users.

AI Summary: The user is unable to pass the `--only` option when implementing SBOM generation, leading to the inclusion of unwanted non-production packages in their SBOM. This appears to be a feature request or a bug preventing the intended filtering of SBOM content.

AI Summary: The `ptc viewer` tool defaults to using port 4123 for all projects, leading to port collisions when multiple projects are initialized. When a collision occurs, the error message is unhelpful, and the user is instead directed to a working Viewer instance from another project, creating confusion and a false sense of security.

AI Summary: A trailing newline character in a credential file causes the command to fail with a generic `internal_error` instead of a more specific, actionable error. This is problematic because the `file:` credential type is recommended for storing secrets, and common methods of creating such files (like `printf` or `echo`) often introduce trailing newlines.

AI Summary: The `ptc` command's root usage message does not advertise the `ptc help` command, despite documentation and generated files instructing users to start with it. This omission creates friction for new users and contradicts existing guidance.

AI Summary: The `ptc run --envelope` command fails with exit code 74 if the specified envelope destination path already exists. This occurs after the workflow has already executed and been billed, with no output indicating the cause of the failure. The user is charged for a run but receives neither the results nor the envelope.