Fix instrumentation wording

[leynos]

Summary

• clarify table wording by using lower-case "tracing instrumentation"
• rephrase span! and event! mention for clarity

Testing

• make fmt
• make lint
• make test
• markdownlint docs/wireframe-1-0-detailed-development-roadmap.md (fails: MD056 table column count)

---

https://chatgpt.com/codex/tasks/task_e_685a9996e69883228087af2380302c6c

Summary by Sourcery

Clarify wording in the detailed development roadmap by using lowercase "tracing instrumentation" and formatting span! and event! calls

Documentation:

• Lowercase "Tracing Instrumentation" to "tracing instrumentation" in the roadmap table
• Format span! and event! mentions as code and clarify they are call invocations

Summary by CodeRabbit

• Documentation
  • Clarified the description of task 4.1 in the Phase 4 development roadmap to specify the use of span! and event! calls.

[sourcery-ai]

Reviewer's Guide

This PR refines the wireframe roadmap documentation by standardizing the casing of “tracing instrumentation” and improving clarity around macro mentions through inline code formatting and precise wording.

File-Level Changes

Change	Details	Files
Normalize casing of tracing instrumentation	Change table header from “Pervasive tracing Instrumentation” to lower-case “instrumentation”	docs/wireframe-1-0-detailed-development-roadmap.md
Reformat and rephrase macro mentions for clarity	Wrap span! and event! in inline code ticks Replace plural suffixes “span!s” and “event!s” with “span! calls” and “event! calls”	docs/wireframe-1-0-detailed-development-roadmap.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The change updates the description of task 4.1 in the Phase 4 development roadmap document, clarifying that "span!" and "event!" refer to specific macro or function calls by using code formatting and more precise language. No functionality, dependencies, or task size are affected.

Changes

File	Change Summary
docs/wireframe-1-0-detailed-development-roadmap.md	Clarified references to span! and event! as calls in task 4.1 description

Poem

In the roadmap, words are now clear and bright,
span! and event! calls shine in code-form light.
No more confusion, just clarity’s delight—
A rabbit’s small hop makes documentation right!
🐇✨

✨ Finishing Touches

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Post Copyable Unit Tests in Comment
• Commit Unit Tests in branch codex/update-wording-for-consistency-in-roadmap

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sourcery-ai]

Hey @leynos - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[coderabbitai]

Actionable comments posted: 1

🔭 Outside diff range comments (1)

docs/wireframe-1-0-detailed-development-roadmap.md (1)

51-54: Table row has the wrong number of columns – breaks markdown-lint

Row 53 contains only three columns, so markdownlint reports MD056 (“table column count mismatch”), causing the pipeline failure mentioned in the PR description.

-| ------ | ----------                     |

Simply delete this stray delimiter row (or pad it to five columns) and the linter should pass.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e0e20b2 and 18da574.

📒 Files selected for processing (1)

• docs/wireframe-1-0-detailed-development-roadmap.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build-test