Commit 2143f36
docs: add Platform Credits page and three-bucket model (#83)
* docs: add Platform Credits page and three-bucket model
Adds a new conceptual page introducing Platform Credits as the third
credit bucket in Warp, alongside AI credits and Cloud Agent Credits.
Explains when Platform Credits apply (cloud agents on any plan, and
local agents on Business/Enterprise with BYOK or BYOLLM inference),
when they don't, and where they appear in usage views.
Also updates the existing Credits and Plans pages to introduce the
three-bucket model and cross-link to the new page.
Pricing specifics are deferred to warp.dev/pricing.
Co-Authored-By: Oz <oz-agent@warp.dev>
* docs(platform-credits): align charge matrix and tighten copy
- Fix contradiction flagged in PR #83 review: cloud agents always charge
Platform Credits regardless of inference source. Reframe intro, three-
bucket section, and the multi-bucket example to match the matrix in
'When Platform Credits apply'.
- Point Generate link at /agent-platform/local-agents/generate/.
- Remove time-unit details from the rate section; defer to warp.dev/pricing.
- Drop internal tooltip-label callouts from the admin section.
- Tighten plans-pricing-refunds Platform Credits one-liner to match.
Co-Authored-By: Oz <oz-agent@warp.dev>
* docs: reframe Platform Credits around inference / compute / platform infrastructure
Per review feedback, lead with the three-infrastructure framing (inference,
compute, platform) rather than the orchestration-layer framing. Each credit
bucket now names the kind of infrastructure it covers. Also drop the
enterprise custom-rate sentence; warp.dev/pricing remains the source of
truth for rates.
Co-Authored-By: Oz <oz-agent@warp.dev>
* docs(platform-credits): address audit findings
- Reframe Platform Credits intro to lead with the rule (every cloud agent
run, plus Business/Enterprise local agent runs with customer-supplied
inference) instead of the negative 'when Warp isn't paying' framing.
- Align cross-file framing in credits.mdx and plans-pricing-refunds.mdx so
all three pages describe Platform Credits in the same terms.
- Replace 'Workflow autofill' with linked 'AI Autofill'.
- Replace 'Local Oz runs' with 'local agent runs' (Oz run is cloud-only).
- Deduplicate the second BYOK parenthetical and normalize BYOLLM wording.
- Clarify that self-hosted cloud workers count as cloud agents for
Platform Credits purposes.
Co-Authored-By: Oz <oz-agent@warp.dev>
* Update src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx
Co-authored-by: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com>
* Update src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx
Co-authored-by: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com>
* docs(platform-credits): apply Rachael's wording suggestions
Address remaining suggested edits from Rachael's review on PR #83:
- plans-pricing-refunds.mdx: rewrite Platform Credits bullet to
action-oriented form, matching sibling bullets.
- platform-credits.mdx: de-dupe "charge for" repetition in intro;
convert three-bucket bullets to active-voice complete sentences;
rewrite "When Platform Credits apply" with "Uses Platform Credits"
/ "Doesn't use Platform Credits" headers and complete-sentence
bullets; replace internal "harness" jargon with "which agent runs
the task"; rename "Third-party harnesses run directly" to
"Third-party agent CLIs run directly".
- credits.mdx: same active-voice and "agent CLI" updates in the
three-bucket summary and Platform Credits subsection.
Validation: style_lint --changed clean (9 files, 0 issues),
check_links --internal-only clean (2435 links, 0 broken).
Co-Authored-By: Oz <oz-agent@warp.dev>
* docs(platform-credits): reframe Cloud Agent Credits as compute bucket + add BYOK TOS rule
Two pieces of feedback addressed on PR #83.
1. Cloud Agent Credits reframing.
The bucket is described as compute infrastructure consumed by any
agent run, local or cloud. Local agents rarely draw from it in
practice because they don't run on Warp's compute, but the credit
type is no longer tied to 'cloud-only by construction.'
Updated:
- platform-credits.mdx three-bucket bullet for Cloud Agent Credits
(was 'cover compute infrastructure when cloud agents run on
Warp-hosted compute,' now 'are the compute bucket... cover
Warp-hosted compute consumed by any agent run, local or cloud').
- credits.mdx three-bucket bullet for Cloud Agent Credits with the
same framing.
- credits.mdx ### Cloud Agent Credits section intro reframed as
'the compute credits bucket - consumed when an agent run uses
Warp-hosted compute. Both local and cloud agent runs can in
principle draw from this pool...'
- credits.mdx 'Not eligible' list intro tightened to make the
reason explicit ('because they don't run on Warp-hosted compute')
instead of implying the credit type is fundamentally cloud-only.
2. BYOK / customer-supplied inference TOS rule.
Surfaces Warp's TOS rule wherever BYOK or customer-supplied
inference is invoked as a workaround for Warp-paid inference.
Added:
- :::caution callout in platform-credits.mdx after the
customer-supplied-inference paragraph, stating the
individuals-and-organizations <=10 users rule and the Business
or Enterprise requirement for orgs >10 users. Links to the
canonical https://www.warp.dev/terms-of-service.
- One-line forward reference at the end of the 'Local agents on
Business or Enterprise with customer-supplied inference' bullet
in platform-credits.mdx, pointing readers back to the callout
for plan-size eligibility.
- :::caution callout in bring-your-own-api-key.mdx directly after
the existing :::note about BYOK paid-plan availability.
- One-sentence summary of the TOS rule in the 'BYOK on Enterprise
and Business plans' section, so admins reading that section see
the eligibility constraint.
Out of scope: renaming the 'Cloud Agent Credits' product term,
changing pricing-faqs.mdx, or reworking BYOLLM enterprise gating
(BYOLLM is already Enterprise-only, so the TOS rule is implicit).
Validation:
- style_lint --changed: 0 issues across 9 files scanned.
- check_links --internal-only: 0 broken links across 319 files and
2,435 internal links.
Co-Authored-By: Oz <oz-agent@warp.dev>
* docs(platform-credits): holistic polish pass after the compute/TOS reframe
Tightens stale framing and copy that fell out of alignment after the
last commit reframed Cloud Agent Credits as the compute bucket.
credits.mdx:
- Drop the orphaned 'small hosting fee, charged only when running
agents in the cloud' sentence in the opener (L13). It predates the
three-bucket model and now contradicts the new framing immediately
below it; the bullet at the new L16 covers the same ground correctly.
- Reframe the 'Cloud Agent Credits' bullet in Credit limits and
billing (was L47, now L45). The old wording ('their normal Warp
credits, Cloud Agent Credits, or a Build plan with available
credits') treated Cloud Agent Credits as a separate currency.
Rewritten as 'Cloud agents and integrations: Individual users can
run cloud agents via the CLI and API, drawing from their plan
credits. Slack and Linear integrations require team membership.'
- Tighten 'in principle draw from this pool' to 'are eligible to draw
from this pool' in the Cloud Agent Credits section intro (L122).
platform-credits.mdx:
- Frontmatter description shortened from 219 to 144 chars (back in the
50-160 SEO range).
- Drop the redundant second sentence on L13 ('Platform Credits don't
apply to local runs on Free, Build, or Max plans...'). The Doesn't
use section below already covers it. The first sentence (defining
customer-supplied inference) stays since the TOS callout depends on it.
- Align the Admin usage breakdown bullet (L55): 'distinct from the AI
and Compute segments' -> 'distinct from the AI credits and Cloud
Agent Credits segments'. Uses the bucket names consistently with
the rest of the page.
Validation:
- style_lint --changed: 2 pre-existing warnings on
bring-your-own-api-key.mdx (Zero Data Retention is a proper term;
Enterprise/Business are proper plan names). Acceptable.
- check_links --internal-only: 0 broken links across 319 files and
2,433 internal links.
Co-Authored-By: Oz <oz-agent@warp.dev>
* docs(platform-credits): rename Cloud Agent Credits -> compute credits + reframe as orthogonal credit-type/host model
Per user correction: the credit type is 'compute credits' (lowercase),
not 'Cloud Agent Credits.' The old name conflated the credit type
(compute) with the host (cloud). The corrected conceptual model treats
the three credit types (AI/inference, compute, platform) and the two
host types (local, cloud) as orthogonal dimensions: any credit type
can in principle apply to any host, with compute credits being the
one that in practice only cloud agents consume (because local agents
run on the user's machine).
Files touched:
Content (6):
- credits.mdx: three-bucket bullets reframed to lead with the
orthogonal dimension; section heading '### Cloud Agent Credits' ->
'### Compute credits'; section intro rewritten; eligible/not-
eligible subheadings renamed; all inline mentions and the
'#cloud-agent-credits' anchor flipped to '#compute-credits'.
- platform-credits.mdx: page intro three-bucket sentence updated to
use 'compute credits'; three-bucket bullets reframed with the
orthogonal-dimension intro; multi-bucket example updated; per-user
and admin breakdown bullets updated to use bucket names consistently.
- team-access-billing-and-identity.mdx: 3 references reworded to
drop the 'normal Warp credits, Cloud Agent Credits, or a Build plan'
stale enumeration and use plan credits / compute credits.
- agent-platform/cloud-agents/overview.mdx: 2 references updated to
the new terminology + anchor.
- enterprise/support-and-resources/billing.mdx: 'small hosting fee'
framing replaced with the explicit three-bucket model; 'no separate
cloud agent credits or local credits' sentence replaced with a
framing that aligns with the bucket model (credit type depends on
infrastructure, not on local vs cloud).
- terminal-and-agent-modes.mdx: Credits indicator description
generalized from 'remaining cloud agent credits' to 'remaining
credits.'
Support / glossary (3):
- AGENTS.md: 'Cloud Agent Credits' entry replaced with 'compute
credits' (lowercase) entry; new 'Platform Credits' entry added
(was previously implicit).
- .agents/references/terminology.md: same swap in the billing glossary.
- .agents/skills/style_lint/style_lint.py: 'Cloud Agent Credits'
removed from PROPER_FEATURE_NAMES (no longer a Title-Case
exception since it's now lowercase); 'Platform Credits' added to
PROPER_FEATURE_NAMES; PRODUCT_CASING gains 'Cloud Agent Credits' ->
'compute credits' and 'Cloud Agent Credit' (singular) as one-way
nudges so future contributors don't reintroduce the old name.
Validation:
- 0 remaining 'Cloud Agent Credit' or '#cloud-agent-credit' references
in src/content/docs.
- style_lint --changed: only the 2 pre-existing BYOK warnings (Zero
Data Retention, BYOK on Enterprise and Business plans). Both are
acceptable false positives flagged in prior commits.
- check_links --internal-only: 0 broken across 319 files and 2,434
internal links. The Astro Starlight heading-to-anchor derivation
(### Compute credits -> #compute-credits) resolves correctly.
Out of scope:
- Lowercasing 'Platform Credits' (user did not request).
- Changes to pricing-faqs.mdx (no mentions).
- vercel.json redirects (anchors aren't redirected; all inbound refs
in our own docs were updated directly).
Co-Authored-By: Oz <oz-agent@warp.dev>
* docs: normalize credits list separators
Co-Authored-By: Oz <oz-agent@warp.dev>
* docs(platform-credits): restore descriptive 'cloud agent credits' on the Credits indicator UI label
In the prior rename pass I over-corrected one spot: the 'Credits
indicator' UI label in terminal-and-agent-modes.mdx, which described
the cloud agent conversation's credit-balance indicator. The original
text 'Shows your remaining cloud agent credits' was using 'cloud
agent credits' descriptively (as in 'the credits cloud agents
consume'), not as a formal product-name reference. Restoring the
original wording.
The PRODUCT_CASING lint nudge is case-sensitive on Title Case 'Cloud
Agent Credits' / 'Cloud Agent Credit', so descriptive lowercase
mentions like this one don't trigger it.
Co-Authored-By: Oz <oz-agent@warp.dev>
* docs(platform-credits): revert compute credits rename back to Cloud Agent Credits
Per user feedback: the product name is 'Cloud Agent Credits'
(Title Case). The word 'compute' is the type description (what the
bucket covers - the sandbox an agent runs in), not the product name.
My prior rename pass conflated the two. Revert it.
Kept from the prior pass:
- The orthogonal credit-type/host conceptual reframe: 'Credit types
and where an agent runs (local or cloud) are independent. Each
agent run consumes from whichever credit types apply to it.' This
framing was an improvement and stays.
- The Enterprise billing page rewrite: the old 'small hosting fee'
framing and the contradicting 'no separate cloud agent credits or
local credits' sentence stay replaced by the explicit three-bucket
explanation. Just substituted 'Cloud Agent Credits' back for the
product-name reference.
- The BYOK / customer-supplied inference TOS callouts in
platform-credits.mdx and bring-your-own-api-key.mdx.
- The Platform Credits glossary entry I added to AGENTS.md and
terminology.md (was a real gap, not added by mistake).
- The descriptive lowercase 'cloud agent credits' in
terminal-and-agent-modes.mdx:126 (UI label restoration in 8833ded).
Reverted:
- credits.mdx: three-bucket bullets, section heading '### Compute
credits' -> '### Cloud Agent Credits', section intro, eligible /
not-eligible subheadings and intros.
- platform-credits.mdx: page intro three-bucket sentence, three-bucket
bullets, multi-bucket example, per-user and admin breakdown
bullets.
- team-access-billing-and-identity.mdx: 3 references and anchor link.
- cloud-agents/overview.mdx: 2 references and anchors.
- enterprise/support-and-resources/billing.mdx: product-name swap.
- AGENTS.md: glossary entry back to 'Cloud Agent Credits'.
- terminology.md: same.
- style_lint.py: 'Cloud Agent Credits' back in PROPER_FEATURE_NAMES;
removed the two PRODUCT_CASING nudges for Cloud Agent Credits ->
compute credits.
Validation:
- 0 'compute credits' product-name references remain in
src/content/docs.
- style_lint --changed: only the 2 pre-existing BYOK header false
positives.
- check_links --internal-only: 0 broken across 319 files and 2,434
internal links. The '#cloud-agent-credits' anchor resolves via the
restored '### Cloud Agent Credits' heading.
Co-Authored-By: Oz <oz-agent@warp.dev>
* docs: add Platform Credits AEO summary
Co-Authored-By: Oz <oz-agent@warp.dev>
* Split Cloud Agent Credits into Compute credits + Cloud agent credits; rename plan credits to normal Warp credits
Address review feedback:
1. Split into two complementary concepts:
- **Compute credits** (sentence case): the compute bucket itself, used
alongside AI credits and Platform Credits when describing credit types.
- **Cloud agent credits** (sentence case, 'Cloud' capitalized): credits
consumed by cloud agents, in contrast with local agent credits.
Both refer to the same underlying bucket; pick the term that fits the
framing.
2. Rename 'plan credits' to 'normal Warp credits' in user-facing copy so
it's no longer confused with 'Build plan credits' (the proper plan
product noun, which is preserved).
Files updated:
- credits.mdx: Three-bucket bullets use 'Compute credits'. Section
heading '### Cloud Agent Credits' becomes '### Compute credits' with
anchor '#compute-credits', plus eligible/not-eligible subheadings
switch to 'compute credits'. A short note explains the 'Cloud agent
credits' alias for the host-context framing.
- platform-credits.mdx: Bucket-context bullets and per-user/admin
breakdown switch to 'Compute credits' (bucket framing) plus the
three-bucket intro sentence.
- team-access-billing-and-identity.mdx, cloud-agents/overview.mdx:
Cloud-vs-local-host bullets use 'Cloud agent credits' (sentence case)
pointing to '#compute-credits'.
- enterprise/support-and-resources/billing.mdx: Three-bucket framing
uses 'compute credits' alongside AI and Platform Credits.
- add-on-credits.mdx, pricing-faqs.mdx: 'plan credits' (legacy term)
swapped for 'normal Warp credits'; 'Build plan credits' (proper noun)
is preserved.
- AGENTS.md, .agents/references/terminology.md: Glossary updated with
both 'Compute credits' and 'Cloud agent credits' entries, and the
'normal Warp credits' guidance.
- .agents/skills/style_lint/style_lint.py: Removes 'Cloud Agent Credits'
from PROPER_FEATURE_NAMES and adds a nudge to use sentence case
('Cloud agent credits') or 'compute credits' depending on framing.
Validation:
- 0 'Cloud Agent Credits' Title Case occurrences in src/content/docs
- All 3 remaining 'plan credits' matches are 'Build plan credits'
- style_lint --changed: only pre-existing BYOK false positives
- check_links --internal-only: 0 broken across 2,434 internal links
- '#compute-credits' anchor resolves via renamed section heading
Co-Authored-By: Oz <oz-agent@warp.dev>
* Lowercase 'cloud agent credits' mid-sentence/mid-bullet
Per review feedback: the term 'cloud agent credits' is a common noun and
should be lowercased anywhere it appears mid-sentence or mid-bullet.
Only capitalize the first letter at the start of a sentence or bullet.
Files updated:
- credits.mdx L124: the alias clarification ('referred to as **cloud
agent credits**') is now lowercase.
- team-access-billing-and-identity.mdx L21, L41, L84: all three are
mid-bullet/mid-sentence references and are lowercased.
- cloud-agents/overview.mdx L120, L135: mid-bullet references lowercased.
- AGENTS.md, .agents/references/terminology.md: glossary entry header
is now '**cloud agent credits**' (lowercase) to match the canonical
form for common-noun terms (consistent with **credits**, **normal
Warp credits**, etc.). The description was updated to explain when
to capitalize.
- .agents/skills/style_lint/style_lint.py: PRODUCT_CASING nudge now
recommends lowercase 'cloud agent credits' with a note about
capitalizing the first letter at sentence/bullet boundaries.
Glossary entries that lead a bullet (e.g. '**cloud agent credits**')
stay lowercase to follow the existing common-noun convention in
terminology.md, not because they're mid-sentence.
Co-Authored-By: Oz <oz-agent@warp.dev>
* Lowercase 'platform credits' mid-sentence/mid-bullet/mid-heading
Per review feedback, apply the same common-noun convention to 'platform
credits' that we applied to 'cloud agent credits' and 'compute credits'.
Capitalize the first letter only at the start of a sentence, bullet, or
heading; lowercase everywhere else.
Files updated:
- platform-credits.mdx: title -> 'Platform credits'. Every body, bullet,
and heading occurrence reframed:
- Three-bucket bullets and mid-sentence text -> 'platform credits' /
'**Platform credits**' (bullet leads stay sentence-cased).
- All H2/H3 headings ('## How platform credits are measured',
'## When platform credits apply', '### Uses platform credits',
'### Doesn't use platform credits', '## Where platform credits
appear') lowercase the second word.
- credits.mdx: three-bucket bullet, section heading '### Platform
credits', subsection headings, and all in-text occurrences updated.
Mid-sentence link text 'See [platform credits](...)' is also
lowercased.
- enterprise/support-and-resources/billing.mdx: the example sentence
the reviewer flagged ('...AI credits..., compute credits..., and
platform credits for the orchestration layer') and the three-types
parenthetical (AI credits, compute credits, and platform credits)
are lowercased.
- plans-pricing-refunds.mdx: the related-links bullet now reads
'[Platform credits](...) - learn how platform credits cover...'.
- AGENTS.md, .agents/references/terminology.md: glossary entry header
is now '**platform credits**' (matching the existing common-noun
convention used for **credits**, **normal Warp credits**, **compute
credits**, **cloud agent credits**) with a usage note explaining
the casing rule. Adjacent **compute credits** entry is normalized
the same way.
- .agents/skills/style_lint/style_lint.py: 'Platform Credits' removed
from PROPER_FEATURE_NAMES and a new PRODUCT_CASING nudge maps the
title-cased form to lowercase 'platform credits' with a note about
capitalizing at sentence/bullet/heading boundaries.
Validation:
- check_links --internal-only: 0 broken across 2,434 internal links.
- The only remaining 'Platform Credits' Title Case match is the
linter's own wrong->right mapping (expected).
Co-Authored-By: Oz <oz-agent@warp.dev>
* docs: rename 'normal Warp credits' to 'Warp credits'
Drops the 'normal' qualifier across user-facing copy, the terminology
glossary, and AGENTS.md. 'Warp credits' is the cleaner brand-aligned
term for credits included with a subscription plan.
Co-Authored-By: Oz <oz-agent@warp.dev>
* docs: polish credit copy after rename
- Drop now-redundant 'or Build plan credits' / 'or a Build plan with available credits' (Build plan credits are Warp credits).
- Tighten 'individual Warp credits' to 'individual credits' to match the prior bullet's wording.
- Remove duplicate 'Warp' in 'your included monthly Warp credits'.
- Replace 'Build plan credits' with [Add-on Credits] in the cloud-agents requirements bullet so it mirrors the team-requirements bullet below it.
- Restructure the Add-on Credits/limits sentence in platform-credits.mdx to make the consumption order explicit.
- Update 'same plan credit pool' to 'same Warp credit pool' in credits.mdx.
Co-Authored-By: Oz <oz-agent@warp.dev>
* docs: drop redundant credit-type enumerations
The '(any type works)' parenthetical and the 'Warp credits, cloud agent
credits, and Add-on Credits all work' bullet aren't actually telling the
user anything actionable — they're all credits and they all draw from
the same balance. Just say '20 credits' and let the linked billing pages
handle the credit-type breakdown.
Touched:
- agent-platform/cloud-agents/overview.mdx (2 occurrences; removed the
redundant credit-type bullet under Credit requirements as well as the
vague 'Usage is billed based on credit type and team configuration'
filler bullet).
- agent-platform/cloud-agents/team-access-billing-and-identity.mdx (2).
- agent-platform/cloud-agents/quickstart.mdx (1).
- agent-platform/cloud-agents/integrations/slack.mdx (1).
- agent-platform/cloud-agents/integrations/linear.mdx (1).
Co-Authored-By: Oz <oz-agent@warp.dev>
---------
Co-authored-by: Oz <oz-agent@warp.dev>
Co-authored-by: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com>1 parent 9375a44 commit 2143f36
15 files changed
Lines changed: 143 additions & 38 deletions
File tree
- .agents
- references
- skills/style_lint
- src/content/docs
- agent-platform/cloud-agents
- integrations
- enterprise/support-and-resources
- support-and-community/plans-and-billing
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
231 | 231 | | |
232 | 232 | | |
233 | 233 | | |
234 | | - | |
| 234 | + | |
| 235 | + | |
| 236 | + | |
235 | 237 | | |
236 | | - | |
| 238 | + | |
237 | 239 | | |
238 | 240 | | |
239 | 241 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
35 | 35 | | |
36 | 36 | | |
37 | 37 | | |
38 | | - | |
| 38 | + | |
39 | 39 | | |
40 | | - | |
41 | | - | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
42 | 43 | | |
43 | 44 | | |
44 | 45 | | |
45 | 46 | | |
46 | 47 | | |
| 48 | + | |
| 49 | + | |
47 | 50 | | |
48 | 51 | | |
49 | 52 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
610 | 610 | | |
611 | 611 | | |
612 | 612 | | |
613 | | - | |
614 | | - | |
| 613 | + | |
| 614 | + | |
| 615 | + | |
| 616 | + | |
615 | 617 | | |
616 | 618 | | |
617 | 619 | | |
| |||
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
66 | 66 | | |
67 | 67 | | |
68 | 68 | | |
69 | | - | |
| 69 | + | |
70 | 70 | | |
71 | 71 | | |
72 | 72 | | |
| |||
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
80 | 80 | | |
81 | 81 | | |
82 | 82 | | |
83 | | - | |
| 83 | + | |
84 | 84 | | |
85 | 85 | | |
86 | 86 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
117 | 117 | | |
118 | 118 | | |
119 | 119 | | |
120 | | - | |
| 120 | + | |
121 | 121 | | |
122 | 122 | | |
123 | 123 | | |
| |||
130 | 130 | | |
131 | 131 | | |
132 | 132 | | |
133 | | - | |
134 | | - | |
135 | | - | |
| 133 | + | |
136 | 134 | | |
137 | 135 | | |
138 | 136 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
157 | 157 | | |
158 | 158 | | |
159 | 159 | | |
160 | | - | |
| 160 | + | |
161 | 161 | | |
162 | 162 | | |
163 | 163 | | |
| |||
Lines changed: 5 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
18 | 18 | | |
19 | 19 | | |
20 | 20 | | |
21 | | - | |
| 21 | + | |
22 | 22 | | |
23 | 23 | | |
24 | 24 | | |
| |||
27 | 27 | | |
28 | 28 | | |
29 | 29 | | |
30 | | - | |
| 30 | + | |
31 | 31 | | |
32 | 32 | | |
33 | 33 | | |
| |||
38 | 38 | | |
39 | 39 | | |
40 | 40 | | |
41 | | - | |
| 41 | + | |
42 | 42 | | |
43 | 43 | | |
44 | 44 | | |
| |||
79 | 79 | | |
80 | 80 | | |
81 | 81 | | |
82 | | - | |
| 82 | + | |
83 | 83 | | |
84 | | - | |
| 84 | + | |
85 | 85 | | |
86 | 86 | | |
87 | 87 | | |
| |||
Lines changed: 2 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
31 | 31 | | |
32 | 32 | | |
33 | 33 | | |
34 | | - | |
| 34 | + | |
35 | 35 | | |
36 | 36 | | |
37 | 37 | | |
38 | | - | |
| 38 | + | |
39 | 39 | | |
40 | 40 | | |
41 | 41 | | |
| |||
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
71 | 71 | | |
72 | 72 | | |
73 | 73 | | |
74 | | - | |
| 74 | + | |
75 | 75 | | |
76 | 76 | | |
77 | 77 | | |
| |||
0 commit comments